[annodex-dev] captioning and cmml

[Ralph Giles]

On Mon, Dec 10, 2007 at 07:23:33AM +1100, Silvia Pfeiffer wrote:

> > whole. What about adding a way to "<import>" a particular track
> > attribute value as an explicit child of a <stream> element?
> 
> I don't understand this.

The <stream> element let a CMML document specify what elements end up 
multiplexed in a physical Ogg bitstream. How would you say, for 
instance, that particular annotation tracks should be embedded as a
separate logical bitstream? Or can a CMML document only embed itself
in a physical stream?

> > Having a place to hang track-level metadata would also let us add a
> > "contentrole" attribute to define additional semantics, like
> > distinguishing dialog translation from commentary from interpretation
> > for the visually impared...it's also important to know which of several
> > tracks that match your user's language preference to use as a default.
> 
> Is the "track" attribute enough for this? I would think so, but I may
> be missing something.

My question was about how the player picks which track to display. It 
could display the attribute value directly, and the user might be able 
to pick based on those if they're named something like english_commentary,
programmerese punctuation aside. But one of the things I've always 
wanted for an Ogg subtitle solution is to do sane language 
autoselection. So at the very least, we need a standard set of track 
attribute values for machine interpretation. I was suggesting it would 
be better to be able to define through another element, the way <import> 
does, a user-visiable name for the track, a machine parsable language 
code, and a (currently undefined) role like dialog, commentary, etc. so 
that could also be machine parsed.

Does that make sense?

 -r