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] Updated: (OFFICE-3432) ODF 1.2 Part 2 MustUse "IRI" and "IRI-Reference" Consistently



     [ http://tools.oasis-open.org/issues/browse/OFFICE-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Hamilton updated OFFICE-3432:
------------------------------------

       Proposal: 
Handle (2-3) with separate JIRA issues.

For (1), make the following adjustments:

In section 1.4:Normative References, remove the [RFC3986] entry.

Remove the last two paragraphs of section 5.8:References

Add the following text at the end of section 5.8:References

"""
The optional Source specifies that the reference is to sheets and/or cells in a different location (possibly in a same-document fragment) than that for the formula in which the reference occurs.  The Source IRI shall be an IRI reference [RFC3987] conforming to the general syntax IRI-reference rule (section 2.2 of [RFC3987]) after each occurrence of paired single-quote characters (APOSTROPHE, U+0027) in the Source is unescaped to a single unescaped (not %-encoded) single-quote character in the IRI reference.  [Note: The escaping of single-quotes as paired single-quotes in the Source is because the Source is delimited by solitary single-quote characters in the Reference.]

Resolution of the IRIs of Sources to absolute IRIs, acceptable IRI schemes, and additional scheme- and application-specific constraints are host-defined behaviors (see section 3.4 HOST-RESOLVER).

[NOTE: Except where the Reference is expressed in a CDATA section, any direct occurrence of "&" (AMPERSAND, U+0026) in the IRI reference can be introduced by use of a character entity or the pre-defined general entity "&" [XML1.0].  When the full Reference is expressed in an XML attribute where the AttValue form has surrounding single-quote characters, all occurrences of the single-quote "'" (APOSTROPHE, U+0027) in the Reference, including the doubled occurrences, can be introduced by character entity or the pre-defined general entity "'" [XML1.0].]

[BEGIN NOTE: 

IRI references allow use of specific ranges of Unicode code points beyond  U+007F (see the uschar and iprivate syntax rules in section 2.2 of [RFC3987]).  The IRI syntax allows only a subset of code points corresponding to ASCII characters in the range U+0000 through U+007F.  The excluded ASCII characters can only occur in IRI References via escaping in positions where IRI syntax rule pct-encoded applies.  The excluded characters include the controls, U+0000 through U+001F and U+007F.  The remaining excluded characters are
   SP SPACE, U+0020
      "  QUOTATION, U+0022
     <  LESS-THAN-MARK, U+003C
     >  GREATER-THAN-MARK, U+003E
      \  REVERSE SOLIDUS, U+005C
      ^  CIRCUMFLEX ACCENT, U+005E
      `  GRAVE ACCENT, U+0060
      {  LEFT CURLY BRACKET, U+007B
       |  VERTICAL LINE, U+007C
       }  RIGHT CURLY BRACKET, U+007D

The character "%" (PERCENT SIGN, U+0025) can only be introduced as other than the first character from the pct-encoded rule by escaping as "%25" where the rule pct-encoded applies.  Those non-excluded ASCII characters that have no reserved purpose in [RFC3987] do not benefit from escaping.  See [RFC3987] for the conditions where escaping of the individual reserved ASCII characters is important.

END NOTE]
""" 

  was:
Handle (2-3) with separate JIRA issues.

For (1), make the following adjustments:

In section 1.4:Normative References, remove the [RFC3986] entry.

Remove the last two paragraphs of section 5.8:References

Add the following text at the end of section 5.8:References

"""
The optional Source specifies that the reference is to sheets and/or cells in a different location (possibly in a same-document fragment) than that for the formula in which the reference occurs.  The Source IRI shall be an IRI reference [RFC3987] conforming to the general syntax IRI-reference rule (section 2.2 of [RFC3987]) after each occurrence of paired single-quote characters (APOSTROPHE, U+0027) in the Source is unescaped to a single unescaped single-quote character in the IRI reference.  [Note: The escaping of single-quotes as paired single-quotes in the Source is because the Source is delimited by solitary single-quote characters in the Reference.]

Resolution of the IRIs of Sources to absolute IRIs, acceptable IRI schemes, and additional scheme- and application-specific constraints are host-defined behaviors (see section 3.4 HOST-RESOLVER).

[NOTE: Except where the Reference is expressed in a CDATA section, any direct occurrence of "&" (AMPERSAND, U+0026) in the IRI reference can be introduced by use of a character entity or the pre-defined general entity "&amp;" [XML1.0].  When the full Reference is expressed in an XML attribute where the AttValue form has surrounding single-quote characters, all occurrences of the single-quote "'" (APOSTROPHE, U+0027) in the Reference, including the doubled occurrences, can be introduced by character entity or the pre-defined general entity "&apos;" [XML1.0].]

[BEGIN NOTE: 

IRI references allow use of specific ranges of Unicode code points beyond  U+007F (see the uschar and iprivate syntax rules in section 2.2 of [RFC3987]).  The IRI syntax allows only a subset of code points corresponding to ASCII characters in the range U+0000 through U+007F.  The excluded ASCII characters can only occur in IRI References via escaping in positions where IRI syntax rule pct-encoded applies.  The excluded characters include the controls, U+0000 through U+001F and U+007F.  The remaining excluded characters are
   SP SPACE, U+0020
      "  QUOTATION, U+0022
     <  LESS-THAN-MARK, U+003C
     >  GREATER-THAN-MARK, U+003E
      \  REVERSE SOLIDUS, U+005C
      ^  CIRCUMFLEX ACCENT, U+005E
      `  GRAVE ACCENT, U+0060
      {  LEFT CURLY BRACKET, U+007B
       |  VERTICAL LINE, U+007C
       }  RIGHT CURLY BRACKET, U+007D

The character "%" (PERCENT SIGN, U+0025) can only be introduced as other than the first character from the pct-encoded rule by escaping as "%25" where the rule pct-encoded applies.  Those non-excluded ASCII characters that have no reserved purpose in [RFC3987] do not benefit from escaping.  See [RFC3987] for the conditions where escaping of the individual reserved ASCII characters is important.

END NOTE]
""" 

    Component/s:     (was: Needs Discussion)

The double use of unescaped in the sentence of the first text paragraph is clarified that one escaping is a paired APOSTROPHE into a single unescaped (in the IRI sense) APOSTROPHE in the IRI.

> ODF 1.2 Part 2 Must Use "IRI" and "IRI-Reference" Consistently
> --------------------------------------------------------------
>
>                 Key: OFFICE-3432
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3432
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Sub-task
>          Components: OpenFormula, Part 2 (Formulas)
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
>
>
>  1. In ODF 1.2 CD05 Part 2, 5.8 References, there is mention of IRI, along with some recommendations that are imprecisely stated concerning absolute IRIs, relative IRIs, the use of "./", and other matters that are imprecise.  The rules for IRI references in [RFC3987] are sufficient.  Notes might be useful in pointing to limitations that apply to IRIs in terms of excluded characters and in dealing with single-quote and "&" occurrences that may be part of the IRI itself.
>  2. In ODF 1.2 CD05 Part 2 there is also mention of IRI as a text operand to the HYPERLINK function (sectin 6.11.3).  The relationship of that use of IRI needs to be clarified.
>  3. There may be similar clarification required in treatment of IRI in the context of the FILENAME Info_Type in the CELL function (section 6.13.3).

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