ISSUE-276: ttp:version vs ttp:profile vs ttp:contentProfile


ttp:version vs ttp:profile vs ttp:contentProfile

Raised by:
Glenn Adams
Opened on:
The semantics of ttp:version (issue-203) need to be clarified (and very specific) in light of ttp:profile and ttp:contentProfile, which already signal conformance to specific normative provisions and can differentiate between TTML1 and TTML2, which declare different profiles.

If ttp:profile is purely informational, shouldn't it be in the ttm: namespace?
Related Actions Items:
No related actions
Related emails:
  1. Re: {minutes} TTWG Meeting 9/10/2014 (from on 2014-10-10)
  2. {minutes} TTWG Meeting 9/10/2014 (from on 2014-10-09)
  3. {agenda} TTWG Meeting 9/10/2014 (from on 2014-10-08)
  4. {agenda} TTWG Meeting 2/10/2014 (from on 2014-10-01)
  5. ACTION-335: Review issue-276 by 9/10/14 (from on 2014-09-25)
  6. {minutes} TTWG Meeting 27/3/2014 (from on 2014-03-27)
  7. {minutes} TTML Meeting of 24/10/13 (from on 2013-10-24)
  8. RE: TTML Agenda for 24/10/13 (from on 2013-10-23)
  9. TTML Agenda for 24/10/13 (from on 2013-10-23)
  10. ISSUE-276 (version-vs-profile): ttp:version vs ttp:profile vs ttp:contentProfile [TTML2] (from on 2013-09-05)

Related notes:

EBU liaison has requested feature to allow document conformance to (zero to many) profiles to be described using short form aliases to allow references to specifications not wholly defined by schemas or feature designators, i.e. where behaviour is described normatively in documentation.

Nigel Megitt, 23 Oct 2013, 14:02:33

[pal]: ttp:version vs ttp:profile vs ttp:contentProfile

24 Oct 2013, 15:31:03

Raised by PAL

Philippe Le Hégaret, 24 Oct 2013, 15:33:30

Proposal added on behalf of EBU:

* There should be a new element that signals standard conformance.
* This element has a lower bound of 1 and an upper bound of "unbounded".
* The standard is referenced by an URI.
* Conformance is not defined by an explicit profile mechanism but is
only defined by the prose of the referenced standard.
* The URI is an unique identifier and there is no strict requirement
that this resolves to a resources available (e.g. over http).

Example (for easier reading without namespaces):


The name of the element could be different.

Nigel Megitt, 31 Oct 2013, 11:21:55

See also note from Nigel in Issue-323.

Glenn Adams, 31 Jul 2014, 14:55:50

Addressed in

Glenn Adams, 24 Sep 2014, 22:59:43

[nigel]: frans has reviewed.

9 Oct 2014, 14:31:29

Display change log ATOM feed

David Singer <>, Nigel Megitt <>, Chairs, Thierry Michel <>, Philippe Le Hégaret <>, Atsushi Shimono <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 276.html,v 1.1 2019/11/12 10:06:38 carcone Exp $