[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (OFFICE-1825) ISO/IEC JTC 1/SC 34N 1078 : DEFECT REPORT NUMBER JP2-34
[ http://tools.oasis-open.org/issues/browse/OFFICE-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635#action_13635 ]
Dennis Hamilton commented on OFFICE-1825:
-----------------------------------------
DISCUSSION REQUIRED: The RFC 3987 relative IRI reference is not the IRI counterpart of the relative-path URI specified in section 17.5.
This is related to the other discussions of ODF 1.0/../ODF 1.1 section 17.5.
1. The relative IRI reference in RFC 3987 has the following problematic statement in its definitions section:
"An IRI reference may be absolute or relative. However, the 'IRI' that results from such a reference only includes absolute IRIs; any relative IRI references are resolved to their absolute form."
(We have some work to do with regard to how absolute forms within a package are to be construed.
2. RFC 3987 is based on RFC 3986 for what a URI is, not the now-obsolete RFC 2396. There is this useful provision that needs to be aligned with how IRIs may be used to reflect fragments in ODF XML documents of the same package:
"Note that in [RFC2396] URIs did not include fragment identifiers, but in [RFC3986] fragment identifiers are part of URIs."
4. The RFC 3987 relative IRI reference includes IRI forms that begin with "//" and "/" (and "@" too) as well as other characters, including ".".
There is some additional subtlety in RFC 3987 around knowing the scheme. Although the relative IRI references have no explicit scheme, there is a scheme and it needs to be specified for how that (implicit) scheme works inside of a package. There is more that has to be defined about that.
RECOMMENDATION
Resolve this in conjunction with everything else having to do with ODF 1.0/1.1 section 17.5 and relative bits of 17.1 (e.g., manifest:full-path and its relationship to Zip package content item names and how content items are located). This means OFFICE-1826 and other issues related to 17.5 and packaging need to be coordinated.
We could continue to defer for resolution in ODF 1.2, and then figure out what to do in rationalization of ODF 1.0/IS 26300/ODF 1.1.
> ISO/IEC JTC 1/SC 34 N 1078 : DEFECT REPORT NUMBER JP2-34
> ---------------------------------------------------------
>
> Key: OFFICE-1825
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-1825
> 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-34
> QUALIFIER error
> REFERENCES IN DOCUMENT Clause 17.5
> NATURE OF DEFECT "relative-path reference" in 17.5 is never defined in RFC 3987.
> SOLUTION PROPOSED BY THE SUBMITTER Use the correct term "relative IRI reference".
--
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]