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=22872#action_22872 ] 

Michael Brauer commented on OFFICE-3440:

-.5 on the proposal.

1. The description for "anyIRI" in the schema seems to be conflicting. On the one hand it says: "anyIRI values are lexically strings satisfying the [RFC3987] IRI-reference format, a subset of the W3C Schema anyURI lexical form." This sounds like 
it need to be checked whether a value is a valid IRI  in order determine whether an ODF document is valid or not, and I still concur with the authors of the XSD specification, that it is "impractical for processors to check that a value is a context-appropriate URI reference". 
The 2ns sentence then read "anyIRI is subject to the same schema conditions as the anyURI datatype." This sounds like no check is required. 
Maybe we can simply remove this description in the schema and say what we want to say in the prose?

2. Instead of defining a new anyIRI datatype I suggest we move "anyURI" from the section of  "18.2 W3C Schema Datatypes" to "18.3 Other Datatypes". This keeps the number of changes smaller and provides consistency with the ODF 1.0/1.1 specifications bit also with the XSD 1.1 specification.

3. The description of the anyIRI datatype also seems to require that IRIs are checked in order to determine whether an ODF document is conforming or not. What about the following description:

anyURI: An IRI-reference as defined in [RFC3987]. The value space of an anyURI value equals that if the XSD 1.0 anyURI datatype. OpenDocument consumers that depend on anyURI values to be valid IRI values should check anyURI values against RFC3987 and other relevant specifications.

This makes it clear that it is not required to check anyURI values in order to determine whether a document is conforming, and that we also do not require ODF consumers to implement such checks, but that they have the option to reject a document if they find an invalid IRI reference.

That would be a compromise that works for me. Dies it work for you, too?

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