ACTION-290: Describe the history for how we got to the signalling needed for mpeg that came from dece for issue-305.

Describe the history for how we got to the signalling needed for mpeg that came from dece for issue-305.

State:
closed
Person:
Mike Dolan
Due on:
May 29, 2014
Created on:
May 22, 2014
Related emails:
  1. {minutes} TTWG Meeting 14/8/2014 (from nigel.megitt@bbc.co.uk on 2014-08-14)
  2. {agenda} TTWG Meeting 14/8/2014 (from nigel.megitt@bbc.co.uk on 2014-08-13)
  3. Re: {agenda} TTWG Meeting 7/8/2014 (from pal@sandflow.com on 2014-08-06)
  4. {agenda} TTWG Meeting 7/8/2014 (from nigel.megitt@bbc.co.uk on 2014-08-06)
  5. {agenda} TTWG Meeting 31/7/2014 (from nigel.megitt@bbc.co.uk on 2014-07-30)
  6. {agenda} TTWG Meeting 24/7/2014 (from nigel.megitt@bbc.co.uk on 2014-07-23)
  7. {agenda} TTWG Meeting 17/7/2014 (from nigel.megitt@bbc.co.uk on 2014-07-16)
  8. {agenda} TTWG Meeting 10/7/2014 (from nigel.megitt@bbc.co.uk on 2014-07-09)
  9. RE: {agenda} TTWG Meeting 19/6/2014 (from mdolan@newtbt.com on 2014-06-18)
  10. {agenda} TTWG Meeting 19/6/2014 (from nigel.megitt@bbc.co.uk on 2014-06-18)
  11. RE: {agenda} TTWG Meeting 12/6/2014 (from mdolan@newtbt.com on 2014-06-12)
  12. Re: {agenda} TTWG Meeting 12/6/2014 (from pal@sandflow.com on 2014-06-11)
  13. Re: {agenda} TTWG Meeting 12/6/2014 (from nigel.megitt@bbc.co.uk on 2014-06-11)
  14. Re: {agenda} TTWG Meeting 12/6/2014 (from pal@sandflow.com on 2014-06-11)
  15. Re: {agenda} TTWG Meeting 12/6/2014 (from nigel.megitt@bbc.co.uk on 2014-06-11)
  16. {agenda} TTWG Meeting 12/6/2014 (from nigel.megitt@bbc.co.uk on 2014-06-11)
  17. RE: {agenda} TTWG Meeting 5/6/2014 (from mdolan@newtbt.com on 2014-06-04)
  18. {agenda} TTWG Meeting 5/6/2014 (from nigel.megitt@bbc.co.uk on 2014-06-04)
  19. {agenda} TTWG Meeting 29/5/2014 (from nigel.megitt@bbc.co.uk on 2014-05-28)
  20. {minutes} TTWG Meeting 22/5/2014 (from nigel.megitt@bbc.co.uk on 2014-05-22)

Related notes:

[nigel]: Nigel to add any requirements from other places.

22 May 2014, 14:25:19

The ISO-layer namespace and schema_location fields were defined by DECE as a way to provide additional ISO-layer signaling about the content of an XML document track - that is what the instance document(s) conformed to. Arguably it could also be what decoder requirements were, but that was not explicitly considered then. FYI, whether the track is a CFF text profile or a CFF image profile was signaled in the metadata. But the document could also contain SMPTE closed caption information and other extension namespaces not easily enumerated in advance without a registry.

XML signals instance document conformance through the use of namespaces and schemas. A list of namespaces in use in the document is useful and was added as a signal field. This would be able to signal that a track document had both. e.g. tt and smpte namespaces.

But it was felt that more information about any profiling of the namespaces would be (optionally) better.

The TTML "profile" was attractive except that: 1) it is currently specific to TTML and not XML in general, and 2) see: https://www.w3.org/AudioVideo/TT/tracker/issues/263

The schema_location field could uniquely identify a profile of the namespace that the document conformed to. The schema_location values are not a managed value space, but a fully qualified URI would accomplish that if there was concern over collisions.

When later defining the ISO sample entry for XML-based timed text in ISO 14496-12, AMD2 & 14496-30 it was deemed desirable to remain compatible with the DECE syntax in use.

There is currently no ISO sample entry specific to TTML. Tracks with TTML documents are minimally signaled with namespace="http://www.w3.org/ns/ttml".

Mike Dolan, 28 May 2014, 17:52:14

Display change log.


David Singer <singer@apple.com>, Nigel Megitt <nigel.megitt@bbc.co.uk>, Chairs, Thierry Michel <tmichel@w3.org>, Philippe Le H├ęgaret <plh@w3.org>, Atsushi Shimono <atsushi@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $