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-3042) Planning for futurefunctions / User-defined functions



    [ http://tools.oasis-open.org/issues/browse/OFFICE-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21893#action_21893 ] 

Andreas Guelzow  commented on OFFICE-3042:
------------------------------------------

Instead of "When the origin of a function cannot be determined, evaluators may omit a prefix. Evaluators may use the prefix to differentiate between different definition types." we may need to write "When the origin of a function cannot be determined, producers may omit a prefix. Producerss may use the prefix to differentiate between different definition types." This is not really an issue for evaluators.

> 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: Needs Discussion, OpenFormula, OpenFormula Test Cases, Overview Document, Packaging, Paragraph, Part 1 (Schema), Part 2 (Formulas), Part 3 (Packages), Presentation, Public Review
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Eric Patterson
>            Assignee: Eric Patterson
>             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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]