[OASIS Issue Tracker] (ODATA-954) Key-As-Segment for multi-part keys

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

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

Michael Pizzo updated ODATA-954:
--------------------------------

    Description: 
Generalize the rules in ODATA-799 to allow key-as-segment notation also for multi-part keys.

Example: an accounting document is identified by the company code, the year, and the (auto-incremented) document number:

      <EntityType Name="AccountingDocument">
        <Key>
          <PropertyRef Name="CompanyCode" />
          <PropertyRef Name="Year" />
          <PropertyRef Name="DocumentNumber" />
        </Key>
      </EntityType>

Taking into account the order of <PropertyRef> elements within the <Key> element a single accounting document can be identified as

    GET AccountingDocuments/SAP/2016/4329043280

Open a new issue (ODATA-976) to track behavior of partial key specification. In the meantime, specification of partial keys is undefined, and if one segment is resolved as a partial key value then the subsequent segments should be resolved as any remaining key values.


  was:
Generalize the rules in ODATA-799 to allow key-as-segment notation also for multi-part keys.

Example: an accounting document is identified by the company code, the year, and the (auto-incremented) document number:

      <EntityType Name="AccountingDocument">
        <Key>
          <PropertyRef Name="CompanyCode" />
          <PropertyRef Name="Year" />
          <PropertyRef Name="DocumentNumber" />
        </Key>
      </EntityType>

Taking into account the order of <PropertyRef> elements within the <Key> element a single accounting document can be identified as

    GET AccountingDocuments/SAP/2016/4329043280

Open a new issue (ODATA-976) to track behavior of partial key specification. In the meantime, specification of partial keys is undefined.



> Key-As-Segment for multi-part keys
> ----------------------------------
>
>                 Key: ODATA-954
>                 URL: https://issues.oasis-open.org/browse/ODATA-954
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Sub-task
>          Components: OData URL Conventions
>    Affects Versions: V4.0_ERRATA02
>         Environment: New Query Capabilities
>            Reporter: Ralf Handl
>             Fix For: V4.01_WD01
>
>
> Generalize the rules in ODATA-799 to allow key-as-segment notation also for multi-part keys.
> Example: an accounting document is identified by the company code, the year, and the (auto-incremented) document number:
>       <EntityType Name="AccountingDocument">
>         <Key>
>           <PropertyRef Name="CompanyCode" />
>           <PropertyRef Name="Year" />
>           <PropertyRef Name="DocumentNumber" />
>         </Key>
>       </EntityType>
> Taking into account the order of <PropertyRef> elements within the <Key> element a single accounting document can be identified as
>     GET AccountingDocuments/SAP/2016/4329043280
> Open a new issue (ODATA-976) to track behavior of partial key specification. In the meantime, specification of partial keys is undefined, and if one segment is resolved as a partial key value then the subsequent segments should be resolved as any remaining key values.



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