[OASIS Issue Tracker] Commented: (OFFICE-3440) ODF 1.2 CD05 Part 1Needs anyIRI datatype

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Dennis Hamilton commented on OFFICE-3440:
-----------------------------------------

THE ISSUE:

1. The definition of anyURI in [xmlschema-2] specifies a definition for lexically accepted values.  It also, wisely, states that it is not expected that the well-formed lexical values be checked for as part of schema validation of an instance.

2. That definition allows IRIs to be used as anyURI values.

3. That definition allows MORE THAN IRIs to be used as anyURI values also.  It specities a transformation of those anyURI values to pure URIs that is *not* the same transformation defined for IRIs.  This is not about whether it is checked for.  It is what the lexical form is defined as and what the transformation is.

4. For example, anyURI permits the following non-IRI attribute as providing a lexically well-formed anyURI value:

      xlink:href="http://example.com/Ŧħìš {is} <nöt> α "valid" \segment| in an IRI".  

The only valid IRI for such a target is of a form such as provided in this XML attribute:

      xlink:href="http://example.com/Ŧħìš%20%7Bis%7D%20%3Cnöt%3E%20α%20%22valid%22 ... "

IRI *excludes* the same ASCII-representable characters that are excluded in URIs (except by their %-encodings). IRI does allow many non-ASCII Unicode Characters as shown in the above strings (if preserved by JIRA and displayed correctly in your browser).  IRI also allows *fewer* additional Unicode characters than anyURI does.  

anyURI allows all Unicode characters that are allowed as XML character data so long as a URI would except a %-escaped character in that position.  IRI excludes several blocks of Unicode characters and limits the private-use Unicode characters to query strings only.

5. To legitimize our use of IRI in referring to attributes currently having an anyURI datatype, I propose the creation of the anyIRI datatype as a subtype of anyURI.  For anyIRI, the lexical form is of an anyURI that is restricted to the admissible IRI forms.  In *all* other respects, the provisions for anyURI are the same as those for anyIRI. 

6.  In particular, the excusing of anyURI from validation of instances is preserved for anyIRI.   What consumers do with an anyIRI that does not conform to the anyIRI lexical structure is just as implementation-dependent as what consumers do with an anyURI that does not conform to the anyURI lexical structure.

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