[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-333) Visualize high level EDM overview through means of small diagrams to aid the reader on understanding base terms
[ http://tools.oasis-open.org/issues/browse/ODATA-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Drees updated ODATA-333:
-------------------------------
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 maybe as top-level hull for other "things"?
was:
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"?
Typos, typos ... a preview function might cut down mail traffic by half ;-)
> Visualize high level EDM overview through means of small diagrams to aid the reader on understanding base terms
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ODATA-333
> URL: http://tools.oasis-open.org/issues/browse/ODATA-333
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData Protocol
> Affects Versions: V4.0_WD01
> Reporter: Stefan Drees
> Priority: Minor
> Fix For: V4.0_WD01
>
>
> 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"?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]