[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [odata-comment] Conflicting declarations about EntityContainer in CSDL
|
Hi Wei, Thank you for your comment. As stated in section 13 the metadata document of an OData service must define exactly one entity container.
Prior versions of OData allowed more than one entity container per schema. This feature was rarely used, and with the introduction of cross-service references
it seemed to be no longer necessary. So we added the restriction to one entity container but kept its position as a schema child to avoid unnecessary confusion for consumers of prior OData versions. It also allowed to keep the naming and cross-referencing
rules which otherwise would have had to be special-cased for the entity container. Thanks! --Ralf From: odata-comment@lists.oasis-open.org [mailto:odata-comment@lists.oasis-open.org]
On Behalf Of Wei Wei Hi, Dear Committee Members, I am working on a hypermedia-driven OData client. While reading the standard document, I found there’re conflicting declarations about EntityContainer. Section 13 Each metadata document used to describe an OData service MUST define
*exactly one* entity container. Section 3.2 The edmx:DataServices element MUST contain *one or more* edm:Schema elements
which define the schemas exposed by the OData service. Section 5.1 The edm:Schema element contains *one or more* of the following elements:
... … There’s ambiguity about *how many EntityContainers* could be specified in one metadata document. However, it make sense to have exactly one EntityContainer per service. Shall we consider moving the EntityContainer one level up to
DataServices? Thanks Wei |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]