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:


1.1 After the definition
<define name="anyURI">
   <data type="anyURI" />

Add the additional definition

<define name="anyIRI">
    <data type="anyURI"  />
            anyIRI values are lexically strings satisfying the [RFC3987] 
            IRI-reference format, a subset of the W3C Schema anyURI
            lexical form.  anyIRI is subject to the same schema conditions
            as the is the anyURI datatype.

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.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].  Well-formed IRI references are a subset of the lexical forms defined for anyURI in [xmlschema-2].

To demonstrate all that is involved to make an anyIRI that is consistent with the use of IRI everywhere in the text, I have proposed a resolution that covers all that needs to be covered to make that explicit.

I am leaving the needs-discussion, of course, because there is at least one negative vote.

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