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-3435) ODF 1.2 CD05 Part 26.11.13 Incredible HYPERLINK Function



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

Dennis Hamilton updated OFFICE-3435:
------------------------------------

       Proposal: 
OPTION 1.   (The painless approach.)

OPTION 2. Replace the definition with one that works without assumptions about how cells support hyperlinks and that provides a rational evaluation rule.

  2.1 Eliminate the idiosyncratic behavior that is discovered about a particular implementation's behavior.  

  2.2 Provide assurance about some basic case and leave issues about occurences in non-evaluated parts of expressions, multiple uses of the function in a single expression, etc., undefined or implementation-dependent and give up.

  2.3 Eliminate any observation about implementations and how a host accepts or does not accept an IRI as a companion result to an evaluation.  Whether the IRI is ignored or not is a matter for host-dependent behavior, the only way it is known that the formula has anything to do with providing a value for a cell.

  2.4 Also, both the IRI parameter and the value text should work with arbitrary expressions that determine their result.  To use HYPERLINK cleanly, there should be no need for wacky side-effects from one occurrence of HYPERLINK to another in the same expression and everything should be well-definable.

  2.5 The occurrence of this function in the interior of a named formula and in array expressions should be particularly exciting, and extensions to lists and matrix operations should be a hoot.  There is probably something that needs to be checked-into and said about this.

  2.6 The IRI delivered by the function (from whichever parameter) should be a well-formed IRI with the proviso that resolution of relative IRIs (including determination of the base IRI), limitations to particular IRI schemes, and IRI scheme-related limitations are host-dependent behaviors.

  was:
OPTION 1. Delete the function form ODF 1.2 Part 2.  (The painless approach.)

OPTION 2. Replace the definition with one that works without assumptions about how cells support hyperlinks and that provides a rational evaluation rule.

  2.1 Eliminate the idiosyncratic behavior that is discovered about a particular implementation's behavior.  

  2.2 Provide assurance about some basic case and leave issues about occurences in non-evaluated parts of expressions, multiple uses of the function in a single expression, etc., undefined or implementation-dependent and give up.

  2.3 Eliminate any observation about implementations and how a host accepts or does not accept an IRI as a companion result to an evaluation.  Whether the IRI is ignored or not is a matter for host-dependent behavior, the only way it is known that the formula has anything to do with providing a value for a cell.

  2.4 Also, both the IRI parameter and the value text should work with arbitrary expressions that determine their result.  To use HYPERLINK cleanly, there should be no need for wacky side-effects from one occurrence of HYPERLINK to another in the same expression and everything should be well-definable.

  2.5 The occurrence of this function in the interior of a named formula and in array expressions should be particularly exciting, and extensions to lists and matrix operations should be a hoot.  There is probably something that needs to be checked-into and said about this.

  2.6 The IRI delivered by the function (from whichever parameter) should be a well-formed IRI with the proviso that resolution of relative IRIs (including determination of the base IRI), limitations to particular IRI schemes, and IRI scheme-related limitations are host-dependent behaviors.

    Component/s: Needs Discussion
     Resolution: 
Delete the HYPERLINK function from ODF 1.2 Part 2.

Remove it from any list in Section 2 that it appears in.

I am resolving this with removal of the function.  That is far easier than attempting to find a safe, neutral definition of it.

I will mark this as needing discussion as well.

An alternative is to make this a weird function that goes in the list in 2.2.4 and then come up with an explanation for which simple usages work, not ones depending on  different evaluation from normal formula evaluation.

> ODF 1.2 CD05 Part 2 6.11.13 Incredible HYPERLINK Function 
> ----------------------------------------------------------
>
>                 Key: OFFICE-3435
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3435
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Needs Discussion, OpenFormula, Part 2 (Formulas)
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
>
>
> ODF 1.2 CD05 Part 2 has an inexplicable definition for the HYPERLINK function.
> The description asserts that there is an effect on a cell.
> The description assrts that there is an effect on a cell even if the function's occurrence is not needed in the evaluation of the formula.
> The description asserts that there is a coordinated effect in how an IRI is composed (or multiples delivered) from individual occurrences of the HYPERLINK function in the same expression.
> The description asserts unjustifiable requirements on the implementation of an evaluator.
> Finally, the examples of this function are used to refine the definition.  Only the simplest examples can be inferred from the definition.
> It appears that incidental consequences of a specific implementation are being appealed to, without concern for what is essential and good enough for an OpenFormula case and no matter what odd behaviors that implementations might have for cases that defy well-definedness.

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