OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

Dennis Hamilton commented on OFFICE-3418:

This discussion is, unfortunately, split across multiple JIRA issues.  My sense of the revised RNG grammar for these obsoleted ID attributes is that 

1. If there is to be an ID, it must be via an xml:id

2. Only If there is an xml:id,  present, the former ID attribute (in this case, form:id) is optional and it is of type NCName (not ID).  
It should also be recommended that the NCName be the same as tne NCName that is the ID value of the xml:id.

3. This provision is intended for backwards compatibility for ODF 1.0 and ODF 1.1 consumers that attempt to process the ODF 1.2 document as if it is ODF 1.1.

There is no meaningful statement to be made in this specificaiton about processing earlier versions of ODF documents as if they are ODF 1.2, since in fact this strict ODF 1.2 requirement makes that impossible.

The original schema allowed a deprecated form:id by itself to be present (and be an ID attribute in that case), but that possibility is not preserved in the proposed change.  For some reason the preservation of upward compatibility in this case, but with standalone form:id and others deprecated is found to be unacceptable.  That is not my position, but I accept that it is the direction these introductions of xml:id have taken.

> 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, Part 1 (Schema)
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Andreas Guelzow 
>            Assignee: Patrick Durusau
>            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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]