[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=21684#action_21684 ] 

Michael Brauer commented on OFFICE-3440:
----------------------------------------

Dennis: You are right that
1. anyURI accepts more strings than RFC3987, and
2. that the definition of IRI came out later than XSD 1.0.

But the reason why anyURI allows more strings than RFC3987 is explained in the XSD 1.1 specification I have cited. It's because a consumer in practice cannot verify whether a string is a valid IRI. See my previous comments. But the XSD 1.1 specification anyway states "anyURI represents an Internationalized Resource Identifier Reference (IRI)." So, for the authors of XSD 1.1, it is not an ssue that anyURI accpests more string than RFC3987. The opposite is the case. They intentionally defined anyURI that way. 

Why should it be an issue for us then? Sure, it's not perfect. But we should not try to solve issues for which other experts group say that the cannot be solved in practice. And we also should not confuse readers of the specification by using uncommon terms. I'm sure that if we avoid the term IRI because the definition of anyURI is not perfect we will get comments what anyURI means, whether IRIs are allowed, and why we don't use the proper term IRI.

> 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