[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=13631#action_13631 ]
Dennis Hamilton commented on OFFICE-1826:
-----------------------------------------
I DON'T THINK THIS RESOLUTION IS COMPLETE ENOUGH
1. How does the URI encoding actually show up in the manifest:full-path attribute that has such path segments?
2. How does the URI encoding actually show up in the Zip content item name (although I presume it and the manifest:full-path value are the same, that's never said anywhere).
3. What directory system are we to assume for normative and interoperability purposes? (I am also concerned that the package might not have a definite file-system location depending on how it is delivered to a consumer.) How are various URI/RI encodings expected to be handled or not? (I also wonder about case sensitivity, allowance of various special characters including spaces, etc.) Finally, the Zip specifications that I've looked at don't appear to specify how one maps a Zip content item name to a file-system name in a hierarchical file system. (I'd like to be mistaken about that.)
4. There are specific passages in RFC3986 (not in 4.2) about "path segments" that are in various technologies (I assume a Zip package counts as one of those) and that how those path segments are processed must be specified in addition to what RFC3986 provides.
My concern is that we need more than a patch, at least for ODF 1.2, and that we can then look at an appropriate way to make errata for 1.0 through 1.1.
> 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.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]