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: RE: Agenda for OData TC meeting on 2018-08-23 - chat transcript


[16:59] Room information was updated by: Ralf Handl (SAP SE)
Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday August 23, 2018 during 8-10 am PDT (17:00-19:00 CEST). For additional information, such as dial-in details and chat room, refer to [2]. For TC timeline, see [3]. Feel free to suggest additions or modifications. 
 
Thanks.
 
[1] Agenda
 
1.Roll call [8:00 am PT]
a.Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46270 
 
2.Approve agenda [8:05 am PT]
 
3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from August 16, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63732/odata-meeting-225_on-20180816-minutes.html 
 
4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]
a.Upcoming
i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2018-09-27
b.Pending
i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2018-07-26
 
5.Issues [8:20 am PT]
a.Data Aggregation: NEW or OPEN
i.ODATA-1215 Clarify datatype of virtual property $count
ii.ODATA-1207 Clarify need for @odata.id in nested response structures
iii.ODATA-947 Transformation for computing ratios with aggregated values (deferred to F2F)
iv.ODATA-945 Correct examples 53 and 54 (deferred to F2F)
 
b.Vocabularies: Annotation Examples and Example Values for types, parameters, request/response bodies (deferred to F2F)
i.ODATA-1194 Add term Core.Example to allow including annotation examples in term definitions
ii.ODATA-1200 ODATA-884 / Support sample values for types, parameters, request/response bodies
 
c.V4.01: NEW or OPEN 
i.ODATA-1210 CSDL ReturnType element needs to specify rules for Nullable and Collection with entity types
ii.ODATA-1203 Allow numeric indexes in Path constructs within annotations
iii.ODATA-1202 Deep update with nested delta items should allow Core.ContentID
iv.ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)
v.ODATA-1197 Chapter 21 Error Response: replace misleading "code" values with FOO or BAR
vi.ODATA-1196 Clarify update of media streams
vii.ODATA-1195 11.2.6.6: value of $search is search _expression_, not boolean _expression_
viii.ODATA-1191 Make sure that all model elements are annotatable
ix.ODATA-1190 Add matchesPattern as a $filter function
x.ODATA-1189 Conformance: Nullable for collections
xi.ODATA-1188 Allow using instance annotations in $select and $expand
xii.ODATA-1187 No way to bind nav prop on recursively nested (contained or complex) type
xiii.ODATA-1183 Allow Singletons to be null
xiv.ODATA-1180 Cast between enumeration types and integer types 
xv.ODATA-1177 Core: add term SchemaLocation
xvi.ODATA-1171 Consider using matrix parameters for filter segments
xvii.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts
xviii.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets
xix.ODATA-1148 PATCH with nested nav props should not remove omitted resources
xx.ODATA-1143 Extend the Property metatype to allow a type that is an EntityType.
xxi.ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path
xxii.ODATA-1135 Document use of JSON $schema
xxiii.ODATA-1088 Clarify effect of applying an Annotation to an element
 
d.Vocabularies: NEW or OPEN with concrete proposal
i.ODATA-1214 Annotate constructor actions (deferred to F2F)
ii.ODATA-1209 Term for original OData version of (auto-)converted $metadata
iii.ODATA-1204 Vocabularies Document references OData Version 4.01. Part 3: Common Schema Definition Language (CSDL)
iv.ODATA-1176 Capabilities: add new term SelectRestrictions
v.ODATA-1167 Add way to specify which batch formats (if any) are supported by a service
vi.ODATA-1064 Add ability to annotate collections to return only count and NextLink
 
e.Vocabularies: NEW or OPEN that need more discussion
i.ODATA-1208 Specify the finest possible granularity for Duration
ii.ODATA-1199 ODATA-884 / Add property SystemQueryOptions to call out supported system query options per request method
iii.ODATA-1193 Automated vocabulary checks indicate some potential issues
iv.ODATA-1177 Allow referencing a (JSON) schema for Edm.Untyped properties
v.ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term
vi.ODATA-1107 Introduce instance annotation to specify which types an instance "implements"
vii.ODATA-1099 Add annotations to describe custom query options and custom headers
viii.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
ix.ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
 
