[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (OFFICE-2685) NEEDS-DISCUSSION: ODF1.2 Part 3 "IRI" and "relative IRI" used throughout are never defined
[ http://tools.oasis-open.org/issues/browse/OFFICE-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Hamilton updated OFFICE-2685: ------------------------------------ Proposal: 1. Add [RFC3987] to the Normative References. 2. Define IRI and relative IRI in some way (a terminology/nomenclature entry would be helpful), with reference to the applicable definitions in [RFC3987] and/or in a specific portion of Part 3, such as section 2.7. 3. Specify when and how IRI-%-encoding kicks in for URI path segments that are within the package and for URI references that end in the package. 4. Be careful about speaking of IRIs vs IRI-encoding in URIs and URIs generally. 5. Make sure we have accounted for normative provisions of [RFC3986] and [RFC3987], of the anyURI datatype, and of whatever it is we say manifest:full-path is and what its relationship to the name recorded for a file as a data unit of the Zip archive. was: 1. Add [RFC3987] to the Normative References. 2. Define IRI and relative IRI in some way (a terminology/nomenclature entry would be helpful), with reference to the applicable definitions in [RFC3987] and/or in a specific portion of Part 3, such as section 2.7. 3. Specify when and how IRI-%-encoding kicks in for URI path segments that are within the package and for URI references that end in the package. 4. Be careful about speaking of IRIs vs IRI-encoding in URIs and URIs generally. 5. Make sure we have accounted for normative provisions of [RFC3986] and [RFC3987], of the anyURI datatype, and of whatever it is we say manifest:full-path is and what its relationship to the name recorded for a file as a data unit of the Zip archive. 3. [removed stray item number in the Proposal text] > NEEDS-DISCUSSION: ODF 1.2 Part 3 "IRI" and "relative IRI" used throughout are never defined > ------------------------------------------------------------------------------------------- > > Key: OFFICE-2685 > URL: http://tools.oasis-open.org/issues/browse/OFFICE-2685 > Project: OASIS Open Document Format for Office Applications (OpenDocument) TC > Issue Type: Bug > Components: Packaging, Part 3 (Packages), Schema and Datatypes > Affects Versions: ODF 1.2 CD 05 > Environment: This applies to all versions of OpenDocument-v1.2-part3-cd1 through -rev04. It also impacts ODF 1.2 Part 1 and ODF 1.2 Part 2 wherever anyURI or equivalent datatype is used in a relative reference. > Reporter: Dennis Hamilton > Assignee: Dennis Hamilton > Fix For: ODF 1.2 CD 06 > > > The terms "IRI" and "relative IRI" are used throughout ODF 1.2 Part 3. > 1. There are no definitions offered for these terms. > 2. There are no references (normative or otherwise) to sources on this terminology (although [RFC3987] would appear to be a good choice). > 3. The manner in which IRIs are to be mapped to URIs in those places where resolution involves URI segments within a package is not defined, nor is the relationship to IRI-encoding in URIs accounted for in the definition of (a) the manifest:full-path attribute or (b) the format for names of files in the ZIP data units that carry files within the ZIP archive. In particular, there should be attention to [RFC3987] sections 6.2-6.4, not merely 6.5. -- 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]