[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (ODATA-198) Allow Type="Any" and Type="Collection(Any)" for NavigationProperty elements
Allow Type="Any" and Type="Collection(Any)" for NavigationProperty elements
---------------------------------------------------------------------------
Key: ODATA-198
URL: http://tools.oasis-open.org/issues/browse/ODATA-198
Project: OASIS Open Data Protocol (OData) TC
Issue Type: Improvement
Components: OData CSDL v1.0
Affects Versions: WD01
Environment: [Proposed]
Reporter: Ralf Handl
Fix For: WD01
We have encountered several situations where we know at design time that an entity will have an association to another entity (in the same or a different service), but we don't know the exact type of the related entity until run-time.
One example are notifications about "events" for some entity the consumer is interested in. The "events" service will be stable over time and may notify about events on business entities that weren't even modeled at the time the "events" service was published.
This is comparable to defining Named Resource Properties with the additional information that the named resource is guaranteed to be an OData entity or a collection of OData entities.
--
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]