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=22916#action_22916 ] 

Dennis Hamilton commented on OFFICE-3440:

1. The description in the schema is just a comment.   [xmlschema-2] specifies what an anyURI is lexically.  I just say what an anyIRI is lexically and that it is a subset of what an anyURI is lexically.   What is well-formed versus what is valid are different.  anyURI is not required to be validated in [xmlschema-2], but they do say what the well-formedness condition is.  The description does not change that.

2. Moving anyURI to Other Datatypes is incorrect, because the schema declares that it uses the [xmlschema-2] datatypes.  There is no way to say anyURI is anything different than that in the scema, so we should not move it in the specification.

3. I don't agree about adding a statement that consumers should check anyURI values, and to say "other relevant specifications" makes no sense at this point.   I think what consumers do that is beyond what the schema requires is up to them.  Not checking something unless it is being used seems appropriate, and it is likely that it is whatever is used for IRI resolution that is going to do the checking, either in the operating system or at the destination domain (if any).

4. I don't know if the "value space" terminology is used in [xmlschema-2] for anyURI.  What I see is this:

The - lexical space-  of anyURI is finite-length character sequences which, when the algorithm defined in Section 5.4 of [XML Linking Language] is applied to them, result in strings which are legal URIs according to [RFC 2396], as amended by [RFC 2732]. 
and later, 
Note:  Each URI scheme imposes specialized syntax rules for URIs in that scheme, including restrictions on the syntax of allowed fragment identifiers. Because it is impractical for processors to check that a value is a context-appropriate URI reference, this specification follows the lead of [RFC 2396] (as amended by [RFC 2732]) in this matter: such rules and restrictions are not part of type validity and are not checked by - minimally conforming-  processors. Thus in practice the above definition imposes only very modest obligations on - minimally conforming-  processors. 

I can use the term "lexical space" if you like.

What I would say is this:

The lexical space of anyIRI is finite-length character sequences which satisfy the syntax for [RFC3987] IRI-reference, a subset of the lexical space of anyURI.  However, no validation is required beyond that specified for minimally-conforming processors of the [xmlschema-2] anyURI datatype.

When we go from [xmlschema-2] to [xsd1.1], that statement should still work.  If there is a later RFC for IRI, I suspect we can substitute that 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]