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=22523#action_22523 ] 

Dennis Hamilton commented on OFFICE-3440:

Michael, it seems to me that the OpenDocument format is an application of [xmlschema-2] datatypes.  We make normative use of it in our specification and in our RNG schema.  Likewise, the OpenDocument Format Specification provides an application of [RNG], [xml-id], [XML1.0], etc.  We are the ones who derive additional types and constrain them in our OpenDocument-specific schemas and explicit provisions in the OpenDocument specification text.  The OpenDocument specification establishes an application-specific set of schemas and additional syntactical and semantic interpretations for instances under those schemas and we rely on (apply) other specifications in so doing.

It may well be that some of the provisions of OpenDocument specification are implementation-dependent/-defined, but even we get to say that, as the specifiers of the OpenDocument application of XML.

Of course, the OpenDocument specification also has applications, either by being referenced in other specifications or the definitions (private or -defined) of software implementations for consumers and producers.  It is the OpenDocument application of these other specifications that creates the combination of provisions that are then available for appllication by implementations of OpenDocument.  But we say how much the specifications that we apply are manifest in provisions of OpenDocument that others then make further application that is consistent with what OpenDocument specifies on the subject.

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