6.Next meetings [9:50 am PT]
a.Thursday August 30, 2018 during 8-10 am PDT (17:00-19:00 CEST)
b.Thursday September 06, 2018 during 8-10 am PDT (17:00-19:00 CEST)
 
7.AOB and wrap up [9:55 am PT]
 
[2] References
Chat room: http://webconf.soaphub.org/conf/room/odatatc 
Conference call & Screen sharing: https://lync.co.sap.com/meet/ralf.handl/Q4QB1098 
Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/63673/latest/TC%20meeting%20dial-in%20details.htm 
 
[3] Timeline
https://www.oasis-open.org/committees/download.php/62637/TC%20Timeline-2018-03-02.docx
[17:00] Ralf Handl (SAP SE): @Hubert: we are using Skype for Business
[17:00] Ralf Handl (SAP SE): Join by phone
 
+1 8552234162 "Canada" (SAP Dial-In)                          
 
+86 4008106069 "China All Cities" (SAP Dial-In)                           
 
+49 8005891883 "Germany" (SAP Dial-In)                     
 
+49 6922227996 "Germany Frankfurt" (SAP Dial-In)                   
 
+91 8071279160 "India Bangalore" (SAP Dial-In)                         
 
0008004404099 "India" (SAP Dial-In)                             
 
+65 67041630 "Singapore All Cities" (SAP Dial-In)                       
 
+44 3306068668 "United Kingdom All Cities" (SAP Dial-In)                        
 
+1 8664100244 "United States" (SAP Dial-In)                               
 
+1 2106069508 "United States All Cities" (SAP Dial-In)                               
 
Find a local number
 
 
 
Conference ID: 66549583
[17:01] Ralf Handl (SAP SE): In case the Skype link https://lync.co.sap.com/meet/ralf.handl/Q4QB1098 (still) does not work
[17:04] Ralf Handl (SAP SE): Voting Members: 5 of 10 (50%) (used for quorum calculation)
[17:04] Ralf Handl (SAP SE): @Hubert: I can try calling you from the Skype meeting, just tell me your phone number
[17:24] Ralf Handl (SAP SE): Voting Members: 6 of 10 (60%) (used for quorum calculation)
[17:25] Ralf Handl (SAP SE): 1.Roll call [8:00 am PT]
a.Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46270 
 
2.Approve agenda [8:05 am PT]
[17:26] Ralf Handl (SAP SE): New issue: https://issues.oasis-open.org/browse/ODATA-1216 - vocabulary-related
[17:26] Ralf Handl (SAP SE): No further changes, agenda is approved
[17:26] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from August 16, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63732/odata-meeting-225_on-20180816-minutes.html
[17:27] Ralf Handl (SAP SE): Minutes are approved
[17:28] Ralf Handl (SAP SE): Reminder: volunteer for minutes-keeper needed!
[17:28] Ralf Handl (SAP SE): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]
a.Upcoming
i.#0037 Concept for Google Protocol Buffers as a data format  Hubert Heijkers  2018-09-27
b.Pending
i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2018-07-26
[17:30] Ralf Handl (SAP SE): Mark provided new versions of the registration documents without redlining and handed them over to Chet Ensign
[17:30] Ralf Handl (SAP SE): 5.Issues [8:20 am PT]
a.Data Aggregation: NEW or OPEN
i.ODATA-1215 Clarify datatype of virtual property $count
[17:30] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1215
[17:41] Ralf Handl (SAP SE): ODATA-1215 is OPEN
[17:42] Gerald Krause (SAP): GET ~/Sales?$apply=aggregate($count as SalesCount)
[17:42] Gerald Krause (SAP): {
 
  "@odata.context": "$metadata#Sales(SalesCount)",
 
  "value": [
    { "@odata.id": null, "SalesCount": 8 }
  ]
 
}
[17:43] Gerald Krause (SAP): I move to resolve ODATA-1215 as proposed.
[17:44] Mark Biamonte (Progress): I second
[17:44] Ralf Handl (SAP SE): ODATA-1215 is RESOLVED as proposed
[17:45] Ralf Handl (SAP SE): ii.ODATA-1207 Clarify need for @odata.id in nested response structures
[17:45] Ralf Handl (SAP SE): Defer this to next time Mike can join us
[17:46] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1216
[17:46] Ralf Handl (SAP SE): Terms for POST/PATCH/PUT with system query options to shape response
[17:48] Ralf Handl (SAP SE): Add new terms
 
