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=22940#action_22940 ] 

Dennis Hamilton commented on OFFICE-3440:

PS: There is no "in principle" about <dc:description> in RNG Schema.  There are specific rules for foreign elements and where they can appear and I honored those rules.  It happened that the dc: prefix binding is already in the ODF 1.2 Schema, so that was an easy choice.

I think we have a comment in at least one other place in one of our schemas, but using <dc:description> seemed much nicer than <!-- ... -->.

However, I don't have any objection to instead referring to a prose statement in the specification.  It should be to the specific section number, of course.

I know what the definition of anyURI is in the schema, I was looking at it when I said where to put the anyIRI definition.  I would not move the definition of anyURI to the later section, because if it is in the schema at all, it is one of the ones taken directly from [xmlschema-2] and it should be with those others.

I'm tired now and I will look at this again on Thursday.

[Maybe we need to say that an anyIRI is an anyURI intended for carrying [RFC3987] IRIs.  And then say what you say for the note in your last comment.  It would at least legitimize and be consistent with our use of IRI in the normative text where we do so already.

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