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=21428#action_21428 ] 

Dennis Hamilton commented on OFFICE-3440:

The OpenFormula SC review of the IRI provision in references will lead to a clean-up at the beginning that will also be useful to make here.

Meanwhile, the final note has problems that I didn't notice right away.  It may be inappropriate to describe such a specific remedy because of that.  I will deal with that considering an update.  Perhaps something between what's there now and this:

[NOTE: The form of fragment identifiers provided for in the General IRI syntax of [RFC3987] is more restricted than allowed for in Section 5.4 of [XLink] such that the currently-effective SchemeBased syntax of the XPointer Framework [XPointer] cannot be employed directly. Successful communication of SchemeBased [XPointer} forms in IRI Reference ifragments depends on resolver conventions for recognizing an escaping of excluded ASCII characters and "%" that can be restored into a SchemeBased syntax that conveys the "^"-bracketing and -escaping conventions of [XPointer].  See Part 3 "IRI Usage in Packages" for consideration applicable to resolution of relative references to XML-based package files that include fragment identifiers.]

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