[OASIS Issue Tracker] Commented: (OFFICE-1875)style:data-style-name, "must match the name of a data style."

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/OFFICE-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11903#action_11903 ] 

Dennis Hamilton commented on OFFICE-1875:
-----------------------------------------

All right, I shall restate myself a little too.

The first question is, what is a conformant ODF Document?  I can't imagine that it is anyone's intention to have that be the rule for conformant documents (extended or otherwise).

This does not constrain consumers of non-conformant documents.  We have nowhere expressed a statement on that as far as I know (conformant text consumers and the like being defined newly with ODF 1.2).

If there is an ODF Document generator that produces dangling style references by design, that would be amazing.  I see no reason to assume that without an implementer expressing their pain over the specification being tightened on the matter.  I say get it right and see if anyone actually complains during the review process.  It should be in the list of changes in ODF 1.2, of course, so any implementer should find it easily.



> style:data-style-name, "must match the name of a data style." 
> --------------------------------------------------------------
>
>                 Key: OFFICE-1875
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1875
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.2
>            Reporter: Patrick Durusau
>            Assignee: Patrick Durusau
>
> The value of a style:data-style-name attribute is required to match the name of a data style. 
> We don't say what happens if it doesn't match the name of a data style. 
> Moreover, we don't have a similar "must" condition for other instances of attributes with styleNameRef values. 
> Shouldn't we:
> 1) Make it mandatory that all attribute values of type styleNameRef match a style of the appropriate type, and
> 2) Define what happens if an attribute with a value of type styleNameRef fails to match an existing style of the appropriate type?
> Being mindful that the question of *when* the style must exist is an issue. In other words the creation of the reference may come immediately before the creation of the style. Is that OK? 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira