[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (ODATA-513) Special handling of derived types in the dynamic expression edm:Record. Why?
Special handling of derived types in the dynamic expression edm:Record. Why? ---------------------------------------------------------------------------- Key: ODATA-513 URL: http://tools.oasis-open.org/issues/browse/ODATA-513 Project: OASIS Open Data Protocol (OData) TC Issue Type: Improvement Components: OData CSDL Affects Versions: V4.0_CS, V4.0_ERRATA01 Reporter: Martin Zurmuehl Fix For: V4.0_CS, V4.0_ERRATA01 We have defined a special handling of derived types in dynamic expression edm:Record: 14.5.14 Expression edm:Record The edm:Record expression enables a new entity type or complex type instance to be constructed. A record expression contains zero or more edm:PropertyValue elements. For each single-valued property of the record construct's type that is neither nullable nor specifies a default value an edm:PropertyValue child element MUST be provided. For derived types this rule applies only to properties directly defined by the derived type. For collection-valued properties the absence of an edm:PropertyValue child element is equivalent to specifying a child element with an empty collection as its value. For me this special looks superfluous. -- 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]