[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=16208#action_16208 ]
Dennis Hamilton commented on OFFICE-1826:
-----------------------------------------
PROPOSE-DISCUSS
Michael, I understand that the manifest:full-path attribute is not an IRI or URI. However, I assume that the IRI is somehow resolved to the names in the Zip entries for individual files of the package when an IRI is used as a relative reference. The question is, how are the special IRI features handled in this context, one that is unique to ODF.
So, if there is IRI encoding in the IRI, the question is, how does it map to the actual name in a manifest:full-path and also to the name in the Zip structure for the file having the same name (or matching initial part, for a manifest:full-path ending in "/")
Re #1: manifest:full-path does not contain an IRI or IRI. It contains a path name.We may want to clarify this, but this is a different issue. (Actually neither its description contain the term IRI/URI nor does it have the anyURI datatype).
*** But we have to be able to figure out the right one given an IRI/URI in a reference from within one of the files.
Re #2: URI encodings do not show up as Zip content items names (see #1).
*** That is not clear. If I am resolving a relative IRI into the same package, are the IRI encodings and URI encodings to be processed first? Maybe so. But as ODF is the authority on whatever the protocol is for path segments that refer into the package, I think we are supposed to say what the game is.
Re #3: Zip files aren't really extracted in order to resolve URI (or IRIs). Only URIs are constructed and processed on a syntactical level. In so far, we don't need to define a "directory system", nor does a file system has to exist. All that is said is that URI/IRI references that have a particular syntax are considered to be references withe the package.
*** I strongly agree with this. However, the definition is given in terms "as if the Zip file had been extracted into a file system" and something has to be said about what that as-if is.
Dennis: Actually, I think the intention of the paragraph in question is clear. If you have a suggestion how to phrase this differently, then I'm glad to discuss this proposal.
Re: #04: To which passages of RFC3986 are you referring?
*** I have to look this up. There is a passage in the specifications about how special applications need to define what their rules are for path segments and resource names.
Dennis: Actually, I think the intention of the paragraph in question is clear. If you have a suggestion how to phrase this differently, then I'm glad to discuss this proposal. Re: #04: To which passages of RFC3986 are you referring?
> 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: Patrick Durusau
> Fix For: 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]