[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (OFFICE-1826) ISO/IEC JTC 1/SC 34N 1078 : DEFECT REPORT NUMBER JP2-35
[ http://tools.oasis-open.org/issues/browse/OFFICE-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565#action_13565 ]
Michael Brauer commented on OFFICE-1826:
----------------------------------------
I think we may indeed turn this paragraph into a note. But we may combine the resolution of this issue with the other defect reports we got for 17.5.
The paragraphs in question read:
-----
A relative-path reference (as described in §6.5 of [RFC3987]) that occurs in a file that is contained in a package has to be resolved exactly as it would be resolved if the whole package gets unzipped into a directory at its current location. The base IRI for resolving relative-path references is the one that has to be used to retrieve the (unzipped) file that contains the relative-path reference.
All other kinds of IRI references, namely the ones that start with a protocol (like http:), an authority (i.e., //) or an absolute-path (i.e., /) do not need any special processing. This especially means that absolute-paths do not reference files inside the package, but within the hierarchy the package is contained in, for instance the file system. IRI references inside a package may leave the package, but once they have left the package, they never can return into the package or another one.
-----
One issue is that the term "relative-path reference" is not formally defined by §6.5 of [RFC3987], but by §4.2 of [RFC3986], which we reference in the ODF 1.0 OASIS standard . As a result, "relative-path" is mostly interpreted as "relative URI", which it isn't.
My suggestion how to resolve this was some time ago:
----
A relative-path reference (as defined in §4.2 of [RFC3986], except
that it may contain the additional characters that are allowed in IRI
references [RFC3987]) that occurs in a file that is contained in a
package has to be resolved exactly as it would be resolved if the whole
package gets unzipped into a directory at its current location. The base
IRI for resolving relative-path references is the one that has to be
used to retrieve the (unzipped) file that contains the relative-path
reference.
Every IRI reference that is not a relative-path reference does not
need any special processing. This especially means that absolute-paths
do not reference files inside the package, but within the hierarchy the
package is contained in, for instance the file system. IRI references
inside a package may leave the package, but once they have left the
package, they never can return into the package or another one.
----
As of today, I would keep only the first two sentences of this paragraph as a note.
The intention of the last sentence was to clarify that ODF does not specify a method how to reference files in a package from "the outside", but this actually seems to cause more confusion than it solves.
If further suggest that we replace the "IRI" with "URI/IRI". This solves the issue that ODF 1.0 uses the term URI, wile ISO 26300 says IRI.
My proposed resolution therefore is:
----
A *relative-path* reference (as defined in ァ4.2 of [RFC3986], except
that it may contain the additional characters that are allowed in IRI
references [RFC3987]) that occurs in a file that is contained in a
package has to be resolved exactly as it would be resolved if the whole
package gets unzipped into a directory at its current location. The base
URI/IRI for resolving relative-path references is the one that has to be
used to retrieve the (unzipped) file that contains the relative-path
reference.
URI/IRI references that are not a relative-path reference do not
need any special processing. This especially means that absolute-paths
do not reference files inside the package, but within the hierarchy the
package is contained in, for instance the file system.
-----
> ISO/IEC JTC 1/SC 34 N 1078 : DEFECT REPORT NUMBER JP2-35
> ---------------------------------------------------------
>
> Key: OFFICE-1826
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-1826
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Affects Versions: ODF 1.0 (second edition)
> Reporter: Robert Weir
> Assignee: Michael Brauer
> Fix For: ODF 1.2, ODF 1.0 Errata 02
>
>
> Transcribed from http://www.itscj.ipsj.or.jp/sc34/open/1078.htm
> Original author: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@asahi-net.or.jp>
> DEFECT REPORT NUMBER JP2-35
> QUALIFIER clarification required
> REFERENCES IN DOCUMENT Clause 17.5
> NATURE OF DEFECT The last paragraph in 17.5 should be a non-normative note, since the behaviour of absolute IRI references is specified in RFC 3986 and RFC 3987.
> SOLUTION PROPOSED BY THE SUBMITTER Rewrite this paragaraph as a note.
--
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]