<Term Name="InsertSupport" Type="Core.InsertSupportType">
  <Annotation Term="Core.Description" String="Advanced insert capabilities" />
</Term>
<ComplexType Name="InsertSupportType">
  <Property Name="ExpandSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $expand with insert requests" />
  </Property>
  <Property Name="ExpandSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $select with insert requests" />
  </Property>
</ComplexType>
 
<Term Name="UpdateSupport" Type="Core.UpdateSupportType">
  <Annotation Term="Core.Description" String="Advanced update capabilities" />
</Term>
<ComplexType Name="UpdateSupportType">
  <Property Name="ExpandSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $expand with update requests" />
  </Property>
  <Property Name="ExpandSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $select with update requests" />
  </Property>
</ComplexType>
 
<Term Name="ActionSupport" Type="Core.ActionSupportType">
  <Annotation Term="Core.Description" String="Advanced Action capabilities" />
</Term>
<ComplexType Name="ActionSupportType">
  <Property Name="ExpandSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $expand with action invocation requests" />
  </Property>
  <Property Name="ExpandSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $select with action invocation requests" />
  </Property>
</ComplexType>
Description
[17:50] Ralf Handl (SAP SE): PATCH Orders(42)?$expand=Items($top=10)&$select=ID,Currency,TotalAmount,...
[17:54] Ralf Handl (SAP SE): George: why not needed for Delete?
[17:54] Ralf Handl (SAP SE): Ralf: DELETE always returns 204 No Content
[17:54] Ralf Handl (SAP SE): George: where would these be applied?
[17:55] Ralf Handl (SAP SE): Ralf: on Entity Container if all resources support it, otherwise on entity sets, singletons, actions
[17:58] Ralf Handl (SAP SE): ODATA-1216 is OPEN
[17:59] Ralf Handl (SAP SE): Updated proposal:
 
<Term Name="InsertSupport" Type="Core.InsertSupportType" AppliesTo="EntityContainer EntitySet Singleton Action">
  <Annotation Term="Core.Description" String="Advanced insert capabilities" />
</Term>
<ComplexType Name="InsertSupportType">
  <Property Name="ExpandSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $expand with insert requests" />
  </Property>
  <Property Name="SelectSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $select with insert requests" />
  </Property>
</ComplexType>
 
<Term Name="UpdateSupport" Type="Core.UpdateSupportType" AppliesTo="EntityContainer EntitySet Singleton Action">
  <Annotation Term="Core.Description" String="Advanced update capabilities" />
</Term>
<ComplexType Name="UpdateSupportType">
  <Property Name="ExpandSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $expand with update requests" />
  </Property>
  <Property Name="SelectSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $select with update requests" />
  </Property>
</ComplexType>
 
<Term Name="ActionSupport" Type="Core.ActionSupportType" AppliesTo="EntityContainer EntitySet Singleton Action">
  <Annotation Term="Core.Description" String="Advanced Action capabilities" />
</Term>
<ComplexType Name="ActionSupportType">
  <Property Name="ExpandSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $expand with action invocation requests" />
  </Property>
  <Property Name="SelectSupported" Type="Edm.Boolean" Nullable="false">
    <Annotation Term="Core.Description" String="Service supports $select with action invocation requests" />
  </Property>
