New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify information sets cardinality of attributes. #879
Comments
We could add a note under conventions, but the use of curly braces follows the customary set notation, which means anything any the set. So a kleene operator |
The wording doesn't say any attributes, it says any attribute, singular, which suggests only one is permitted. If |
In TTML1, we had |
The convention used in TTML for specifying element information item syntax comes from [1]. In reviewing the usage there, I see a variety of instances of
So it would seem proper that we add change any attribute to any attributes. Note this is an editorial change only, since we have always intended "any attribute" to mean "any [one or more] attributes" in this context. |
Clarify 'any attribute' language (#879).
Many elements permit
{any attribute in TT Style Namespaces}
or similar language. This test was taken from theinitial
element, as an example. Whereas forContent
the cardinality is indicated, it is omitted for attributes. This could lead to the unintended interpretation that the text permits only a single attribute in the given namespace, rather than any number of such attributes.Raising this and marking as agenda for discussion on the next call. Is there anything we can do to clarify this editorially in the TTML2 and TTML1 3rd Edition specs? For example append a
*
after the curly braces.The text was updated successfully, but these errors were encountered: