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=23021#action_23021 ] 

Michael Brauer commented on OFFICE-3440:

Dennis: Patrick has proposed to have a vote on this issue, and this works for me.

But I would like to state here that I have no objections to changing the description of "anyURI" to

An IRI-reference as defined in [RFC3987].

[Note: The procedure for resolution of anyIRI values that are not IRI values is undefined] 

I don't consider it to be useful to rename "anyURI" to "anyIRI", but if other TC members are also in favor  of this change (of if at least no one objects), I can concur to that.

I consider a change of  "URIorSafeCURIE" to "URIorSafeCURIE" to be not reasonable. We are intentionally using that datatype and name to be compatible with RDFa.

All I'm objecting to is any language that makes a check of IRIs to be required for checking document conformance, since that is in my opinion and in the opinion of the W3C impracticable.

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