[OASIS Issue Tracker] Updated: (ODATA-269) Separate Functions and Actions

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

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

Ralf Handl updated ODATA-269:
-----------------------------

    Component/s: OData URL Conventions 
     Resolution: 
https://www.oasis-open.org/committees/download.php/48378/odata-core-v4.0-wd01-part3-csdl-2013-02-26-RH.doc
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/edmx.xsd?rev=201
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/edm.xsd?rev=201

> Separate Functions and Actions
> ------------------------------
>
>                 Key: ODATA-269
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-269
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL, OData Protocol , OData URL Conventions 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Assignee: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> In ODATA-225 we moved function definition out of the EntityContainer by introducing a new Function element. We should take this opportunity to clean up the confusion between actions (which may be side-effecting and are not composable) from functions (which must not be side-effecting and may be composable). Previously these were differentiated by an isSideEffecting attribute on the FunctionImport, and depending on whether this was set other attributes (like isComposable) were or were not valid.

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