</ComplexType>
[18:02] Ralf Handl (SAP SE): Default behavior: expect only new services to advertise the capability
[18:02] Ralf Handl (SAP SE): So would expect that absence of the annotation means not supported
[18:04] Ralf Handl (SAP SE): All agree that not specifying a default value for the "Supported" properties is the right choice
[18:04] Ralf Handl (SAP SE): It's also in line with the existing term BatchSupport
[18:05] Mark Biamonte (Progress): I move that ODATA-1216 be resolved as proposed
[18:05] George Ericson (Dell): Second
[18:06] Ralf Handl (SAP SE): ODATA-1216 is RESOLVED as proposed
[18:06] Ralf Handl (SAP SE): ii.ODATA-1209 Term for original OData version of (auto-)converted $metadata
[18:07] Ralf Handl (SAP SE): We have several cases of generic clients that can interact with V2 and V4 services and internally only use V4 syntax and semantics. One aspect of this is that the client converts the V2 $metadata into V4 $metadata and needs to "remember" whether the original protocol version - and the one to use for URL generation and payload serialization is something else than V4.
[18:09] Ralf Handl (SAP SE): Mark: seems to be an implementation detail
[18:10] Ralf Handl (SAP SE): George: not run into that problem
[18:10] Ralf Handl (SAP SE): Will close this without action
[18:11] Ralf Handl (SAP SE): iii.ODATA-1204 Vocabularies Document references OData Version 4.01. Part 3: Common Schema Definition Language (CSDL)
[18:11] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1204
[18:12] Ralf Handl (SAP SE): Part 3 doesn't exist any more
[18:12] Ralf Handl (SAP SE): Proposal:
 
In the Related Work section of the OData Vocabularies document remove the sub-bullet that references 
 
 OData Version 4.01. Part 3: Common Schema Definition Language (CSDL)
 
and replace with references to
 
OData Common Schema Definition Language (CSDL) JSON Representation Version 4.01
OData Common Schema Definition Language (CSDL) XML Representation Version 4.01
[18:12] Ralf Handl (SAP SE): ODATA-1204 is OPEN
[18:13] George Ericson (Dell): Motion to approve 1204 as proposed
[18:13] Mark Biamonte (Progress): I second
[18:13] Ralf Handl (SAP SE): ODATA-1204 is RESOLVED as proposed
[18:14] Ralf Handl (SAP SE): iv.ODATA-1176 Capabilities: add new term SelectRestrictions
[18:14] Ralf Handl (SAP SE): Similar to other xxxRestrictions add a SelectRestrictions structured term with (for now) a single property Selectable of type Boolean:
 
Example:
 
<Annotation Term="Capabilities.SelectRestrictions">
  <Record>
    <PropertyValue Property="Selectable" Bool="false" />
  </Record>
 </Annotation>
[18:15] Ralf Handl (SAP SE): Proposal
 
<Term Name="SelectRestrictions" Type="Capabilities.SelectRestrictionsType" AppliesTo="EntitySet Singleton">
  <Annotation Term="Core.Description" String="Restrictions on selecting properties" />
</Term>
<ComplexType Name="SelectRestrictionsType">
  <Property Name="Selectable" Type="Edm.Boolean" DefaultValue="true">
    <Annotation Term="Core.Description" String="$select is supported" />
  </Property>
</ComplexType>
[18:19] Ralf Handl (SAP SE): Alternative term would be "SelectSupported" similar to existing TopSupported:
 
      <Term Name="TopSupported" Type="Core.Tag" DefaultValue="true" AppliesTo="EntitySet">
        <Annotation Term="Core.Description" String="Supports $top" />
      </Term>
[18:21] Ralf Handl (SAP SE): New proposal:
 
      <Term Name="SelectSupported" Type="Core.Tag" Nullable="true" DefaultValue="true" AppliesTo="EntitySet">
        <Annotation Term="Core.Description" String="Supports $select" />
      </Term>
[18:21] Ralf Handl (SAP SE): Newer proposal:
 
      <Term Name="SelectSupported" Type="Core.Tag" Nullable="false" DefaultValue="true" AppliesTo="EntitySet">
        <Annotation Term="Core.Description" String="Supports $select" />
      </Term>
[18:22] Ralf Handl (SAP SE): Even newer proposal:
 
      <Term Name="SelectSupported" Type="Core.Tag" Nullable="false" DefaultValue="true" AppliesTo="EntitySet Singleton">
        <Annotation Term="Core.Description" String="Supports $select" />
      </Term>
[18:22] George Ericson (Dell): Motion to approve 1176 as modified
[18:22] Mark Biamonte (Progress): I second
[18:23] Ralf Handl (SAP SE): ODATA-1176 is RESOLVED as proposed
[18:24] Ralf Handl (SAP SE): v.ODATA-1167 Add way to specify which batch formats (if any) are supported by a service
[18:24] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1167
[18:24] Ralf Handl (SAP SE): Add a SupportedFormats property to the BatchSupportType:
 
