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

Ralf Handl commented on ODATA-812:
----------------------------------

Then we'll have to be rather restrictive:
- services must guarantee that there are no ambiguities
- do not define properties or navigation properties that can collide with actions/functions applicable to that type
- either don't use open types or reject requests to add dynamic properties htat will introduce ambiguities
- 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.


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