[OASIS Issue Tracker] (ODATA-651) Chapter 3: Rephrase "An entity can be a member of at most one entity set at any given point in time"

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

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

Ralf Handl updated ODATA-651:
-----------------------------

    Proposal: 
Protocol, chapter 3:

[Keep]   An entity's key uniquely identifies the entity within an entity set. 
[New]    If multiple entity sets use the same entity type, the same combination of key values can appear in more than one entity set and identifies different entities, one per entity set where this key combination appears. Each of these entities has a different entity-id (link to section 4.1).
[Delete] An entity can be a member of at most one entity set at any given point in time. 
[Keep]   Entity sets provide entry points into the data model. 

Protocol, chapter 4.1:
[Delete] Whereas entities in the Data Model are uniquely identified by their key values within an entity set, entities within a payload are identified by a durable, opaque, globally unique entity-id.
[New]    Whereas entities within an entity set are uniquely identified by their key values, entities are also uniquely identified by a durable, opaque, globally unique entity-id.

CSDL, chapter 13:

[Remove] Note: although a model may expose multiple entity sets of the same type, an entity can be a member of at most one entity set, see [OData-Protocol].

  was:
Protocol, chapter 3:

[Keep]   An entity's key uniquely identifies the entity within an entity set. 
[New]    If multiple entity sets use the same entity type, the same combination of key values can appear in more than one entity set and identifies different entities, one per entity set where this key combination appears. Each of these entities has a different entity-id (link to section 4.1).
[Delete] An entity can be a member of at most one entity set at any given point in time. 
[Keep]   Entity sets provide entry points into the data model. 

Protocol, chapter 4.1:
[Delete] Whereas entities in the Data Model are uniquely identified by their key values within an entity set, entities within a payload are identified by a durable, opaque, globally unique entity-id.
[New]    Whereas entities within an entity set are uniquely identified by their key values, entities across the entire service are uniquely identified by a durable, opaque, globally unique entity-id.

CSDL, chapter 13:

[Remove] Note: although a model may expose multiple entity sets of the same type, an entity can be a member of at most one entity set, see [OData-Protocol].


> Chapter 3: Rephrase "An entity can be a member of at most one entity set at any given point in time"
> ----------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-651
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-651
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL, OData Protocol 
>    Affects Versions: V4.0_OS
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_ERRATA01
>
>
> The sentence "An entity can be a member of at most one entity set at any given point in time" is causing some confusion. Replace it with a more verbose description of what we want to achieve.
> An incomplete version of this sentence is included in CSDL and should be removed to avoid confusion.



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