<Property Name="SupportedFormats" Type="Collection(Edm.String)" Nullable="false">
  <Annotation Term="Core.Description" String="Media types of supported formats for $batch" />
  <Annotation Term="Core.IsMediaType" />
  <Annotation Term="Validation.AllowedValues">
    <Collection>
      <Record>
        <PropertyValue Property="Value" String="multipart/mixed" />
        <Annotation Term="Core.Description"
          String="Multipart Batch Format, see http://docs.oasis-open.org/odata/odata/v4.01/cs01/part1-protocol/odata-v4.01-cs01-part1-protocol.html#sec_MultipartBatchFormat" />
      </Record>
      <Record>
        <PropertyValue Property="Value" String="application/json" />
        <Annotation Term="Core.Description"
          String="JSON Batch Format, see http://docs.oasis-open.org/odata/odata-json-format/v4.01/cs01/odata-json-format-v4.01-cs01.html#sec_BatchRequestsandResponses" />
      </Record>
    </Collection>
  </Annotation>
</Property>
[18:26] Ralf Handl (SAP SE): Short form:
 
Add a SupportedFormats property to the BatchSupportType:
 
<Property Name="SupportedFormats" Type="Collection(Edm.String)" Nullable="false">
  <Annotation Term="Core.Description" String="Media types of supported formats for $batch" />
  <Annotation Term="Core.IsMediaType" />
</Property>
[18:26] Ralf Handl (SAP SE): plus restriction on allowed values:
 
  <Annotation Term="Validation.AllowedValues">
    <Collection>
      <Record>
        <PropertyValue Property="Value" String="multipart/mixed" />
        <Annotation Term="Core.Description"
          String="Multipart Batch Format, see http://docs.oasis-open.org/odata/odata/v4.01/cs01/part1-protocol/odata-v4.01-cs01-part1-protocol.html#sec_MultipartBatchFormat" />
      </Record>
      <Record>
        <PropertyValue Property="Value" String="application/json" />
        <Annotation Term="Core.Description"
          String="JSON Batch Format, see http://docs.oasis-open.org/odata/odata-json-format/v4.01/cs01/odata-json-format-v4.01-cs01.html#sec_BatchRequestsandResponses" />
      </Record>
    </Collection>
  </Annotation>
[18:28] Ralf Handl (SAP SE): Annotation example:
 
@Capabilities.BatchSupport:{
  SupportedFormats: ["application/json", "multipart/mixed" ]
}
[18:31] Ralf Handl (SAP SE): ODATA-1167 is OPEN
[18:34] Mark Biamonte (Progress): I move that ODATA-1167 be resolved as proposed
[18:34] Ramesh Reddy(Red Hat): I second
[18:35] Ralf Handl (SAP SE): ODATA-1167 is RESOLVED as proposed
[18:35] Ralf Handl (SAP SE): vi.ODATA-1064 Add ability to annotate collections to return only count and NextLink
[18:36] Ralf Handl (SAP SE): George: agreement with Mike reached, wait for Mike to recap the proposal
[18:37] Ralf Handl (SAP SE): c.V4.01: NEW or OPEN 
i.ODATA-1210 CSDL ReturnType element needs to specify rules for Nullable and Collection with entity types
[18:37] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1210
[18:37] Ralf Handl (SAP SE): Description
It is reasonable to assume:
 
A collection of entities never contains null because the null entity has no meaning.
A function returning a single entity would have to return 204 No Content to signal no entity returned, similar to following a single-valued navigation property with nothing associated at that point in time.
Therefore:
 
A function returning entities behaves like a navigation property.
A function returning structured or primitive instances behaves like a structural property.
In regard to CSDL XML/JSON 4.01, we should specify:
 
Nullable should never be specified for a Collection(SomeEntityType), and it must always be considered to be false by default. This would bring consistency with navigation properties.
 
Going one step further, we should probably apply this reasoning to Parameter elements, i.e. a parameter of type Collection(SomeEntityType) should also never have an explicit Nullable facet.
[18:39] Ralf Handl (SAP SE): ODATA-1210 is OPEN
[18:51] Mark Biamonte (Progress): I move ODATA-1210 be resolved as proposed
[18:51] Ramesh Reddy(Red Hat): I second
[18:51] Ralf Handl (SAP SE): ODATA-1210 is RESOLVED as proposed
[18:52] Ralf Handl (SAP SE): ii.ODATA-1203 Allow numeric indexes in Path constructs within annotations
[18:52] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1203
[18:52] Ralf Handl (SAP SE): Description
 
