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=20624#action_20624 ] 

Patrick Durusau commented on OFFICE-3342:
-----------------------------------------

Dennis,

OK, agree we need to put in a reference for IRI and include that where it is cited. 

When you say:

****
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.
****

Isn't it sufficient to compare anyURI, xhtml:href and xlink:href and any other IRI reference structures, now conveniently isolated in separate sections since if they are valid in one they are valid in all? 

Do you have an example of where "...their relative URI references are not IRI encodings?"

Seems like that would be a better way to raise the issue. As well as focus any effort to answer it. BTW, the xlink:href attribute has all the elements that invoke it gathered together so it should not be difficult to see if we call out a reference that doesn't work under an IRI.

Just a historical note: IRIs were added at the request of the CJK community.

PS: If there are any modifications to the invocation of xlink:href, for example, that is not located with the xlink:href definition, that is an editorial error that I need to correct.

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