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) NEEDS-DISCUSSION:ODF 1.2 CD05 Part 1 Needs anyIRI datatype

    [ http://tools.oasis-open.org/issues/browse/OFFICE-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21497#action_21497 ] 

Michael Brauer commented on OFFICE-3440:

It might be worth having a look as XSD 1.1 Datatypes, which currently are a working draft:


It states

"anyURI represents an Internationalized Resource Identifier Reference (IRI).  An anyURI value can be absolute or relative, and may have an optional fragment identifier (i.e., it may be an IRI Reference).  This type should be used when the value fulfills the role of an IRI, as defined in [RFC 3987] or its successor(s) in the IETF Standards Track."

but also:

"The value space of anyURI is the set of finite-length sequences of zero or more characters (as defined in [XML]) that - match-  the Char production from [XML]."

which means that it the W3C definition does not attempt to restrict the value space of an IRI. The explanation for this can be found in the note that follows:

"For an anyURI value to be usable in practice as an IRI, the result of applying to it the algorithm defined in Section 3.1 of [RFC 3987] should be a string which is a legal URI according to [RFC 3986]. (This is true at the time this document is published; if in the future [RFC 3987] and [RFC 3986] are replaced by other specifications in the IETF Standards Track, the relevant constraints will be those imposed by those successor specifications.)
Each URI scheme imposes specialized syntax rules for URIs in that scheme, including restrictions on the syntax of allowed fragment identifiers. Because it is impractical for processors to check that a value is a context-appropriate URI reference, neither the syntactic constraints defined by the definitions of individual schemes nor the generic syntactic constraints defined by [RFC 3987] and [RFC 3986] and their successors are part of this datatype as defined here. Applications which depend on anyURI values being legal according to the rules of the relevant specifications should make arrangements to check values against the appropriate definitions of IRI, URI, and specific schemes."

Based on that, I strongly recommend to use a definition for anyIRI/anyURI that is in alignment with the upcoming W3C definition. I further strongly recommend to not add any restrictions for anyURI/anyIRI which are not in the W3C definitions. Not only because they are hard to check, but also because they will be incomplete (each URI scheme adds additional restrictions) or may become obsolete with successors of RFC3987. Further, we should keep the option to switch to XSD 1.1. which is approved which would resolve this issue. If further recommend to not rename the datatype.

I'm not really sure if there is an issue with our anyURI datatype at all. RFC3987 states in section 1.2:


"For example, XML schema [XMLSchema] has an explicit type "anyURI" that includes IRIs and IRI references. Therefore, IRIs and IRI references can be in attributes and elements of type "anyURI". The reference to |XMLSchema] is: 


That's the same XSD specification we use in ODF. 

My recommendation therefore is to keep the specification as is, simply to avoid that we add IRI related issues which will be specific to ODF, because we try to solve issue that IRIs and XSD may have in general.

However, if we want to change the definition of anyURI, we should adopt the definition of XSD 1.1.

> NEEDS-DISCUSSION: 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
>             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]