#176 Cater for audio/video facsimile

RED
closed-duplicate
3
2013-11-13
2009-04-01
No

Bertrand Gaiffe and others have mentioned the need to record information of audio/video files which are provided in facsimile of the transcribed text. Particularly to be able to reference zones or ranges in these surrogates. They appropriated facsimile and zone for this usage. The point isn't to describe them (as one would in sourceDesc) but to have ranges and three and four dimensional zones which can then be referenced as facsimile content elsewhere inside a transcription, exactly the way one currently uses @facs to point to a zone in an image. If one's facsimile is not an image, but a video/audio/other then it is much more complicated to do this in TEI currently. While they may have been able to use timeline for this, perhaps the TEI should re-examine the way it handles audio/video/graphic files to make sure that we have some joined-up thinking on the way we handle pointing into portions and zones of multimedia objects.

-James

Discussion

  • Lou Burnard

    Lou Burnard - 2010-09-13

    Needs to be discussed along with 2507305

     
  • Martin Holmes

    Martin Holmes - 2011-03-07

    I'd like to see how BG & co encoded the alteration of zones over time (as when a speaking character moves across the screen). Do you record two separate positions at two separate times, and then rely on the user agent to "tween" them?

     
  • Bertrand Gaiffe

    Bertrand Gaiffe - 2011-03-18

    Until now, we have only used facsimile to link the transcription to an audio file. For the alignment, we have used timeline. However, we could in theory have zones of dimension 1 (time). Probably we could do a lot with such zones, but we sometimes also need points in time (to "synch" an anchor for instance).
    Another question is when we have more than one multimedia file. We could then have "surface" which seems inappropriate as a name in the case of audio or video files ! Last thing, how to you link your several files to the appropriate "msDesc" or "recording" ?

     
  • James Cummings

    James Cummings - 2012-06-29
    • assigned_to: nobody --> martindholmes
     
  • Kevin Hawkins

    Kevin Hawkins - 2012-12-19

    In April 2012 Technical Council meeting, it was decided that James Cummings would write to TEI-L asking for people who are interested in participating in a work group on this and on http://purl.org/tei/fr/2507305 . This group should report back to Council with a proposal for discussion at a later meeting.

    But now see http://purl.org/tei/fr/3597335 .

     
  • Laurent Romary

    Laurent Romary - 2012-12-19

    And we are about to issue a new work item proposal in ISO which I would like to see a joint initiative with the TEI. I guess the <audio>-<media>-<facsimile> issue could be dealt with there partially.

     
  • Syd Bauman

    Syd Bauman - 2013-11-13
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,4 +1,3 @@
    -
     Bertrand Gaiffe and others have mentioned the need to record information of audio/video files which are provided in facsimile of the transcribed text.  Particularly to be able to reference zones or ranges in these surrogates.  They appropriated facsimile and zone for this usage.  The point isn't to describe them \(as one would in sourceDesc\) but to have ranges and three and four dimensional zones which can then be referenced as facsimile content elsewhere inside a transcription, exactly the way one currently uses @facs to point to a zone in an image.  If one's facsimile is not an image, but a video/audio/other then it is much more complicated to do this in TEI currently.   While they may have been able to use timeline for this, perhaps the TEI should re-examine the way it handles audio/video/graphic files to make sure that we have some joined-up thinking on the way we handle pointing into portions and zones of multimedia objects.
    
     -James
    
    • status: open --> closed-duplicate
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks