[OASIS Issue Tracker] Updated: (ODATA-542) Clarify that $selected Actions/Functions are included in [project-list] within a ContextUrl

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

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

Ralf Handl updated ODATA-542:
-----------------------------

    Environment: [Proposed][Applied for Review]  (was: [Proposed][Applied to CSDL; need to update ABNF])
     Resolution: 
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-construction-rules.txt?rev=489
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-testcases.xml?rev=489


> Clarify that $selected Actions/Functions are included in [project-list] within a ContextUrl
> -------------------------------------------------------------------------------------------
>
>                 Key: ODATA-542
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-542
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ABNF Construction Rules, OData Protocol 
>    Affects Versions: V4.0_CS01
>         Environment: [Proposed][Applied for Review]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CSD03
>
>
> The purpose of putting the project list in the context url is so that the client (i.e., a JSON parser) can differentiate between content that was omitted from a response because they weren't selected versus omitted because they weren't applicable (i.e., dynamic properties, functions and actions)
> We support the project-list for properties but we don't specify whether or not it includes actions/functions that are explicitly requested by the client.
> In general, the client knows that it can always try to invoke a bound action/function to an entity of the correct type, so it doesn't need to be advertised in the payload, but if a client explicitly selects a function/action then it must be included, if applicable, and the client knows that it's absence means that it is not applicable (can't be called) on the current entity.
> This all works fine; we just failed to mention in [Protocol] and [ABNF] that functions/actions from the $select also appear in the project-list

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