[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: 
-introduce a vocabulary element for services to declare one or more default namespaces, as per simplified url proposal (https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201511/msg00007.html)

-4.01 services need to support invoking unqualified actions/functions defined within a default namespace
-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 as per simplified url proposal:
   -declared property=>function/action=>open property 
-Services must also allow qualified invocation

-make sure that docs are clear that services must not require clients to understand custom annotations, but OData annotations may imply semantics that a client reporting support for that version of the specification would need to understand in order to work correctly with the service. 

  was:
-introduce a vocabulary element for services to declare one or more default namespaces, as per simplified url proposal (https://www.oasis-open.org/apps/org/workgroup/odata/email/archives/201511/msg00007.html)

-4.01 services need to support invoking unqualified actions/functions defined within a default namespace
-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 as per simplified url proposal:
   -declared property=>function/action=>open property 
-Services 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;[Proposed]
>            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)