[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-196) Remove sections 15.2.6 FunctionReference and 15.2.12 ParameterReference
[ http://tools.oasis-open.org/issues/browse/ODATA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-196: ----------------------------- Summary: Remove sections 15.2.6 FunctionReference and 15.2.12 ParameterReference (was: Remove section 15.2.6 FunctionReference) Description: Section 15.2.6 The edm:FunctionReference Expression states that its value is a reference to the return type of a function. This seems to be a leftover from removing model functions. The example uses Function="org.example.person.GetAge", which indicates that it points to a model function as it uses the same prefix as the org.example.person.Age value term, which implies that GetAge is defined in a schema (as a model function would have been) and not in an entity container (as a function import must be). Also the introduction of Type Definitions now allows giving a name to primitive types with facets, so even primitive return types with facets can now be given a name, reducing the need for referring to implicitly defined types. The meaning of a ParameterReference as defined in section 15.2.12 is unclear, and the example gives no hints on how to interpret it, was: Section 15.2.6 The edm:FunctionReference Expression states that its value is a reference to the return type of a function. This seems to be a leftover from removing model functions. The example uses Function="org.example.person.GetAge", which indicates that it points to a model function as it uses the same prefix as the org.example.person.Age value term, which implies that GetAge is defined in a schema (as a model function would have been) and not in an entity container (as a function import must be). Also the introduction of Type Definitions now allows giving a name to primitive types with facets, so even primitive return types with facets can now be given a name, reducing the need for referring to implicitly defined types. > Remove sections 15.2.6 FunctionReference and 15.2.12 ParameterReference > ----------------------------------------------------------------------- > > Key: ODATA-196 > URL: http://tools.oasis-open.org/issues/browse/ODATA-196 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: OData CSDL v1.0 > Affects Versions: WD01 > Environment: [Proposed] > Reporter: Ralf Handl > Fix For: WD01 > > > Section 15.2.6 The edm:FunctionReference Expression states that its value is a reference to the return type of a function. This seems to be a leftover from removing model functions. > The example uses Function="org.example.person.GetAge", which indicates that it points to a model function as it uses the same prefix as the org.example.person.Age value term, which implies that GetAge is defined in a schema (as a model function would have been) and not in an entity container (as a function import must be). > Also the introduction of Type Definitions now allows giving a name to primitive types with facets, so even primitive return types with facets can now be given a name, reducing the need for referring to implicitly defined types. > The meaning of a ParameterReference as defined in section 15.2.12 is unclear, and the example gives no hints on how to interpret it, -- 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]