Minor This is based on my review of the latest revision [OData Core Part 1: Protocol, Version 4.0](https://www.oasis-open.org/committees/download.php/48762/odata-core-v4.0-wd01-part1-protocol-current-2013-4-5MP.docx).
The section on entity data model must be hard to read, as it tries to describe a survival guide for a generic model, where it comes to the nitty-gritty.
That's ok. I am fine with that. First we really need the nitty-gritty details and second we are not writing children books.
But maybe we can do better.
A) One problem for the astute reader seems to lie in the details of adjectives/attributes to the main terms.
B) Another are related terms we introduce.
C) Third the topological complexity, that cries for a parallel depict through a picture or some pictures.
To A)
Differentiating between an Entity and a Named Entity is one example
To B)
The wrapper in specific where to segragate from the Entity Container ...
To C)
I may volunteer to paint some 
maybe during the prep phase of the face to face in Walldorf as to receive early feedback and converge fast.
Assume one for entity -> entities
Another for relationships external and derived
Yet another for containers and their objects (entities, actions, functions) showing also wrappers maybe as top-level hull for other "things"?
| Field | Original Value | New Value |
|---|---|---|
| Description |
This is based on my review of the latest revision [OData Core Part 1: Protocol, Version 4.0](https://www.oasis-open.org/committees/download.php/48762/odata-core-v4.0-wd01-part1-protocol-current-2013-4-5MP.docx). The section on entity data model must be hard to read, as it tries to describe a survival guide for a generic model, where it comes to the nitty-gritty. That's ok. I am fine with that. First we really need the nitty-gritty details and second we are not writing children books. But maybe we can do better. A) One problem for the astute reader seems to lie in the details of adjectives/attributes to the main terms. B) Another are related terms we introduce. C) Third the topological complexity, that cries for a parallel depict through a picture or some pictures. To A) Differentiating between an Entity and a Named Entity is one example To B) The wrapper in specific where to segragate from the Entity Container ... To C) I may volunteer to paint some :-) maybe during the prep phase of the face to face in Walldorf as to receive early feedback and converge fast. Assume one for entity -> entities Another for relationships external and derived Yet another for containers and their objects (entities, actions, functions) showing also wrappers may as top-level hull for other "things"? |
This is based on my review of the latest revision [OData Core Part 1: Protocol, Version 4.0](https://www.oasis-open.org/committees/download.php/48762/odata-core-v4.0-wd01-part1-protocol-current-2013-4-5MP.docx). The section on entity data model must be hard to read, as it tries to describe a survival guide for a generic model, where it comes to the nitty-gritty. That's ok. I am fine with that. First we really need the nitty-gritty details and second we are not writing children books. But maybe we can do better. A) One problem for the astute reader seems to lie in the details of adjectives/attributes to the main terms. B) Another are related terms we introduce. C) Third the topological complexity, that cries for a parallel depict through a picture or some pictures. To A) Differentiating between an Entity and a Named Entity is one example To B) The wrapper in specific where to segragate from the Entity Container ... To C) I may volunteer to paint some :-) maybe during the prep phase of the face to face in Walldorf as to receive early feedback and converge fast. Assume one for entity -> entities Another for relationships external and derived Yet another for containers and their objects (entities, actions, functions) showing also wrappers maybe as top-level hull for other "things"? |
To C: wouldn't the ER diagram of the Metadata Service (ODATA-126) be that picture?
| Proposal | Visualize high level EDM overview through means of small diagrams to aid the reader on understanding base terms | Close without further action as the Metadata Service chapter contains small diagrams that explain the relationship of CSDL elements. |
| Environment | [Proposed] |
inserted a now in above proposal to make clear, that this change has been introduced after the creation of tis issue and thus the issue has already been resolved (by providing adequate info in a different place).
If we already did resolve the sub issues A and B I am in favor of closing the issue as proposed, but would kindly suggest that we document this (point to a different issue probably one reported by Patrick relevant to the edm "intro" where the resolution took place.
If A and B have not been resolved, ... I might also be willing to second closure, as Mike once stated, that this short edm term "listing" was never meant to replace the explanations in the CSDL etc. This should only be clear to everyone when we close this issue.
| Proposal | Close without further action as the Metadata Service chapter contains small diagrams that explain the relationship of CSDL elements. | Close without further action as the Metadata Service chapter now contains small diagrams that explain the relationship of CSDL elements. |
| Resolution | Accepted in F2F 2013-06-13 | |
| Status | New [ 10000 ] | Open [ 1 ] |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Environment | [Proposed] | [Closed] |
| Status | Closed [ 6 ] | Open [ 1 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Applied [ 10002 ] |
| Status | Applied [ 10002 ] | Closed [ 6 ] |
| Resolution | Accepted in F2F 2013-06-13 |
Accepted in F2F 2013-06-13 Accepted: https://www.oasis-open.org/committees/download.php/49557/odata-meeting-41_on-20130613_14-F2F-minutes.html#odata-333 |
Reference to meeting #41 minute link fragment documenting the approval of application has been added.
Typos, typos ... a preview function might cut down mail traffic by half