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-3496) OpenFormulaConformance Clause 2.2.2(I) Seems Misplaced

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

Michael Brauer updated OFFICE-3496:

    Component/s:     (was: Needs Discussion)

This issue has been set to resolved after the needs discussion flag has been set. I strongly assume the resolution reflects the result of the discussion, and therefore will remove the needs discussion.

> OpenFormula Conformance Clause 2.2.2(I) Seems Misplaced
> -------------------------------------------------------
>                 Key: OFFICE-3496
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3496
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Conformance, OpenFormula
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
> In the Conformance Clause for Small Group Evaluators, there is this particular clause 2.2.2(I):
> """
> I)It shall support international characters for named expression identifiers.
> Note: This specification does not mandate a user interface for international characters, so a resource-constrained application may choose to not show the traditional glyph (e.g., it may show the [UNICODE] numeric code instead).
> """
> Problem #1: The Note is not about OpenFormula evaluators but what a hosting-specification and its implementations might provide for.  The note should be removed, especially since it includes normative-provision language ("may").
> Problem #2: "international characters" is not a defined concept.  The syntax for named expression identifiers seems to be quite explicit.  Although there are many notes in section 5.11, there is a potential conflict with the rules for case-sensitive names that must not be case-insensitive confused and some other non-note provisions.
> Problem #3: The resolution of named expressions is clearly a host-dependent behavior (and the host-dependent behaviors that are tacit in section 5.11 need to be made explicitly host-dependent and simplified), so which uses of Unicode characters match with host-provided named expressions need not be resolved here.

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]