[OASIS Issue Tracker] (ODATA-906) Consider how to specify an included namespace as a default in JSON CSDL

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/ODATA-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-906:
--------------------------------

    Environment:     (was: Simplified Syntax;[Proposed])
    Description: 
In ODATA-812 we added the concept of a default namespace, and allowed annotations from these default namespaces to be represented without namespace qualification.  We said that the service defined certain namespaces as default in $metadata by annotating the <Include> element.

While <Include> is not currently an annotatable element, there doesn't seem to be any problem making it annotatable. However, we have to consider how we would annotate this element in JSON CSDL.

  was:
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.

       Proposal:   (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)

> Consider how to specify an included namespace as a default in JSON CSDL
> -----------------------------------------------------------------------
>
>                 Key: ODATA-906
>                 URL: https://issues.oasis-open.org/browse/ODATA-906
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>              Labels: AdoptionBlocker
>             Fix For: V4.01_WD01
>
>
> In ODATA-812 we added the concept of a default namespace, and allowed annotations from these default namespaces to be represented without namespace qualification.  We said that the service defined certain namespaces as default in $metadata by annotating the <Include> element.
> While <Include> is not currently an annotatable element, there doesn't seem to be any problem making it annotatable. However, we have to consider how we would annotate this element in JSON CSDL.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)