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=21620#action_21620 ] 

Michael Brauer commented on OFFICE-3440:

Dennis: Sorry, but I really do not understand what the issue is. We have attributes that are IRIs, the W3C defines a datatype for these attributes (and call that anyURI). Why should we then not call the attribute values IRI? Is it because the attribute theoretically could be not a valid IRI? That seems to be a week argument for me for confusing readers with using a term anyURI? And I bet if would make that change, we get comments why we don't call the attributes, questions whether IRIs are allowed, etc. Remember: We are using the term IRI because we got a comment for this for the ODF 1.0 ISO ballot. We did a research, and RFC3987 explicitly said that the anyURI datatype supports IRIs.

What we also must not forget here is that the schema is only one source of constrains for valid documents. If the schema permits non-valid IRI that is not an issue. We have other places where the schema allows more than what is actually allowed. Vice versa, it would be an issue if the schema disallows some valid IRI. Because of the complex topic I once again strongly recommend that we don't try to solve issues in ODF that in the eyes of the IETF and W3C seems not to exist. They are the experts. What's fine fort them should work for us.

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