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] Commented: (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:comment-tabpanel&focusedCommentId=22960#action_22960 ] 

Michael Brauer commented on OFFICE-3440:

Dennis: I had another look into RFC3987. It states in section 3.1: Every URI is by definition an IRI.

I withdraw my last comment. There are no URIs that are not valid IRIs. 

But I have to admit that I neither do understand your last comment, nor what issue we are trying to solve here.

I have no objections if we describe the anyURI datatype as:

An IRI-reference as defined in [RFC3987].

Note: The lexical space of the [xmlschema-2] anyURI datatype permits literals that are not valid IRIs. No validation is required for OpenDocuments URI other than that specified for minimally-conforming processors of the [xmlschema-2] anyURI datatype

But I don't see a value in all the other changes that are proposed. Sure we talk about IRIs and call the datatype anyURI. But that is exactly that XSD 1.1 does, so why should we confuse our readers with a different name? The same for "URIorSafeCURIE ". We have taken that name from the RDFa specification, and that explicitly says that this datatype accepts IRIs. Why should we confuse readers with calling that datatype "IRIorSafeCURIE"?

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