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=22364#action_22364 ] 

Dennis Hamilton edited comment on OFFICE-3440 at 10/20/10 2:34 PM:
-------------------------------------------------------------------

We seem to keep talking past each other.  It is TRUE that you can put an [RFC3987] into an anyURI with no problem.  The problem is that anyURI is NOT RESTRICTED TO [RFC3987] IRIs, and if wat to stick to IRIs, we have to say so.

That's, I think, where you and I disagree.  Also, In Part 3, section 3.7, we only deal with IRIs (off-hand) and URI's specifically, so why not with regard to how anyURI is applied in ODF?  Defining anyIRI to be an anyURI that *only* holds an IRI Reference would do that.

1. Do you see the difference?
2. (I understand you to say the difference is unimportant, but do you see the difference?).

      was (Author: orcmid):
    We seem to keep talking past each other.  It is TRUE that you can put an [RFC3987] into an anyURI with no problem.  The problem is that anyURI is NOT RESTRICTED TO [RFC3987] IRIs, and if wat to stick to IRIs, we have to say so.

That's, I think, where you and I disagree.  Also, In Part 3, section 3.7, we only deal with IRIs (off-hand) and URI's specifically, so why not with regard to how anyURI is applied in ODF?  Defining anyIRI to be an anyURI that holds an IRI would do that.

1. Do you see the difference?
2. (I understand you to say the difference is unimportant, but do you see the difference?).
  
> 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]