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-3342) NEEDS-DISCUSSION:ODF 1.2 Part 1 "IRI" abuse

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

Dennis Hamilton commented on OFFICE-3342:

It is true that the URI specification allows IRIs and anything that allows URIs allows IRIs.  But that is like saying SMTP plaintext messages allow HTML messages or even XML.  It is true, but it is true by a convention that is not part of URI (or SMTP plaintext) itself.  (Using MIME enclosures solves this problem in a particular way, so that using plaintext as a carrier of a special markup is less common, but not prevented, as far as I know.)

It is an out-of-band agreement that the encoding convention in URI be used and understood in a particular way that allows Unicode characters not permitted directly in a URI to be carried by following a specific convention on the use of encoding.  (URI encoding is a single-byte encoding scheme.  It encodes a single byte.  To treat sequences of them as encodings of UTF-8 encodings of single Unicode code points is *not* part of the URI specification.

If *we* intend that convention, we need to be very specific where it applies and where we use the term IRI.  We should probably adopt IRI in all of those places and not use URI in the same breath.  At the same time, we need to make sure that where we assert use of the IRI convention, we are dealing with data types or namespace provisions that accomodate that.

I gather that we want to permit IRIs to be used to reference files within the same package (using relative URI references as the carrier).  That means we also need to specifiy what that means in terms of how the name of the package file is is related to the various relative IRI-carrying URIs by which it can be referenced.  (This is the job that needs to be dealt with in Part 3.  The job in Part 1 has to do with making sure that all of the places where anyURI, xhtml:href, and xlink:href and other reference structures are used, including same-page references via URI fragment forms, how their relative URI references are IRI encodings.  We need to determine whether we are we seeing exceptions related to the determination of a base tolerated in Part 3 and are there any other exceptions.  In particular, is our use a deviation from what the specifications for those references under the namespace of other folks require (e.g., for RDF and for XML DSig), and have we made that deviation explicit and unambigous in the ODF specification?

> NEEDS-DISCUSSION: ODF 1.2 Part 1 "IRI" abuse
> --------------------------------------------
>                 Key: OFFICE-3342
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3342
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: General, OpenFormula, Part 1 (Schema), Part 2 (Formulas), Schema and Datatypes
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
> There are over 20 places in ODF 1.2 CD05 Part 1 where the term "IRI" is used without reference or explanation.  These are often in the same statement where URI/URL are used and it is not clear whether these are being assumed to be interchangeable or different.  
> These mentions of IRI are too casual.  We should perhaps establish that we assume all provisions for URI references in Part 1 are subject to IRI encoding and choose to use IRI consistently.  We might need to be careful that we don't overstep existing provision on URIs used as part of attributes defined by other specifications, such as xhtml:href and xlink:href, however.  We may also need to say more about  URI references when they use XML Schema Datatype anyURI.
> Whatever we do, it is a defect to continue to use IRI casually and with neither definition nor reference to an authoritative source.
> This is related to the similar situation in ODF 1.2 CD05 Part 3, addressed by issue OFFICE-2685 and any resolution in part 1 should be consistent.
> There may also be need for IRI clarification, and clarification around the permissable use of relative URIs in OpenFormula when an OpenFormula expression employs a URI in one of its forms for a reference.

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]