Possible misinterpretation of note in §11.3.1.2 Inline Regions.

[nigelmegitt]

The note:

A content element can only be associated with a single region. Consequently, if a content element specifies a region attribute, then any explicit inline region specification is ignored.

is incorrect - we have established through discussion of other issues that some content elements are associated with multiple regions. I think this is about explicit association by specifying a region attribute. Suggest rewording to:

A content element can only specify a single region. Consequently, if a content element specifies a region attribute, then any explicit inline region specification is ignored.

[palemieux]

The PR was closed before the 14 day period was over. I do not have a concern with the contents of the note. It should however not be a note since it sets a normative precedence order.

[skynavga]

This issue and PR was marked editorial. I have just reviewed the details of the change (again) and it is indeed editorial. Therefore, we have followed the rules.

[skynavga]

And, no, it does not set a precedence order, normative or not.

[skynavga]

Just a reminder, an addition, change, or removal of a note is, by definition, editorial, since all notes are non-normative.

[palemieux]

Where is the normative prose that specifies that explicit inline region specification is ignored, if not in this note?

[skynavga]

Repeating myself, any and all information in a note is non-normative in TTML:

2.3 Document Conventions
All paragraphs marked as a Note are considered non-normative.

Therefore, it is NOT normative. If you want to open another issue with a complaint that someone might (foolishly) interpret the text of this note as a normative statement, then feel free to do so, but do not keep reopening this issue.

[skynavga]

I can keep closing this all night. Please file another issue if you wish.

[nigelmegitt]

Where is the normative prose that specifies that explicit inline region specification is ignored, if not in this note?

@palemieux I'm content that this is normatively stated, since the first step in [process inline regions] is:

1. if the [attributes] information item property of B contains a region attribute, then exit this procedure

So I agree this is editorial.