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

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

If we did the above suggestion, we could require that an inheritance hierarchy would be prohibited from defining properties and nested actions/functions with clashing names (and disalllow dynamic properties which would clash).

The use of nested actions/functions would remove the difficulties associated with referencing other schemas/vocabularies.


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