[OASIS Issue Tracker] (ODATA-684) Define what it means for an added property to conflict with an existing dynamic property

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Michael Pizzo updated ODATA-684:
--------------------------------

    Summary: Define what it means for an added property to conflict with an existing dynamic property  (was: Define what it means for an adding property to conflict with an existing dynamic property)

> Define what it means for an added property to conflict with an existing dynamic property
> ----------------------------------------------------------------------------------------
>
>                 Key: ODATA-684
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-684
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol 
>    Affects Versions: V4.0_OS
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Priority: Minor
>             Fix For: V4.0_ERRATA01
>
>
> Section 5.2 of Protocol currently says that adding properties/nav props are "safe" schema changes (not requiring a version change) as long as the added property/nav prop  "does not conflict with an existing dynamic property".
> However, we don't say what "conflict" means.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)