[OASIS Issue Tracker] Updated: (OFFICE-3042) Planning for futurefunctions / User-defined functions

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Michael Brauer updated OFFICE-3042:
-----------------------------------

    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.

> Planning for future functions / User-defined functions
> ------------------------------------------------------
>
>                 Key: OFFICE-3042
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3042
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: OpenFormula
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Eric Patterson
>            Assignee: Patrick Durusau
>             Fix For: ODF 1.2 CD 06
>
>
> CD05 indicates that functions that are not part of the spec should be written out using a prefix (com.microsoft...).  This causes problems with user-defined functions as well as future functions to be defined later.  There has been discussion about adding the "User." prefix to user-defined functions, but how do future functions fit in?
> Assuming that a new function is added in ODF-Next, implementers of ODF 1.2 may read a future file and encounter one of these future functions.  It will be unclear how to treat the future function without some designation.  We want to avoid future functions being tagged with "User."

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