[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (OIC-38) State of Interoperabilitycd03: Improper Assertion of Problem Fix in 4.1(2a).
[ http://tools.oasis-open.org/issues/browse/OIC-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Hamilton updated OIC-38:
-------------------------------
Description:
1. In section 4.1 Priority Areas for Improvement, there is the following item (2a):
"When writing out embedded charts, some implementations write out a link to the embedded chart as: xlink:href="Object 1/". Other implementations write it out as: xlink:href="./Object 1". Only the later is correct."
2. The assertion that a particular case is the correct one is inappropriate in this document. This is a fine example of inconsistency, but assertion of a remedy does not belong here.
3. It is, in fact, arguable that neither may be correct in the face of some subtle rules in ODF packages around how sub-documents are represented in the manifest.xml file and how that may influence what are appropriate URLs for reference to the sub-document as opposed to (the only one of) its files. In particular, the use of a "./" prefix in the URI is irrelevant to the situation described, although it might be inadmissable for other reasons related to provisions of ODF 1.1 Section 17.5.
4. But the key objection is that such an assertion does not belong in this document.
[Personal apology: I did not notice this in cd02 (cd01 rev 02). Since my attention has been very much on ODF 1.2 Part 3 cd01 at this time, it lept out at me. I noticed the problem with the supposed "correct" case some time ago, but I did not notice that it crept into this report.]
was:
1. In section 4.1 Priority Areas for Improvement, there is the following item (2a):
"When writing out embedded charts, some implementations write out a link to the embedded chart as: xlink:href="Object 1/". Other implementations write it out as: xlink:href="./Object 1". Only the later is correct."
2. The assertion that a particular case is the correct one is inappropriate in this document. This is a fine example of inconsistency, but assertion of a remedy does not belong here.
3. It is, in fact, arguable that neither may be correct in the face of some subtle rules in ODF packages around how sub-documents are represented in the manifest.xml file and how that may influence what are appropriate URLs for reference to the sub-document as opposed to (the only) of its files. In particular, the use of a "./" prefix in the URI is irrelevant to the situation described, although it might be inadmissable for other reasons related to provisions of ODF 1.1 Section 17.5.
4. But the key objection is that such an assertion does not belong in this document.
[Personal apology: I did not notice this in cd02 (cd01 rev 02). Since my attention has been very much on ODF 1.2 Part 3 cd01 at this time, it lept out at me. I noticed the problem with the supposed "correct" case some time ago, but I did not notice that it crept into this report.]
Corrected a phrasing around how a subdocument as such is referenced in contrast with any of its files, even if there is only one file.
> State of Interoperability cd03: Improper Assertion of Problem Fix in 4.1(2a).
> -----------------------------------------------------------------------------
>
> Key: OIC-38
> URL: http://tools.oasis-open.org/issues/browse/OIC-38
> Project: OASIS Open Document Format Interoperability and Conformance (OIC) TC
> Issue Type: Bug
> Components: StateOfInteroperability
> Affects Versions: Committee Draft
> Environment: This issue applies to The State of ODF Interoperability Version 1.0 Committee Draft 03, StateOfInterop-v1.0-cd03.odt (.pdf and .html.zip). It also applies to the earlier cd02 rev01 and the cd01 rev02 that was approved as cd02.
> Reporter: Dennis Hamilton
> Priority: Blocker
> Fix For: Committee Draft
>
>
> 1. In section 4.1 Priority Areas for Improvement, there is the following item (2a):
> "When writing out embedded charts, some implementations write out a link to the embedded chart as: xlink:href="Object 1/". Other implementations write it out as: xlink:href="./Object 1". Only the later is correct."
> 2. The assertion that a particular case is the correct one is inappropriate in this document. This is a fine example of inconsistency, but assertion of a remedy does not belong here.
> 3. It is, in fact, arguable that neither may be correct in the face of some subtle rules in ODF packages around how sub-documents are represented in the manifest.xml file and how that may influence what are appropriate URLs for reference to the sub-document as opposed to (the only one of) its files. In particular, the use of a "./" prefix in the URI is irrelevant to the situation described, although it might be inadmissable for other reasons related to provisions of ODF 1.1 Section 17.5.
> 4. But the key objection is that such an assertion does not belong in this document.
> [Personal apology: I did not notice this in cd02 (cd01 rev 02). Since my attention has been very much on ODF 1.2 Part 3 cd01 at this time, it lept out at me. I noticed the problem with the supposed "correct" case some time ago, but I did not notice that it crept into this report.]
--
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]