With ODATA-1061 we allowed key segments in parenthesis syntax after path segments that identify a collection of entities.
 
A logical extension is allowing numeric indexes to reference entities or complex type instances within a collection:
 
<Annotation Term="Some.Term" Path="ComplexCollection/0/SomeProperty" />
This would address the first item in the collection. If the item is structured, additional path segments can follow after the index segment.
[18:55] Ralf Handl (SAP SE): Proposal
 
Path expressions allow index segments after path segments that identify a collection. The index is zero-based and MUST be an integer literal. Negative integers count from the end of the collection, with -1 representing the last item in the collection.
 
This key syntax can only be used in Path expressions as only these refer to instance values.
 
It cannot be used in expressions for model references, i.e. PropertyPath, NavigationPropertyPath, AnnotationPath, and their abstract supertypes AnyPropertyPath and AnyPath.
 
Optional extension: this could be generalized to allow path expressions as indexes if we make path expressions to be used as an index distinguishable from path expressions that navigate into structured collection items. The natural choice would be the # symbol:
 
<Annotation Term="Some.Term" Path="ComplexCollection/#(ComplexPropertyNextToComplexCollection/IntegerProperty)/SomePropertyofComplexItem" />
The # symbol so far is only used to separate a term from a qualifier, so the sequence /#( cannot appear so far. Using parentheses around the path to the index is necessary to mark the end of the index path.
 
An even more powerful alternative would be to add a templating-style syntax using e.g. curly braces
 
<Annotation Term="Some.Term" Path="ComplexCollection/{path/to/something/that/results/in/a/valid/path/segment}/SomePropertyofComplexItem" />
Here the result of evaluating the path _expression_ within the curly braces is then used as a path segment for the "outer" path - of course with nesting. If the result is a number, it is treated as an index for the collection, if it is a string, it is treated as a path.
[18:58] Ralf Handl (SAP SE): ODATA-1203 is OPEN
[18:59] Ralf Handl (SAP SE): 6.Next meetings [9:50 am PT]
a.Thursday August 30, 2018 during 8-10 am PDT (17:00-19:00 CEST)
b.Thursday September 06, 2018 during 8-10 am PDT (17:00-19:00 CEST)
[18:59] Ralf Handl (SAP SE): George may not be able to attend on September 06
[19:00] Ralf Handl (SAP SE): 7.AOB and wrap up [9:55 am PT]
[19:00] Ralf Handl (SAP SE): Hotels for F2F
[19:01] Ralf Handl (SAP SE): Name of hotel: Element Seattle Redmond
Street: 15220 NE SHEN ST SUITE 100
Postal code/City: 98052 Redmond (United States)
[19:01] Ralf Handl (SAP SE): That's where Gerald and I will stay
[19:02] Ralf Handl (SAP SE): Meeting is adjourned

 

 

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 22. August 2018 17:11
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-08-23

 

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday August 23, 2018 during 8-10 am PDT (17:00-19:00 CEST). For additional information, such as dial-in details and chat room, refer to [2]. For TC timeline, see [3]. Feel free to suggest additions or modifications.

 

Thanks.

 

[1] Agenda

 

1.        Roll call [8:00 am PT]

    1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=46270

 

2.        Approve agenda [8:05 am PT]

 

3.        Approve minutes from previous meeting(s) [8:10 am PT]

    1. Minutes from August 16, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63732/odata-meeting-225_on-20180816-minutes.html

 

4.        Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php?sort_field=due_closed_date] [8:15am PT]

    1. Upcoming

                                  i.    #0037 Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2018-09-27

    1. Pending

                                  i.    #0036 Register the OData- headers and preferences with IANA – Mark Biamonte – 2018-07-26

 

