Menu

#416 Need for one or more elements to handle audio and video

AMBER
closed-accepted
5
2013-01-14
2012-12-18
No

A lengthy discussion, beginning on TEI-L:

http://tei-l.970651.n3.nabble.com/some-questions-about-non-textual-components-and-media-td4022926.html

and moving to TEI-Council:

http://lists.village.virginia.edu/pipermail/tei-council/2012/016805.html

suggests that it would be a good idea to have a <media> element which could be used in the same way <graphic> is used for images. Other suggestions:

@mimeType should be obligatory

@medium should be obligatory, with values including video, audio etc.

The element should remain simple, like <graphic> (which might now be seen as syntactic sugar for it), and not venture into the complexities of similar HTML5 elements

Discussion

  • James Cummings

    James Cummings - 2013-01-08

    Assigning to rahtz to push forward if council agrees. Group set to RED for now as needs a lot more discussion and clarification. -JamesC

     
  • James Cummings

    James Cummings - 2013-01-08
    • milestone: --> 871207
    • assigned_to: nobody --> rahtz
     
  • Sebastian Rahtz

    Sebastian Rahtz - 2013-01-08

    I am assuming this waits for the next Council f2f meeting, since its RED

     
  • Lou Burnard

    Lou Burnard - 2013-01-08
    • milestone: 871207 --> AMBER
     
  • Lou Burnard

    Lou Burnard - 2013-01-08

    I don't think this is RED. It really didn't seem very difficult to implement as outlined above, so I have taken the liberty of implementing it at rev 11358. Feel free to revert or modify as needed, of course. I note that this has been an outstanding request for many months now and it seems daft not to deal with it when we have a consensus. Leaving ticket open for further discussion anyway.
    See also previous ticket 2724997 (from 2009) which could be closed along with this one.

     
  • Sebastian Rahtz

    Sebastian Rahtz - 2013-01-08

    I am not entirely happy with using @type instead of the compulsory @medium suggested;
    and I do think @mimeType should be compulsory. allowing for <media> with only the @url being compulsory is asking for trouble, I reckon.

    i think theres a reason this wasnt GREEN :-}

     
  • Martin Holmes

    Martin Holmes - 2013-01-08

    @Sebastian: I agree. We can always add @medium later (once we've finished arguing about the values it should have), but how about making @mimeType compulsory right now (before the release)?

    @Lou: where did the idea of @scale come from? It seems entirely concerned with output rendering, so I'm not sure it belongs there.

     
  • Sebastian Rahtz

    Sebastian Rahtz - 2013-01-08

    yes. make @mimeType compulsory, leave out att.typed for now until there's a need, or while we debate @medium.

    @scale is copied from <graphic>. it's been there for ages, right or wrong, and if <media> is to be a superset of <graphic>, it is easier to let it stay

     
  • Martin Holmes

    Martin Holmes - 2013-01-08

    I'd be inclined to leave it as a member of att.typed, just because whether or not @mimeType and (later) @medium is there, people will surely ask for it. It's a place to put info about codecs, for instance, which people may well wish to do.

    Doh on @scale. Sorry Lou.

     
  • Sebastian Rahtz

    Sebastian Rahtz - 2013-01-14
    • status: open --> closed-accepted
     
  • Sebastian Rahtz

    Sebastian Rahtz - 2013-01-14

    i think we are done with this. the <media> element now mandates @mimeType, and doesn't use @type to distinguish formats. we'll see how the public reacts to it...