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=22401#action_22401 ] 

Dennis Hamilton commented on OFFICE-3440:

Here's my highlight:

"*Applications which depend on anyURI values being legal according to the rules of the relevant specifications should make arrangements to check values against the appropriate definitions of IRI, URI, and specific schemes.*"

I believe that is consistent with us saying that we do mean [RFC3987] and no more.  I proposed one way to do that so that we are clear that is what we mean.  

I am not proposing that this is part of schema validation for a document instance, but that we expect IRI References in those anyURI attribute values and that a validator could indeed report on whether there is anything different there.  In fact, even though [xmlschema-2] specifies a specific lexical structure on anyURI, it specifically excludes that structure from requiring schema validation. I do not propose to change that, only be specific that, for use, we mean the subset of anyURI that satisfies the lexical structure of [RFC3987].

We only specify, in part 3, how to resolve IRIs, using the generic methods of [RFC3987] and [RFC3986].  We should be consistent.

If we do not mean to be precise about IRI, we have no right to use "IRI" here.

Furthermore, I object to reasoning based on XSD 1.1, when our specification is normatively based on [xmlschema-2] and XSD 1.1 is no a W3C Recommendation.  [They make it clear why they propose to make anyURI open-ended in the future so that they don't have to revise XSD in order t

I think we now know the nature of our disagreement.

You gave your +0- and I gave my +0- to the 1-2-3 choices.  

> 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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]