5.        Issues [8:20 am PT]

    1. Data Aggregation: NEW or OPEN

                                  i.    ODATA-1215 Clarify datatype of virtual property $count

                                 ii.    ODATA-1207 Clarify need for @odata.id in nested response structures

                                iii.    ODATA-947 Transformation for computing ratios with aggregated values (deferred to F2F)

                                iv.    ODATA-945 Correct examples 53 and 54 (deferred to F2F)

 

    1. Vocabularies: Annotation Examples and Example Values for types, parameters, request/response bodies (deferred to F2F)

                                  i.    ODATA-1194 Add term Core.Example to allow including annotation examples in term definitions

                                 ii.    ODATA-1200 ODATA-884 / Support sample values for types, parameters, request/response bodies

 

    1. V4.01: NEW or OPEN

                                  i.    ODATA-1210 CSDL ReturnType element needs to specify rules for Nullable and Collection with entity types

                                 ii.    ODATA-1203 Allow numeric indexes in Path constructs within annotations

                                iii.    ODATA-1202 Deep update with nested delta items should allow Core.ContentID

                                iv.    ODATA-1198 ETag handling deviations from RFC7232 are avoidable if we consider two kinds of ETag (ETag in response header and ETag in response payload)

                                 v.    ODATA-1197 Chapter 21 Error Response: replace misleading "code" values with FOO or BAR

                                vi.    ODATA-1196 Clarify update of media streams

                               vii.    ODATA-1195 11.2.6.6: value of $search is search _expression_, not boolean _expression_

                              viii.    ODATA-1191 Make sure that all model elements are annotatable

                                ix.    ODATA-1190 Add matchesPattern as a $filter function

                                 x.    ODATA-1189 Conformance: Nullable for collections

                                xi.    ODATA-1188 Allow using instance annotations in $select and $expand

                               xii.    ODATA-1187 No way to bind nav prop on recursively nested (contained or complex) type

                              xiii.    ODATA-1183 Allow Singletons to be null

                              xiv.    ODATA-1180 Cast between enumeration types and integer types

                               xv.    ODATA-1177 Core: add term SchemaLocation

                              xvi.    ODATA-1171 Consider using matrix parameters for filter segments

                             xvii.    ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts

                            xviii.    ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets

                              xix.    ODATA-1148 PATCH with nested nav props should not remove omitted resources

                               xx.    ODATA-1143 Extend the Property metatype to allow a type that is an EntityType.

                              xxi.    ODATA-1141 Upsert: clarify upsert along nullable single-valued navigation path

                             xxii.    ODATA-1135 Document use of JSON $schema

                            xxiii.    ODATA-1088 Clarify effect of applying an Annotation to an element

 

    1. Vocabularies: NEW or OPEN with concrete proposal

                                  i.    ODATA-1214 Annotate constructor actions (deferred to F2F)

                                 ii.    ODATA-1209 Term for original OData version of (auto-)converted $metadata

                                iii.    ODATA-1204 Vocabularies Document references OData Version 4.01. Part 3: Common Schema Definition Language (CSDL)

                                iv.    ODATA-1176 Capabilities: add new term SelectRestrictions

                                 v.    ODATA-1167 Add way to specify which batch formats (if any) are supported by a service

                                vi.    ODATA-1064 Add ability to annotate collections to return only count and NextLink

 

    1. Vocabularies: NEW or OPEN that need more discussion

                                  i.    ODATA-1208 Specify the finest possible granularity for Duration

                                 ii.    ODATA-1199 ODATA-884 / Add property SystemQueryOptions to call out supported system query options per request method

                                iii.    ODATA-1193 Automated vocabulary checks indicate some potential issues

                                iv.    ODATA-1177 Allow referencing a (JSON) schema for Edm.Untyped properties

                                 v.    ODATA-1140 ODATA-884 / Add details to HTTPResponseCode term

                                vi.    ODATA-1107 Introduce instance annotation to specify which types an instance "implements"

                               vii.    ODATA-1099 Add annotations to describe custom query options and custom headers

                              viii.    ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

                                ix.    ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

 

6.        Next meetings [9:50 am PT]

    1. Thursday August 30, 2018 during 8-10 am PDT (17:00-19:00 CEST)
    2. Thursday September 06, 2018 during 8-10 am PDT (17:00-19:00 CEST)

 

7.        AOB and wrap up [9:55 am PT]

 

[2] References

 

[3] Timeline



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