[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=22937#action_22937 ] 

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

Dennis: Thanks for updating your proposal.

1. Regarding the <dc:description> element and its content: The W3C XSD type system has a value space and a lexical space. The lexical space defines "the set of valid literals for a far a datatype". If we say "The lexical space of anyIRI is finite-length character sequences which satisfy the syntax for [RFC3987] IRI-reference" then we say actually that only values that satisfy the syntax for [RFC3987] are valid values. This to me sounds like a contradiction to saying no validation is required beyond that specified for minimally-conforming processors of the [xmlschema-2] anyURI datatype.

Further, we have so far nowhere used <dc:description> elements in the schema. While RNG in principle allows that, I'm a little bit reluctant to adding this for a single datatype now. My recommendation therefore to say what we want to say in the prose, as we do with other datatypes as well. If we add anything I would recommend c omment like "Any IRI. See part 1, section 18.3".

2. Regarding the name (anyURI vs. anyIRI). Whenever we reference anyURI in the schema, this is just the name of  a define. That is , in the schema we have only <ref name="anyURI"/>. The definition of anyURI is

<define name="anyURI">
    <data type="anyURI"/>
</define>

We therefore can of course document that define in 18.3 rather than 18.2. Indeed, if we add an "anyIRI" define, then the "anyURI" define would not be used anymore, and we can remove it.
Having that said: I still think for consistency with ODF 1.0/1.1 and XSD we should stay with "anyURI". But I will not object to your proposal if you decide to keep the name change. It is just the name of a define. We may also call it "theMostDiscussedODF12Datatype". From syntactic and semantic that would not make a difference.

3. I',m fine with the normative text of "anyIRI" (or to use that as normative text for "anyURI", if we keep the name). I'd like to avoid the term "lexical space" in combination with IRI for the reasons I've stated above. But what about:

"Note: The lexical space of the [xmlschema-2] anyURI datatype permits literals that are not valid IRIs. No validation is required for OpenDocuments anyIRI (or anyURI) other than that specified for minimally-conforming processors of the [xmlschema-2] anyURI datatype."

> 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