[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=60702#comment-60702 ] 

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

Thanks Ralf for highlighting that wording.

Now back to your earlier comments:

" -either don't reference external documents that may define actions/functions, or only reference such documents that are under full control of the service owner 

 The latter rule will essentially prevent services from referenceing shared vocabularies because these are allowed to add actions/functions."

If we consider allowing unqualified naming of calls only for *bound* actions/functions, then how likely is it that a shared vocabulary (in a referenced document) will define a *bound* action/function where the binding parameter type (in a referencing document) defines a property with the same name?

Isn't it most likely that *bound* actions/functions will be defined in the same document as the binding parameter 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)