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) Needs-Discussion:Planning for future functions / User-defined functions

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

Robert Weir  commented on OFFICE-3042:

I was assuming that future OpenFormula-defined functions would be neither com.microsoft nor User.  I think we want to reserve essentially the entire "default" namespace for future OpenFormula functions.

The distinction between user extensions and vendor extensions is a bit nebulous.  

In terms of processing unknown functions, I think we have the following:

1) Functions in default namespace not recognized by application.  These could be future functions or just 1.2 functions that are not implemented

2) Extensions functions whether by vendor or user

3) Known functions that have additional arguments or expanded range of arguments compared to ODF 1.2.  This gets messy and is best avoided, I think.  We could agree that in the future changes to semantics of built-in functions are dealt with by creating a new function name.

> 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
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Eric Patterson
> 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]