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-24) Simplify how Relationships are expressed in CSDL

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

Michael Pizzo commented on ODATA-24:

Section 7.3; example should show "Partner" attribute. This is true in other examples as well.
Section 7.3.3, Nullable attribute. Should this be required to be false for collection valued navigation properties? I.e., the collection must exist, even if it is empty.
Section 7.3.5, If a navigation property navigates between entity types in the same entityset, it's not true containment. Containment is when each parent conceptually defines a separate entityset for its contained children.
Section 11.3, I don't know that I would specify multiple navigationpropertybindings for the same navigation property; there's not much value. If there may be more than one I would just omit it.
Section 11.4, edm:Entity Element. Does it make sense to support inheritance here, or should we say the property must be of the specified type? I suppose it's fine to make it derived, so the same model could be used to represent different schemas, some that use derived types, I just hadn't really thought about the case before.
Need to update core part I in two places; Section 3, Data Model talks about "association types" as being structural types, and section, "Entity Set Path Expressions" talks about deducing entitysets by backing association sets (needs to be updated to describe navigationpropertybindings).

> Simplify how Relationships are expressed in CSDL
> ------------------------------------------------
>                 Key: ODATA-24
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-24
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Assignee: Ralf Handl
>             Fix For: WD01
> Relationships are expressed in CSDL as binary associations with association sets; navigation properties reference these associations and describe target and source "ends" of these associations.
> The requirement of defining binary associations for each relationship makes the CSDL more verbose, harder to read, and moves the information that is interesting about the navigation property out of line.
> A simpler way to express navigation properties is summarized in the following presentation, presented at the first OData TC Meeting in July:  
> https://www.oasis-open.org/apps/org/workgroup/odata/download.php/46576/Association%20Simplification.pptx.
> A complete proposal would be the application of these concepts to [OData-CSDL].

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]