[OASIS Issue Tracker] Commented: (OFFICE-3418) 19.278 form:id seemsto be inconsistent

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

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

Michael Stahl  commented on OFFICE-3418:
----------------------------------------

well, the sentence you object to prescribes how an invalid document is to be processed.

because the xml:id attribute is new in ODF1.2, it is easy to imagine that such invalid documents could be
created by applications loading an ODF1.1 document into a DOM and storing it as ODF1.2.

i think keeping this stipulation (with the "should" keyword) is a good idea, because it will increase the real-world interoperability.


> 19.278 form:id seems to be inconsistent
> ---------------------------------------
>
>                 Key: OFFICE-3418
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3418
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Forms
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Andreas Guelzow 
>            Priority: Minor
>             Fix For: ODF 1.2 CD 06
>
>
> In 19.278 form:id we have
> "If there is no xml:id attribute value, then a form:id attribute should be processed as it were an xml:id attribute."
> and later
> "An element shall not have an form:id attribute if it has no xml:id attribute value."
> So in view of the second sentence, the first one doesn't make sense: if there is no xml:id attribute then there cannot be a form:id attribute that could be processed as it were an xml:id attribute.

-- 
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