odata message

Subject: [OASIS Issue Tracker] (ODATA-1226) Ambiguity with Capabilities.ChangeTracking annotation

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: odata@lists.oasis-open.org
Date: Tue, 18 Sep 2018 19:42:00 +0000 (UTC)

Evan Ireland created ODATA-1226:
-----------------------------------

             Summary: Ambiguity with Capabilities.ChangeTracking annotation
                 Key: ODATA-1226
                 URL: https://issues.oasis-open.org/browse/ODATA-1226
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: Vocabularies
            Reporter: Evan Ireland


Suppose I have an entity type with 2 structural properties (A, B) and 2 navigation properties (C, D).

Â

Then I use :

Â

<Annotation Term=âCapabilities.ChangeTrackingâ>

Â <Record>

ÂÂÂ <PropertyValue Property=âFilterablePropertiesâ/>

ÂÂÂÂÂ <Collection>

ÂÂÂÂÂÂÂ <PropertyPath>A</PropertyPath>

ÂÂÂÂÂ </Collection>

ÂÂÂ </Record>

</Annotation>

Â

Now it is clear that A is filterable and B is not. But how is the client to interpret ExpandableProperties not being specified (defaults to an empty Collection(NavigationPropertyPath))?

Â
 # The server omitted these properties from the annotation because they (C, D) are *all* expandable.
 # The server omitted these properties from the annotation because they (C, D) are *not* expandable.

Â

The interpretation of an empty collection here is ambiguous.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)