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] 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-15T03:49Z removed the removal of anyURI from the list in the Datatypes section.
[edited 2010-11-09T04:32Z removed 2.1 indication of there being an exception and added connection to OFFICE-3342 resolution.]
[edited 2010-11-09T04:04Z simplifed to remove all validation and emphasize IRI-ness.
[edited 2010-11-05T16:58Z to remove all modification related to Curies.
[edited 2010-11-04T18:26Z to relax to only what anyURI says apart from notes]
[edited 2010-11-03T15:22Z to use "lexical space."]
[edited 2010-11-11 by Michael to reflect the actual schema changes that were applied]

1. SCHEMA UPDATE

1.1 Keep the definition for anyURI

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> 
        An IRI-reference as defined in  [RFC3987].     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"/>', except those that occurs in the definition of "URIorSafeCURIE".

1.4 replace the two XML comment in the schema with <dc:description> elements.

2. TEXT CHANGES

2.1 Uses of "IRI".  All of the uses of IRI in the text can remain.  OFFICE-3442 should be marked Resolved as fixed with a resolution that the use of IRI has been harmonized by this issue.

2.2 Add after 18.3.1 angle, a new entry,

"""
18.3.2 anyIRI

An IRI-reference as defined in [RFC3987], expressed in an [xmlenc-2] anyURI.  

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

  was:
[edited 2010-11-09T04:32Z removed 2.1 indication of there being an exception and added connection to OFFICE-3342 resolution.]
[edited 2010-11-09T04:04Z simplifed to remove all validation and emphasize IRI-ness.
[edited 2010-11-05T16:58Z to remove all modification related to Curies.
[edited 2010-11-04T18:26Z to relax to only what anyURI says apart from notes]
[edited 2010-11-03T15:22Z to use "lexical space."]
[edited 2010-11-11 by Michael to reflect the actual schema changes that were applied]

1. SCHEMA UPDATE

1.1 Keep the definition for anyURI

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> 
        An IRI-reference as defined in  [RFC3987].     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"/>', except those that occurs in the definition of "URIorSafeCURIE".

1.4 replace the two XML comment in the schema with <dc:description> elements.

2. TEXT CHANGES

2.1 Uses of "IRI".  All of the uses of IRI in the text can remain.  OFFICE-3442 should be marked Resolved as fixed with a resolution that the use of IRI has been harmonized by this issue.


2.2 In secition 18.2 W3C Schema Datatypes, delete "anyURI" from that list.

2.3 Add after 18.3.1 angle, a new entry,

"""
18.3.2 anyIRI

An IRI-reference as defined in [RFC3987], expressed in an [xmlenc-2] anyURI.  

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


> 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: Part 1 (Schema), Schema and Datatypes
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Patrick Durusau
>             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]