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] 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=22310#action_22310 ] 

Dennis Hamilton edited comment on OFFICE-3440 at 10/18/10 11:44 AM:
--------------------------------------------------------------------

My own vote:

1. -1
2. +1
3. -1

[comment edited slightly:]

I was asked why all the notes, and could we just simply say we are using anyURI restricted to [RFC3987].  I didn't want to contradict the provisions of [xmlschema-2] in any way.  However, deriving a restrained type to the subset of anyURI that [RFC3987] is all that the introduction of anyIRI needs to say.  There doesn't even need to be different schema, although it is possible to add a pattern that excludes the [RFC3987]-excluded Unicode code points that anyURI does not exclude.  This would not make schema checking any different than already required by anyURI use, other than the elimination of some Unicode code points.  

The notes are to encourage people to actually take note of the specifications and not assume that it is known what the difference is or assuming there is no difference.  They are just notes.  They are probably more important in Part 2 where we don't have even anyURI to rely on.

Note that an anyIRI would fit exactly with the definition in Part 3 for resolution of IRI References in Packages.  There it proposed that we be specific about [RFC3987].  See OFFICE-2685 as it plays out.

      was (Author: orcmid):
    My own vote:

1. -1
2. +1
3. -1

I was asked why all the notes, and could we just not say we are using anyURI restricted to [RFC3987].  I didn't want to contradict the provisions of [xmlschema-2] in any way.  However, deriving a restrained typ to the subset of anyURI that [RFC3987] is all that the introduction of anyIRI needs to say.  There doesn't even need to be different schema, although it is possible to add a pattern that excludes the [RFC3987]-excluded Unicode code points that anyURI does not exclude.

The notes are to encourage people to actually take note of the specifications and not assume that it is known what the difference is or assuming there is no difference.  They are just notes.  They are probably more important in Part 2 where we don't have even anyURI to rely on.

Note that an anyIRI would fit exactly with the definition in Part 3 for resolution of IRI References in Packages.  There it proposed that we be specific about [RFC3987].  See OFFICE-2685 as it plays out.
  
> 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]