[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (OFFICE-3317) ODF 1.2Part 1 5.5.2 <text:changed-region> ID attribute inconsisently available
[ http://tools.oasis-open.org/issues/browse/OFFICE-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21614#action_21614 ]
Dennis Hamilton edited comment on OFFICE-3317 at 9/27/10 12:19 AM:
-------------------------------------------------------------------
This is one that I think should have the schema adjusted differently.
This is, I believe, the correct way for an ODF 1.2 processor to accept ODF 1.0/1.1 documents as ODF 1.2, rather than talking about an illegal case in some way.
It is also the case that having the values be the same when both are present and have the text:id be an NCName will work exactly right assuming that a downlevel application will ignore the xml:id and we don't have a problem with the rule about two attributes having the same ID value in the same XML docoument. (ODF 1.0/1.1 document will already process the text:id as an attribute of type ID.)
I also see that I had a bug in the proposal that is still there. I apologize for that. I will correct it now.
This has also come up in OFFICE-3418. I believe all of these cases of an xml:id beside an optional old-id NCName value and the old-id there by itself as an ID should be handled exactly the same way. The use case is the same. Also, it now makes sense to say the old-id is deprecated, while still permitting an ODF 1.2 processor to accept it appropriately when treating a down-level document version as if it is an ODF 1.2 document.
was (Author: orcmid):
This is one that I think should have the schema adjusted differently.
This is, I believe, the correct way for an ODF 1.2 processor to accept ODF 1.0/1.1 documents as ODF 1.2, rather than talking about an illegal case in some way.
It is also the case that having the values be the same when both are present and have the text:id be an NCName will work exactly right assuming that a downlevel application will ignore the xml:id and we don't have a problem with the rule about two attributes having the same ID value in the same XML docoument. (ODF 1.0/1.1 document will already process the text:id as an attribute of type ID.)
I also see that I had a bug in the proposal that is still there. I apologize for that. I will correct it now.
> ODF 1.2 Part 1 5.5.2 <text:changed-region> ID attribute inconsisently available
> -------------------------------------------------------------------------------
>
> Key: OFFICE-3317
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-3317
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: Needs Discussion, Part 1 (Schema), Public Review, Text
> Affects Versions: ODF 1.2 CD 05
> Environment: This defect applies since at least ODF 1.2 Part 1 CD04. This issue is presented in terms of ODF 1.2 CD05 Part 1.
> Reporter: Dennis Hamilton
> Assignee: Michael Brauer
> Priority: Blocker
> Fix For: ODF 1.2 CD 06
>
>
> 1. Every <table:changed-region> attribute requires an attribute of type ID in order to be referenced by the IDREF text:change-ide attribute in one or more change marks elements.
> However, with the current RNG Schema, there is no <table:changed-region> attribute with a value of type ID when there is no xml:id attribute. That is because the text:id attribute, which must be present when there is no xml:id attribute, has a value of type NCName, not type ID.
> 2. The definition for text:id and xml:id usage in this case does not correspond to what is required to satisfy the requirements for use of ID in accordance with the [XML-ID]. Those conditions surely have precedence over any supplementary conditions in the text of ODF 1.2. In particular, the text of section 19.811.5 specifies that there must always be an xml:id when there is a text:id, but that contradicts the schema, which makes explidit allowance for a standalone text:id attribute on a <text:changed-region> attribute.
> 3. It is not clear how backward compatibility is served by the peculiar requirement to have xml:id and text:id have the same value when both are present. This presumes that a down-level consumer will ignore the xml:id and not consider there to be a violation of [XML-ID] by the apparent appearance of to ID-valued attributes with the same value (according to the down-level schema plus [XML-ID]).
> [NOTE: There are other places where the same device appears to be attempted with regard to introduction of an xml:id attribute that pre-empts the type of another attribute formerly (and in isolation) having a value of type ID. Similar measures may be appropriate for those cases. This issue does not address those potential cases.]
--
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]