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

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

Since any such change would require some new CSDL syntax...

What about, for bound actions/functions in complex/entity types, allow the Action/Function definition to appear nested inside the ComplexType/EntityType (in which case IsBound would be implied by the nesting).

Rather than this:

<edmx:Edmx xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx"; Version="4.0">
  <edmx:DataServices>
    <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm"; Namespace="calc" Alias="Self">
      <EntityType Name="Calc">
        <Key>
          <PropertyRef Name="id"/>
        </Key>
        <Property Name="id" Type="Edm.String"/>
      </EntityType>
      <Action Name="add" IsBound="true" ReturnType="Edm.Double">
        <Parameter Name="this" Type="Self.Calc"/>
        <Parameter Name="x" Type="Edm.Double"/>
        <Parameter Name="y" Type="Edm.Double"/>
      </Action>
      <EntityContainer Name="Components">
        <EntitySet Name="Calc" EntityType="Self.Calc"/>
      </EntityContainer>
    </Schema>
  </edmx:DataServices>
</edmx:Edmx>

we could have this:

<edmx:Edmx xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx"; Version="4.0">
  <edmx:DataServices>
    <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm"; Namespace="calc" Alias="Self">
      <EntityType Name="Calc">
        <Key>
          <PropertyRef Name="id"/>
        </Key>
        <Property Name="id" Type="Edm.String"/>
        <Action Name="add" ReturnType="Edm.Double">
          <Parameter Name="x" Type="Edm.Double"/>
          <Parameter Name="y" Type="Edm.Double"/>
        </Action>
      </EntityType>
      <EntityContainer Name="Components">
        <EntitySet Name="Calc" EntityType="Self.Calc"/>
      </EntityContainer>
    </Schema>
  </edmx:DataServices>
</edmx:Edmx>


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