[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=22956#action_22956 ]
Michael Brauer commented on OFFICE-3440:
----------------------------------------
Your comment "Do we have any users clammoring for more than IRI ? How do we demonstrate to those who do want IRI that we have diligently provided for that? " is interesting.
So, let's stop this discussion for a moment and look back why we are using the term IRI. In ODF 1.0 (1st edition) we used the term "URI". We then got a comment from Japan that ODF 1.0 does not support IRIs. We clarified that ODF 1.0 does support IRI, because it anyURI supports IRI. We decided to make this clear by using the term IRI instead of URI from ODF 1.0 2nd edition on.
So, what we got was a request to support IRIs. There never was a request to forbid URIs that are not valid IRIs. The only one who is requesting this is you.
So, rather than introducing a restriction to IRIs that never has been requested, we maybe should better say "URI or IRI" wherever we talk of IRIs at the moment? This would be in the spirit of the original comment, would save us from adding our own IRI datatype definition, and would further save us from adding restriction that have not been requested, and where we don't know what their impact actually is.
> 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]