[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (OFFICE-3440) ODF 1.2CD05 Part 1 Needs anyIRI datatype
[ http://tools.oasis-open.org/issues/browse/OFFICE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22726#action_22726 ]
Dennis Hamilton edited comment on OFFICE-3440 at 10/27/10 7:16 PM:
-------------------------------------------------------------------
Michael, I promised that there will be no invalidation of anyIRI that is not an invalidation of anyURI.
I will correct the proposal to honor that assurance, using language derived from what is said for anyURI.
This proposal will work just fine if there is a future update to rely on XSD 1.1 also.
Also, how can an [RFC3987] IRI be "non-standard?" It's the only IRI standard there is. I can't imagine any future RFC breaking [RFC3987], especially where it matters to us inside ODF packages.
was (Author: orcmid):
Michael, I promised that there will be no invalidation of anyIRI that is not an invalidation of anyURI.
I will correct the proposal to honor that assurance, using language derived from what is said for anyURI.
This proposal will work just fine if there is a future update to rely on XSD 1.1 also.
> 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]