OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (ODATA-513) Special handling of derived types in the dynamic expression edm:Record. Why?

    [ http://tools.oasis-open.org/issues/browse/ODATA-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34753#action_34753 ] 

Michael Pizzo commented on ODATA-513:

I think this is a fall-out of the rule we had that your annotations only define mapping for the defined properties ,not the properties derived from the base type.

I.e., we said that if I had a base complex type "persontype" and derived types "customertype" and "salespersontype", then I would have separate "person", "customer" and "salesperson" terms, and I would annotate an entity by applying each term separately, mapping only those PropertyValues defined in that type (not those derived from the base type).

I'm not sure that rule is still there, but I think it needs to be.

> 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: Bug
>          Components: OData CSDL
>    Affects Versions: V4.0_CS01
>         Environment: [Proposed]
>            Reporter: Martin Zurmuehl
>             Fix For: V4.0_CSD03
> 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 handling of the derived types 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]