ISSUE-315: Maximum number of regions should be a processor constraint
Maximum number of regions should be a processor constraint
Maximum number of regions should be a processor constraint
- State:
- OPEN
- Product:
- TTML IMSC 2.0
- Raised by:
- Nigel Megitt
- Opened on:
- 2014-05-21
- Description:
- The requirement in §4.6.3 [1] to limit the number of presented regions in a given intermediate synchronic document should be expressed as a minimal processing constraint rather than a maximal document constraint in order not to limit future expansion. Example wording:
Presentation processors SHALL be able to present 4 or more regions within any given intermediate synchronic document.
This would permit sub-profiling of IMSC in other environments such that more than 4 regions are permitted within an intermediate synchronic document if a use case for that should arise, while still ensuring that all documents authored to meet the maximum of 4 regions constraint can be successfully processed.
[1] http://www.w3.org/TR/ttml-imsc1/#maximum-number
This may require a processor profile to be created for IMSC1, as noted as a possibility in ISSUE-307. - Related Actions Items:
- No related actions
- Related emails:
- {agenda} TTWG Meeting 25/9/2014 (from nigel.megitt@bbc.co.uk on 2014-09-24)
- Re: {agenda} TTWG Meeting 11/9/2014 (from glenn@skynav.com on 2014-09-10)
- {agenda} TTWG Meeting 11/9/2014 (from nigel.megitt@bbc.co.uk on 2014-09-10)
- {agenda} TTWG Meeting 4/9/2014 (from nigel.megitt@bbc.co.uk on 2014-09-03)
- {agenda} TTWG Meeting 21/8/2014 (from nigel.megitt@bbc.co.uk on 2014-08-20)
- Re: New Change Proposal 28 on IMSC 1: Profile refactoring (from nigel.megitt@bbc.co.uk on 2014-08-14)
- Re: New Change Proposal 28 on IMSC 1: Profile refactoring (from pal@sandflow.com on 2014-08-14)
- {agenda} TTWG Meeting 14/8/2014 (from nigel.megitt@bbc.co.uk on 2014-08-13)
- New Change Proposal 28 on IMSC 1: Profile refactoring (from nigel.megitt@bbc.co.uk on 2014-08-08)
- Re: {agenda} TTWG Meeting 7/8/2014 (from pal@sandflow.com on 2014-08-06)
- {agenda} TTWG Meeting 7/8/2014 (from nigel.megitt@bbc.co.uk on 2014-08-06)
- {agenda} TTWG Meeting 31/7/2014 (from nigel.megitt@bbc.co.uk on 2014-07-30)
- {minutes} TTWG Meeting 19/6/2014 (from nigel.megitt@bbc.co.uk on 2014-06-19)
- RE: {agenda} TTWG Meeting 19/6/2014 (from mdolan@newtbt.com on 2014-06-18)
- {agenda} TTWG Meeting 19/6/2014 (from nigel.megitt@bbc.co.uk on 2014-06-18)
- IMSC feature designators (from nigel.megitt@bbc.co.uk on 2014-06-13)
- RE: {agenda} TTWG Meeting 12/6/2014 (from mdolan@newtbt.com on 2014-06-12)
- Re: {agenda} TTWG Meeting 12/6/2014 (from pal@sandflow.com on 2014-06-11)
- Re: {agenda} TTWG Meeting 12/6/2014 (from nigel.megitt@bbc.co.uk on 2014-06-11)
- Re: {agenda} TTWG Meeting 12/6/2014 (from pal@sandflow.com on 2014-06-11)
- Re: {agenda} TTWG Meeting 12/6/2014 (from nigel.megitt@bbc.co.uk on 2014-06-11)
- {agenda} TTWG Meeting 12/6/2014 (from nigel.megitt@bbc.co.uk on 2014-06-11)
- RE: {agenda} TTWG Meeting 5/6/2014 (from mdolan@newtbt.com on 2014-06-04)
- {agenda} TTWG Meeting 5/6/2014 (from nigel.megitt@bbc.co.uk on 2014-06-04)
- {agenda} TTWG Meeting 29/5/2014 (from nigel.megitt@bbc.co.uk on 2014-05-28)
- {agenda} TTWG Meeting 22/5/2014 (from nigel.megitt@bbc.co.uk on 2014-05-21)
- ISSUE-315 (Maximum number of regions should be a processor constraint): Maximum number of regions should be a processor constraint [TTML IMSC 1.0] (from sysbot+tracker@w3.org on 2014-05-21)
Related notes:
document (content) and processor constraints should be separated here, and they can be distinct numbers; e.g., one could define a content profile that limits the number of regions expressed in any given ISD, while at the same time defining a processor profile that requires support for a minimum number of regions in an ISD, and the numbers could be different;
Glenn Adams, 23 May 2014, 23:26:38I've added a suggested feature designator for this along with those for the HRM in Issue-319.
Nigel Megitt, 13 Jun 2014, 16:38:49See also Change Proposal 28 [1].
[1] https://www.w3.org/wiki/TTML/changeProposal028
This issue is non-blocking on the CR publication. However it is dependent on defining the processor profile, which is not done in IMSC 1 and not available in combination with the content profile in TTML1. Deferring this issue to IMSC 2.
Nigel Megitt, 28 Nov 2014, 15:55:58(NB CP28 was withdrawn on 2014-09-05)
Nigel Megitt, 28 Nov 2014, 15:56:16Display change log