[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:all-tabpanel ]

Michael Pizzo updated ODATA-812:
--------------------------------

    Proposal: 
-4.01 services need to support invoking unqualified actions/functions 
-State that bound actions/functions SHOULD NOT conflict with any properties on the type they are bound to
-Define a precedence for resolving possible conflicts:
   -declared property=>function/action=>open property 
-Services must also allow qualified invocation

  was:
- Define term for services to announce whether they support invoking functions/actions without namespace qualification
- Require that bound actions/functions don't conflict with any properties if service announces support for shortcut syntax
- Make clear that services can support this in addition to qualified invocation, and must also allow qualified invocation


> 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: Simplified Syntax
>            Reporter: Michael Pizzo
>            Assignee: 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)