[ https://issues.oasis-open.org/browse/ODATA-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60697#comment-60697 ]
Ralf Handl commented on ODATA-812:
----------------------------------
All direct schema children share the same namespace, so an entity type must not have the same name as an action, function, or other type, see http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part3-csdl/odata-v4.0-errata02-os-part3-csdl-complete.html#_Toc406397947.
> 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
> 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)
