[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (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:all-tabpanel ]
Dennis Hamilton updated OFFICE-3440:
------------------------------------
Resolution:
[edited 2010-11-04T18"26Z to relax to only what anyURI says apart from notes]
[edited 2010-11-03T15:22Z to use "lexical space."]
1. SCHEMA UPDATE
1.1 Delete the definition
"""
<define name="anyURI">
<data type="anyURI" />
</define>
"""
1.2 Add, in the block of schema definitions based on [xmlschema-2] but not in [xmlschema-2],
the definition
"""
<define name="anyIRI">
<data type="anyURI" />
<dc:description>
ODF 1.2 makes use of the [xmlschema-2] anyURI as one means for carrying
[RFC3987] IRI-references. See ODF 1.2 Part 1 section 18.3.
</dc:description>
</define>
1.3 replace every occurrence of '<ref name="anyURI"/>' with '<ref name="anyIRI"/>'.
1.4 replace every occurrence of 'URIorSafeCURIE' with 'IRIorSafeCURIE' (2 places) only if that is still compatible with the reference to [RDFa] in section 18.3.36.
2. TEXT CHANGES
2.1 Uses of "IRI". All of the uses of IRI in the text can remain, except as identified below.
2.2 In 18,3.36, URIorSafeCURIE
(a) Use IRI only if that is permissible under the definition in [RDFa] section 7.
(b) Optionally, change the name to IRIorSafeCURIE if that is done in the schema and it is compatible with the definition in [RDFa] section 7.
2.3 In secition 18.2 WeC Schema Datatypes, delete "anyURI" from that list.
2.3 Add after 18.3.1 angle, a new entry,
"""
18.3.2 anyIRI
An [xmlschema-2] anyURI. The value should be an IRI-reference string as defined in [RFC3987].
[Note: The procedure for resolution of anyIRI values that are not IRI values is undefined]
"""
was:
[edited 2010-11-03T15:22Z to use "lexical space."
1. SCHEMA UPDATE
1.1 After the definition
"""
<define name="anyURI">
<data type="anyURI" />
</define>
"""
Add the additional definition
"""
<define name="anyIRI">
<data type="anyURI" />
<dc:description>
The lexical space of anyIRI is finite-length character sequences which
satisfy the syntax for [RFC3987] IRI-reference, a subset of the lexical
space of anyURI. However, no validation is required beyond that specified
for minimally-conforming processors of the [xmlschema-2] anyURI datatype.
</dc:description>
</define>
1.2 replace every occurrence of '<ref name="anyURI"/>' with '<ref name="anyIRI"/>'.
1.3 replace every occurrence of 'URIorSafeCURIE' with 'IRIorSafeCURIE' (2 places) only if that is still compatible with the reference to [RDFa] in section 18.3.36.
2. TEXT CHANGES
2.1 Uses of "IRI". All of the uses of IRI in the text can remain, except as identified below.
2.2 In 18,3.36, URIorSafeCURIE
(a) Use IRI only if that is permissible under the definition in [RDFa] section 7.
(b) Optionally, change the name to IRIorSafeCURIE if that is done in the schema and it is compatible with the definition in [RDFa] section 7.
2.3 Add after 18.3.1 angle, a new entry,
"""
18.3.2 anyIRI
An IRI-reference as defined in [RFC3987].
[Note: The lexical space of IRI references is a subset of the lexical space of the [xmlschema-2] anyURI datatype. No validation is required other than that specified for minimally-conforming processors of the [xmlschema-2] anyURI datatype.]
"""
One more loosening to focus on IRIs while providing reassurance that consumers are not required to validate anything more than RNG and [xmlschema-2] require validation of the anyURI datatype for minimally-conforming use of the datatype.
> 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]