[ https://issues.oasis-open.org/browse/ODATA-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60675#comment-60675 ]
Steven Legg edited comment on ODATA-812 at 9/11/15 12:01 AM:
-------------------------------------------------------------
Ralf, UnqualifiedCalls or UnqualifiedBoundCalls as suggestions for the term name. Or if we don't mind having two terms, UnqualifiedFunctionCalls & UnqualifiedActionCalls or UnqualifiedBoundFunctionCalls & UnqualifiedBoundActionCalls.
Evan, the advantage of a term is that it can be defined in an extension vocabulary without changing the CSDL syntax. Nested actions/functions can be considered whenever the CSDL syntax is next revised.
was (Author: steven.legg):
[~handl], UnqualifiedCalls or UnqualifiedBoundCalls as suggestions for the term name. Or if we don't mind having two terms, UnqualifiedFunctionCalls & UnqualifiedActionCalls or UnqualifiedBoundFunctionCalls & UnqualifiedBoundActionCalls.
[~evan.ireland.2], the advantage of a term is that it can be defined in an extension vocabulary without changing the CSDL syntax. Nested actions/functions can be considered whenever the CSDL syntax is next revised.
> Allow omitting namespaces for unambiguous functions/actions
> -----------------------------------------------------------
>
> Key: ODATA-812
> URL: https://issues.oasis-open.org/browse/ODATA-812
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: OData Protocol
> Affects Versions: V4.0_ERRATA02
> Environment: [Proposed]
> Reporter: Michael Pizzo
> Labels: AdoptionBlocker
> Fix For: V4.01_WD01
>
>
> I hear a lot of pushback on having to qualify functions/actions when invoking.
> We can support unqualified function/actions as long as they don't conflict with any properties.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
