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-3440) ODF 1.2 CD05 Part 1Needs anyIRI datatype

    [ http://tools.oasis-open.org/issues/browse/OFFICE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22978#action_22978 ] 

Dennis Hamilton commented on OFFICE-3440:

Michael, there are no valid URIs that are not valid IRIs.  We worked through this on the list earleri, and Andreas found the relevant parts of the IRI specification where this is established.  However, there are values in the [xmlschema-2] (and XSD 1.1 for sure if it passes as written) anyURI lexical space that are not valid IRIs and are consequently not valid URIs either.

Furthermore, not every valid IRI is a valid URI, but we don't have to go down that road.  There is a prescribed mapping from IRIs to URIs (which needs to be addressed in Part 3).  The mapping that leaves a valid URI.  The URI that has been subject to such mapping can be systematically reconstituted as a valid IRI having Unicode code points not permited directly in URIs.  This reverse mapping may happen, for example, when the URI reaches an end-point resource in a file system that allows more Unicode characters in file-system names than are carried directly in the URI.  (Many such end-points will, for example, convert %20 escapes in the URI to space characters in the file-system name.  spaces are not allowed directly in *either* URIs or IRIs.)

It is these differences in the various lexical spaces (whether validated for or not) that has us need to be precise in what we say shall work..

> ODF 1.2 CD05 Part 1 Needs anyIRI datatype
> -----------------------------------------
>                 Key: OFFICE-3440
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3440
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Sub-task
>          Components: Needs Discussion, Part 1 (Schema), Schema and Datatypes
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
> The rules for IRI references are slightly different than the rules for anyURI.  In particular, anyURI accepts ASCII characters that are excluded from IRI references by [RFC3987].
> Rather than qualify the use of anyURI to be specific to IRIs every place that anyURI is used in the current schema, it is recommended that this be handled in one place by introducing an anyIRI datatype that is  derivative of anyURI with an additional pattern constraint that eliminates the ASCII-corresponding characters that are excluded from IRI references in [RFC3987].

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]