[OASIS Issue Tracker] (ODATA-812) Allow omitting namespaces for unambiguous functions/actions

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

    [ https://issues.oasis-open.org/browse/ODATA-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60696#comment-60696 ] 

Evan Ireland commented on ODATA-812:
------------------------------------

Another thing to consider: we are assuming that OData 4.0 doesn't permit ambiguity already.But we have:

singleNavigation = [ "/" qualifiedEntityTypeName ] 
                  ...
                   / boundOperation

boundOperation = "/" ( boundActionCall ... )

boundActionCall  = namespace "." action

So if a qualifiedEntityTypeName matches a boundActionCall (if a bound Action in the Schema has the same name as an eityty type), then we already might have ambiguity, depending on interpretation of CSDL spec.

SCDL spec states: "The schema’s namespace is combined with the name of elements in the entity model to create unique qualified names, so identifiers that are used to name types MUST be unique within a namespace to prevent ambiguity."

Is an Action considered to be a "type"?




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