[OASIS Issue Tracker] (ODATA-798) Semantic Key or Alternate Key for entity types

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

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

Michael Pizzo updated ODATA-798:
--------------------------------

    Proposal: 
Adopt the following community vocabulary by adding the term to the OData Core vocabulary and describing the behavior in [URL Conventions]:
https://github.com/OData/vocabularies/blob/master/OData.Community.Keys.V1.md 
https://github.com/OData/vocabularies/blob/master/OData.Community.Keys.V1.xml 

AppliesTo should be EntityType and EntiySet. NavigationProperty would be an exception, is somewhat implied by entity set, and AppliesTo does not prohibit other uses.

Contact the existing community vocabulary owners to say that the term has been adopted by the OData Core vocabulary and should be used moving forward.

  was:
Adopt the following community vocabulary by adding the term to the OData Core vocabulary and describing the behavior in [URL Conventions]:
https://github.com/OData/vocabularies/blob/master/OData.Community.Keys.V1.md 
https://github.com/OData/vocabularies/blob/master/OData.Community.Keys.V1.xml 

Contact the existing community vocabulary owners to say that the term has been adopted by the OData Core vocabulary and should be used moving forward.


> Semantic Key or Alternate Key for entity types
> ----------------------------------------------
>
>                 Key: ODATA-798
>                 URL: https://issues.oasis-open.org/browse/ODATA-798
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL, OData URL Conventions
>    Affects Versions: V4.0_ERRATA02
>         Environment: New Query Capabilities
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: Extension
>             Fix For: V4.01_WD01
>
>
> Sometimes an entity type has a technical unique key, e.g. a sequence number or a guid, as well as one or more "semantic" or "alternate" keys, e.g. a User could be identified via a UserID or alternatively via an EmailAddress, or a Person could be identified via a Country+PassportNumber combination or a Country+SSN combination.
> These "semantic" or "alternate" keys may include nullable properties (you may not know a person's SSN, but if you know it, it identifies the person), and there could be more than one of them, each consisting of a different set of properties.



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