[ https://issues.oasis-open.org/browse/ODATA-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60653#comment-60653 ]
Steven Legg commented on ODATA-812:
-----------------------------------
There is still potential ambiguity if Something is a collection navigation property and a function. For example, given
GET ~/EntitySet(Key)/Something(key='foobar')
this could be calling the Something function or applying a key predicate to the Something collection.
> 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)
