[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=21580#action_21580 ] 

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

Michael, as I commented on OFFICE-3432, we should not be referencing IRI if we want to tie ourselves to XML Schema anyURI as being all right without qualification.  Then what we are supporting is XSD anyURI and we should call it that.  That is, remove reference to RFC3987 and 3986 altogether, then take our lumps on that in Part 3, I suppose, where we need to do something about how we deal with mapping sequences of "/"-separated segment strings to package subdocuments and package files.  I have no objection to this, assuming Part 3 can be made sensible, so long as we are normatively precise about what we allow in anyURI and refer to them accurately.  I do note that the current W3C Recommendations do not use "IRI" at all and we should not in that case either.

With regard to which version of XML Schema Datatypes we make normative reference to, I believe it can only be one that has achieved W3C Recommendation.  I beleive even the W3C says that those are the only ones that should be referenced that way (thinking I've seen words to that in effect in the front matter of W3C Drafts.)



> 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