OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (OFFICE-2685) ODF 1.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:comment-tabpanel&focusedCommentId=20618#action_20618 ] 

Dennis Hamilton commented on OFFICE-2685:

It needs to be clear here and in Part 1 (perhaps Part 2) that 

 1. There are only URIs.  IRIs are URIs to which a specific convention has been applied so that characters not permitted in URIs are encoded in a particular way that is permissible:  URIs are limited in the character repertoire which can be used (essentially a subset of the 95 graphic Basic Latin characters), and a number of the characters are reserved for special purposes and are not permitted to be freely chosen where they are forbidden or where they have a delimiter purpose.

  1.1 If the character is not one permitted to be freely chosen at a particular place in a URI, the following procedure is applied to create a permissible URI:

  1.2 The character's Unicode Code Point is expressed in a UTF-8 encoding sequence.  Then each byte of the UTF-8 sequence that is not a permitted character at that place in the URI is encoded by the %-encoding technique provided for URIs.  The entire UTF-8 sequence, with necessary encodings, is then used in place of the original not-permitted character.  These are the only cases where %-encoding should be applied (according to the IRI specification).

  1.3 This becomes the URI.  It is presumably what is submitted to a URI resolver, if any.  This needs to be taken into account when we have resolvers that work with relative URI References.

  1.4 Here is a proper URI that has IRI encoding:


Here is another:


And one more:


as a reminder that SP is not a permitted character in any segment of a clean URI and it is consequently subject to this encoding.

2. Note that the specifications in W3C schema for the anyURI datatype (which is specifically for URI references) and in other specifications where URIs are allowed, such as XHTML for xhtml:href,  have very specific conditions on what is admissable and, in the case of xhtml:href, how the equivalent of IRI-encoding is done even though the IRI specification is not referenced.  I suspect there are impacts with regard to RDF and RDFa as well.

3. For ODF 1.2, we have to understand how a correct URI is formed from a relative reference in an XML document within a package, including understanding what the implicit base is as an actual URI, and then how these references are used to produce a string that matches the value of a manifest:full-path attribute in the manifest.xml.  We then need to know how the manifest:full-path for a package file (not a subdocument) is expected to match the Zip filename for the packaged form of the package file.  (I am presuming that there is no package file for a subdocument and these are always differentiated by having a full-path attribute ending in "/".)

> 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
>             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]