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] Updated: (ODATA-123) Referential constraint: prose text does not properly reflect case of optional principal


     [ http://tools.oasis-open.org/issues/browse/ODATA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-123:
-----------------------------

       Proposal: 
Rephrase last sentence in section 11.4 from
    In the example that follows, the category must exist for a product in that category to exist: 
to
    In the example that follows, the CategoryID of a Product entity must either be null or contain the ID of an existing category:

Rephrase second sentence in first paragraph of section 11.6 from
    The entity on this end of the association may only exist if an entity on the opposite end of the association exists. 
to
   If the multiplicity of the principal association end is 1, the entity on the dependent end of the association may only exist if an entity on the principal end of the association exists. 


  was:Reformulate sections 11.4 and 11.6 accordingly, ideally add example that highlights this fact, e.g. Issue-Assignee :-)

    Environment: [Proposed]

> Referential constraint: prose text does not properly reflect case of optional principal
> ---------------------------------------------------------------------------------------
>
>                 Key: ODATA-123
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-123
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>            Priority: Minor
>             Fix For: WD01
>
>
> A referential constraint is explicitly allowed and definitely makes sense also in cases where the principal cardinality is 0..1, i.e. when the "dependent" entity may have no "principal".
> It is just a constraint on property values of the "dependent" entity: if the entity is associated to a "principal", the dependent properties must have the same value as the corresponding principal properties.

-- 
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]