[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-225) Define Functions in Schema; reference in Container using FunctionImport.
[ http://tools.oasis-open.org/issues/browse/ODATA-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-225:
-----------------------------
Proposal:
-Define a <Function> element used to define the shape of a function in the schema. The function definition defines parameters, return values, and may specify an entitysetpath.
-Functions defined in the model are available for use by referencing the model. You do not need to "import them" into your container
-The only time you use a functionimport is if you want to expose a function as a top-level function in your entitycontainer, or bind a function to a specific entityset in your entitycontainer. Note that, if the return set is relative to the input set you can define this in the entitysetpath in the <Function> definition of the model, then you don't need to import it unless you want to expose it as a top-level function.
-The FunctionImport always references a <Function> defined in the schema (similar to how an EntitySet always references an EntityType defined in the schema)
-Functions should be bindable to primitive or complex types (or sets of primitive or complex types) in addition to entities/sets of entities.
Accepted: https://www.oasis-open.org/committees/download.php/48097/odata-meeting-23_on-20130130_31-F2F-minutes.html#odata-225
was:
-Define a <Function> element used to define the shape of a function in the schema. The function definition defines parameters, return values, and may specify an entitysetpath.
-Functions defined in the model are available for use by referencing the model. You do not need to "import them" into your container
-The only time you use a functionimport is if you want to expose a function as a top-level function in your entitycontainer, or find a function to a specific entityset in your entitycontainer. Note that, if the return set is relative to the input set you can define this in the entitysetpath in the <Function> definition of the model, then you don't need to import it unless you want to expose it as a top-level function.
-The FunctionImport always references a <Function> defined in the schema (similar to how an EntitySet always references an EntityType defined in the schema)
-Functions should be bindable to primitive or complex types (or sets of primitive or complex types) in addition to entities/sets of entities.
Accepted: https://www.oasis-open.org/committees/download.php/48097/odata-meeting-23_on-20130130_31-F2F-minutes.html#odata-225
Component/s: OData ABNF Construction Rules v1.0
As functions and actions are now schema children and function imports are only required for top-level functions we need to change the qualification rules for function and action names: they are now namespace- or alias-qualifed instead of container-qualified.
> Define Functions in Schema; reference in Container using FunctionImport.
> ------------------------------------------------------------------------
>
> Key: ODATA-225
> URL: http://tools.oasis-open.org/issues/browse/ODATA-225
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData ABNF Construction Rules v1.0, OData CSDL v1.0
> Affects Versions: WD01
> Environment: [Proposed]
> Reporter: Michael Pizzo
> Assignee: Ralf Handl
> Fix For: WD01
>
>
> It is difficult to share functions because they are defined in an entitycontainer.
> Functions should follow a similar model to Entities; the types should be defined in schema and we should use the entitycontainer to expose them at the container level, or to bind to particular sets within the container.
--
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]