Re: Call for Consensus to request transition of IMSC 1.1 to CR2

Hi Cyril,

Thanks. See PR at [1] and comments below.

[1] https://github.com/w3c/imsc/pull/417

>  Is this sentence still needed in the abstract "Both profiles are based
on [SUBM]."

The primary purpose is not to give credit, but instead provide a pedigree
to inform those that have implemented ancestors of the specification. It
could be replaced by the following, which is from Section I.5:

"This specification was derived from the text and image profiles specified
in Section 6 at [CFF]"

> The MPEG DASH example in 5.4 still mentions 1.0.1. It could be updated to
also
> include an example with im2t/im2i.
​
im2t/im2i
​ are not yet defined at [2].

[2] https://www.w3.org/TR/ttml-profile-registry/​


​> I read that "as a replacement of an attribute in the TT Style
Namespacess" and that's probably not the intention.

Yes, it is the intention: the {any attribute in TT Style Namespaces}​ is
replaced by an IMSC style property, since there cannot be two style
properties in an <initial> element.

Alternatively, we could be very explicit, and override the syntax
definition of <initial> to:

<initial
  condition = <condition>
  xml:base = <uri>
  xml:id = ID
  xml:lang = xsd:string
  xml:space = ("default" | "preserve")
  {any attribute in TT Style Namespaces} | itts:fillLineGap |
itts:forcedDisplay | ebutts:linePadding | ebutts:multiRowAlign
  Content: Metadata.class*
</initial>

Best,

-- Pierre




On Mon, Jul 2, 2018 at 1:43 PM Cyril Concolato <cconcolato@netflix.com>
wrote:

> Hi Nigel, all,
>
> I made a first full read of the CR2 and found some minor editorial things:
>
> - Is this sentence still needed in the abstract "Both profiles are based
> on [SUBM]." Not to remove the credit of the original proposal but I don't
> think it's that important to be in the abstract. It could be moved to the
> "Acknowledgment section" for example, which could also be updated.
>
> - The MPEG DASH example in 5.4 still mentions 1.0.1. It could be updated
> to also include an example with im2t/im2i.
>
> - There are 2 rows with "#profile-full-version-2"
>
> - #writingMode-vertical is not listed in alphabetical order
>
> - In Section 7.7, the use of "the rectangular area" is not clear as it is
> not defined. I would say:
> "The Root Container Region of a Document Instance SHALL be mapped to *a
> rectangular area associated with* each image frame of the Related Video
> Object according to the following:"
>
> - " instead of an attribute in the TT Style Namespaces:"
> I read that "as a replacement of an attribute in the TT Style Namespacess"
> and that's probably not the intention. I would remove that text or replace
> "instead of" by "at the same place as" or "as if it were an attribute in
> the TT Style Namespaces, except that it keeps its own namespace".
>
> HTH,
> Cyril
>
> On Fri, Jun 29, 2018 at 9:42 AM Nigel Megitt <nigel.megitt@bbc.co.uk>
> wrote:
>
>> All,
>>
>> As agreed during yesterday's call
>> <https://www.w3.org/2018/06/28-tt-minutes.html#item11>, the open pull
>> requests on IMSC 1.1 have been merged into the editor's draft so the
>> complete document can be reviewed. This means that part of the normal
>> review period for pull requests is being run simultaneously with this call
>> for consensus to request transition.
>>
>> This email is a call for consensus to request transition of IMSC 1.1 to
>> CR2 based on the ED.
>>
>> *Please review the CR2 draft* at
>> https://rawgit.com/w3c/imsc/imsc1.1-cr2/imsc1/spec/ttml-ww-profiles.html
>> with a view to agreeing with the proposal to request transition to CR2.
>>
>> This email is the call for consensus that begins the countdown timer on
>> our decision policy: if no objection to requesting transition is received *by
>> end of Friday 13th July* then the Resolution is passed and I will
>> request the transition to CR2.
>>
>> The dates for deadline for comments and earliest PR in the SoTD were
>> obtained from
>> https://w3c.github.io/spec-releases/milestones/?cr=2018-07-26 : please
>> review those dates as part of your review.
>>
>> For ease of reference the following pull requests were merged recently:
>>
>> Merged #413 Improve description of dependent features and links to
>> feature definitions <https://github.com/w3c/imsc/pull/413>
>> Merged #412 Make TTML2 reference dated
>> <https://github.com/w3c/imsc/pull/412>
>> Merged #396 Apply tt:initial to extension style properties
>> <https://github.com/w3c/imsc/pull/396>
>> Merged #411 Add support for rh/rw <https://github.com/w3c/imsc/pull/411>
>> Merged #403 Add support for tts:rubyAlign='spaceAround'
>> <https://github.com/w3c/imsc/pull/403>
>> Merged #408 Limit number of tts:textShadow <values> to 4
>> <https://github.com/w3c/imsc/pull/408>
>> Merged #397 Apply tts:origin constraints to tts:position
>> <https://github.com/w3c/imsc/pull/397>
>> Merged #406 Add tts:textShadow to HRM glyph definition
>> <https://github.com/w3c/imsc/pull/406>
>> Merged #399 Relax <annotation-position> constraints
>> <https://github.com/w3c/imsc/pull/399>
>> Merged #400 Apply workaround to <img> resize issue
>> <https://github.com/w3c/imsc/pull/400>
>> Merged #395 Refactor features tables
>> <https://github.com/w3c/imsc/pull/395>
>> Merged #398 Improve accessibility of table colours
>> <https://github.com/w3c/imsc/pull/398>
>>
>> Kind regards,
>>
>> Nigel
>>
>>