RE: TTML Schema Verification

I see. Yes, the full schema will help with that.  Although it is permissible
to add private metadata (although not like that), so I don't know how you
police that since you can still create equivalent, conforming TTML.

 

I mentioned the subsets since there are tighter schemas available.  The W3C
schemas can generate a number of false positives - using xs:string datatypes
rather than enum and regex.

 

                Mike

 

From: David Ronca [mailto:dronca@netflix.com] 
Sent: Wednesday, February 13, 2013 5:03 PM
To: public-tt@w3.org
Subject: RE: TTML Schema Verification

 

> Any chance they are really trying to conform with a subset profile such as

SDP-US or CFF-TT?

 

We are seeing obvious schema issues like this: tts:textAlign="after".  Also
seeing the positioning model below that does not appear to be a schema
error, but is not defined in the spec: 

 

<p begin="00:00:01.40" end="00:00:04.13" region="speaker"
tts:textAlign="right"><metadata ccrow="12" cccol="8"/>[crowd cheering]</p>