[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-279) Define URL conventions for addressing functions and function imports
[ http://tools.oasis-open.org/issues/browse/ODATA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-279:
-----------------------------
Proposal:
Functions MUST NOT be used at the service root.
Function imports MUST NOT be used anywhere except at the service root, especially not in query options or path expressions.
Children of the default entity container MAY be used without qualifiers in URLs.
Children of any schema in the metadata document MAY be qualified with the alias defined by the Schema element that defines them.
All Schema elements within a CSDL document MUST have different values for the Alias attribute.
Aliases introduced via the Alias attribute of Schema elements are now document-global and can be used in other schemas of the same document without needing a Using element.
Using elements MUST NOT introduce clashes with aliases defined by other Using elements of the same schema (we forgot to specify this) or with aliases defined by other Schema elements of the same document.
See https://www.oasis-open.org/committees/document.php?document_id=48353&wg_abbrev=odata for details.
Accepted: https://www.oasis-open.org/committees/download.php/48481/odata-meeting-28_on-20130307-minutes.html#odata-279
was:
Functions MUST NOT be used at the service root.
Function imports MUST NOT be used anywhere except at the service root, especially not in query options or path expressions.
Children of the default entity container MAY be used without qualifiers in URLs.
Children of any schema in the metadata document MAY be qualified with the alias defined by the Schema element that defines them.
All Schema elements within a CSDL document MUST have different values for the Alias attribute.
Aliases introduced via the Alias attribute of Schema elements are now document-global and can be used in other schemas of the same document without needing a Using element.
Using elements MUST NOT introduce clashes with aliases defined by other Using elements of the same schema (we forgot to specify this) or with aliases defined by other Schema elements of the same document.
Children of any schema in scope MAY be qualified with the alias defined by the schema that defines the top level resource (directly following the service root) of the request.
See https://www.oasis-open.org/committees/document.php?document_id=48353&wg_abbrev=odata for details.
Accepted: https://www.oasis-open.org/committees/download.php/48481/odata-meeting-28_on-20130307-minutes.html#odata-279
Removed sentence "Children of any schema in scope MAY be qualified with the alias defined by the schema that defines the top level resource (directly following the service root) of the request." from proposal; aliases are document-global and this sentence was a left-over.
> Define URL conventions for addressing functions and function imports
> --------------------------------------------------------------------
>
> Key: ODATA-279
> URL: http://tools.oasis-open.org/issues/browse/ODATA-279
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: OData ABNF Construction Rules, OData CSDL, OData URL Conventions
> Affects Versions: V4.0_WD01
> Environment: [Proposed]
> Reporter: Ralf Handl
> Fix For: V4.0_WD01
>
>
> Separating Function from FunctionImport with ODATA-225 was a good idea, now we need to define how these two beasts can be addressed in URLs.
--
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]