RE: Agenda for OData TC meeting on 2018-09-10

[16:57] 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 September 13, 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=46273

2.Approve agenda [8:05 am PT]

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

a.Minutes from Septenber 06, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63900/odata-meeting-228_on-20180906-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.In progress

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

5.Issues [8:20 am PT]

a.APPLIED

i.

b.Vocabularies: NEW or OPEN with concrete proposal

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

c.V4.01: NEW or OPEN

i.ODATA-1189 Conformance: Nullable for collections

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

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

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

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

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

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

viii.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)

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

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

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-1171 Consider using matrix parameters for filter segments

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

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

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

xviii.ODATA-1135 Document use of JSON $schema

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

d.Data Aggregation: NEW or OPEN (deferred to F2F)

i.ODATA-1218 Transformations for recursive hierarchy processing

ii.ODATA-1207 Clarify need for @odata.id in nested response structures (deferred to F2F)

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

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

e.Vocabularies: deferred to F2F  examples, custom headers and query options, error codes

i.ODATA-1216 Terms for POST/PATCH/PUT with system query options to shape response

ii.ODATA-1214 Annotate constructor actions

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

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

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

vi.ODATA-1176 Capabilities: add new term SelectSupported

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

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

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

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

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

f.Vocabularies: NEW or OPEN that need more discussion

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

6.Next meetings [9:50 am PT]

a.Thursday September 20, 2018 during 8-10 am PDT (17:00-19:00 CEST)

b.Face-to-Face Thursday & Friday September 27 & 28, 2018 during 9-17 am PDT & 9-15 PDT (18:00-02:00 CEST & 18:00-00: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:01] Ralf Handl (SAP SE): Voting Members: 4 of 10 (40%) (used for quorum calculation)

[17:02] Ralf Handl (SAP SE): Voting Members: 5 of 10 (50%) (used for quorum calculation)

[17:03] Ralf Handl (SAP SE): Voting Members: 6 of 10 (60%) (used for quorum calculation)

[17:03] Ralf Handl (SAP SE): Quorum achieved: yes

[17:04] Ralf Handl (SAP SE): @Ted: do you want to join the telephone conference?

[17:04] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT]

[17:06] Ralf Handl (SAP SE): New issues opened since Monday:

- ODATA-1221 Apply, as much as possible, our JSON Format to our annotations as well

- ODATA-1220 Instance annotations section only refers to the XML CSDL, not JSON CSDL

- ODATA-1219 Be more explicit about the purpose of $DefaultValue in a Term definition

[17:07] Ralf Handl (SAP SE): No more changes, agenda is approved

[17:07] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT]

a.Minutes from Septenber 06, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63900/odata-meeting-228_on-20180906-minutes.html

[17:07] Ralf Handl (SAP SE): Fabulous

[17:07] Ralf Handl (SAP SE): Fine!

[17:07] Ralf Handl (SAP SE): Minutes are approved

[17:07] Ted Jones (Red Hat): Troubles dialing in Ralf.. just a sec

[17:08] 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.In progress

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

[17:09] Ralf Handl (SAP SE): Feedback from IANA: why no OData- prefix for Isolation and EntityID

[17:10] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1223 - Add OData- prefix back to Entity-Id and Isolation headers

[17:10] Ralf Handl (SAP SE): ODATA-1223 is OPEN

[17:28] Ralf Handl (SAP SE): Discussion on EntityID versus Location header, Hubert to open an issue to make EntityID header optional if value is identical to Location header value

[17:29] Ralf Handl (SAP SE): Discussion on Isolation to be tracked in ODATA-1223

[17:30] Ralf Handl (SAP SE): Mike to look into possible value lists for "Isolation", e.g. SQL isolation levels

[17:30] Ralf Handl (SAP SE): 5.Issues [8:20 am PT]

a.APPLIED

i.

b.Vocabularies: NEW or OPEN with concrete proposal

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

[17:31] Ralf Handl (SAP SE): https://issues.oasis-open.org/issues/?jql=project%20%3D%20ODATA%20AND%20status%20in%20(Open%2C%20New)%20AND%20component%20%3D%20Vocabularies%20AND%20environment%20~%20Proposed%20ORDER%20BY%20key%20DESC

[17:32] Ralf Handl (SAP SE): 5.b.i should actually reference https://issues.oasis-open.org/browse/ODATA-1222 - Validation: add terms minItems and maxItems

[17:32] Ralf Handl (SAP SE): Add terms minItems and maxItems that apply to anything collection-valued and allows specifying the expected minimum and maximum number of items in the collection.

Similar to minimum and maximum this is along the lines of JSON Schema minItems and maxItems, see https://tools.ietf.org/html/draft-handrews-json-schema-validation-01#section-6.4.3

[17:33] Ralf Handl (SAP SE): Hubert: why lowerCamelCase?

[17:34] Ralf Handl (SAP SE): Ralf: typo, should be MinItems and MaxItems to be in sync with our other terms

[17:34] Ralf Handl (SAP SE): ODATA-1222 is OPEN

[17:36] Hubert Heijkers (IBM): I move to resolve ODATA-1222 as proposed

[17:36] Stefan Hagen: I second

[17:37] Ralf Handl (SAP SE): ODATA-1222 is RESOLVED as proposed

[17:38] Ralf Handl (SAP SE): Next: https://issues.oasis-open.org/browse/ODATA-1221 - Apply, as much as possible, our JSON Format to our annotations as well

[17:43] Ralf Handl (SAP SE): {

      "$DateTimeOffset": "2013-04-08T23:00:00.0Z"

],

  "$Function": "odata.UriEncode"

[17:43] Ralf Handl (SAP SE): 2013-04-08T23:00:00.0Z

[17:46] Ralf Handl (SAP SE): With simplified representation this would become

    "2013-04-08T23:00:00.0Z"

],

  "$Function": "odata.UriEncode"

[17:46] Ralf Handl (SAP SE): Less than:

  "$Lt": [

      "$Path": "Price"

},

      "$Int": 20

},

[17:57] Ralf Handl (SAP SE): An alternative representation that is more consistent with CSDL JSON itself is to use a member $Type next to $EnumMember as it is done in the $Cast and $IsOf expressions:

"@com.odata.v4.technical.scenario.TermEnum": {

  "$Type": "Namespace1_Alias.ENString",

  "$EnumMember": "String1,String3"

[17:57] Ralf Handl (SAP SE): Instead of

"@com.odata.v4.technical.scenario.TermEnum": {

  "$EnumMember@odata.type": "#Namespace1_Alias.ENString",

  "$EnumMember": "String1,String3"

[18:00] Ralf Handl (SAP SE): Less than:

  "$Lt": [

      "$Path": "Size"

},

      "$EnumMember": "XXL"

},

[18:08] Ralf Handl (SAP SE): Mike: wrapper objects for constant values only needed where we use arrays

[18:10] Ralf Handl (SAP SE): Wrapper objects as discussed for JSON Format:

   value: "XXL",

   "@type": "#my.EnumType"

[18:12] Ralf Handl (SAP SE): Hubert: park this issue for the F2F

[18:14] Michael Pizzo: {

  "$Lt": [

      "Edm.PropertyPath": "Size",

      "Namespace1_Alias.SizeEnum": "XXL"

},

[18:14] Michael Pizzo: trying to do something like:

  "$Lt": {

      "Edm.PropertyPath": "Size",

      "Namespace1_Alias.SizeEnum": "XXL"

},

[18:14] Michael Pizzo: except properties aren't ordered. So I made them an array, but then they have to be an array of objects...

[18:15] Michael Pizzo: {

  "$Lt": [

      {"Edm.PropertyPath": "Size"},

      {"Namespace1_Alias.SizeEnum": "XXL"}

},

[18:15] Hubert Heijkers (IBM): {

  "$Lt": [

  "@type": "Edm.PropertyPath",

      "$value": "Size"

},

  "@type": "Namespace1_Alias_SizeEnum",

      "$value": "XXL"

},

[18:16] Ralf Handl (SAP SE): ODATA-1221 is OPEN

[18:18] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1220 - Instance annotations section only refers to the XML CSDL, not JSON CSDL

[18:19] Ralf Handl (SAP SE): Description

In our OData JSON format specification, chapter 20 Instance Annotations, we, only, refer to the XML CSDL. I think what we really are trying to say is that the annotations have to be defined in CSDL, irrespective of the format, and should find a way to express that here.

[18:19] Ralf Handl (SAP SE): Proposal:

Add/correct wording to express that annotations have to be defined in CSDL, irrespective of the format used.

[18:19] Ralf Handl (SAP SE): ODATA-1220 is OPEN

[18:20] Hubert Heijkers (IBM): I move to resolve ODATA-1220 as proposed.

[18:20] Stefan Hagen: I second

[18:20] Ralf Handl (SAP SE): ODATA-1220 is RESOLVED as proposed

[18:20] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1219

[18:20] Ralf Handl (SAP SE): Be more explicit about the purpose of $DefaultValue in a Term definition

[18:20] Ralf Handl (SAP SE): Description

It appears to be unclear what the purpose is of having a $DefaultValue for a term definition in our JSON CSDL as, as stated in the specification as is, in our JSON CSDL a value MUST always be specified anyway. And while a $DefaultValue might be obvious for some terms, most notably boolean typed terms (read: tags) where the values is typically true, and there maybe a value for some enum and numerically based terms, this is less so the case for any of the other types.

The reference to it being for documentation purposes raised different questions.

On the other hand, if a term is of a structured type, default values of the individual structural properties are indeed implied in absence of the property, which is not the case for terms not being applied to any model element it could have been applied to, which further would speak to not having a $DefaultValue in terms potentially causing confusion.

Our XML CSDL however didn't require the value to be there, merely 'tagging' a model element with the annotation term would suffice, implying the DefaultValue specified in the XML CSDL. Therefore, arguably, the only remaining 'function' of this $DefaultValue is to allow for full fidelity round-tripping between our XML and JSON versions of the CSDL.

[18:21] Ralf Handl (SAP SE): Proposal:

At a minimum I think we should be extremely clear in our JSON CSDL specification that this full fidelity between the two formats of our CSDL is the sole purpose of this $DefaultValue to exists and to not confuse it with $DefaultValue of properties that, when omitted, are presumed to be applied.

[18:24] Ralf Handl (SAP SE): ODATA-1219 is OPEN

[18:26] Stefan Hagen: I move to resolve ODATA-1219 as proposed including the updated wording

[18:26] Michael Pizzo: I second

[18:26] Ralf Handl (SAP SE): ODATA-1219 is RESOLVED as proposed

[18:27] Ralf Handl (SAP SE): c.V4.01: NEW or OPEN

i.ODATA-1189 Conformance: Nullable for collections

[18:27] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1189

[18:27] Ralf Handl (SAP SE): Description

Chapter 17 Conformance states:

12.  SHOULD specify the Nullable facet for collections

This makes sense in CSDL XML where Nullable defaults to true and collections weren't considered initially.

In CSDL JSON $Nullable defaults to false for single- and collection-valued properties, so no need to state

[18:27] Ralf Handl (SAP SE): Remove conformance statements in CSDL JSON, keep it only in CSDL XML

12.  SHOULD specify the Nullable facet for collections

14.  MUST specify the Nullable facet for collections

[18:28] Ralf Handl (SAP SE): ODATA-1189 is OPEN

[18:28] Michael Pizzo: I move we resolved ODATA-1189 as proposed

[18:28] Hubert Heijkers (IBM): I second

[18:29] Ralf Handl (SAP SE): ODATA-1189 is RESOLVED as proposed

[18:29] Ralf Handl (SAP SE): ii.ODATA-1190 Add matchesPattern as a $filter function

[18:29] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1190

[18:29] Ralf Handl (SAP SE): Proposal:

Add matchesPattern as a $filter function:

Edm.Boolean matchesPattern(Edm.String,Edm.String)

The matchesPattern function returns true if the second parameter string value evaluates to a [[ECMAScript]|http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/cs01/odata-csdl-xml-v4.01-cs01.html#ECMAScript] (_javascript_) regular _expression_ and the result of the first argument string matches that regular _expression_, using syntax and semantics of [[ECMAScript]|http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/cs01/odata-csdl-xml-v4.01-cs01.html#ECMAScript] regular expressions, otherwise it returns false.

[18:32] Stefan Hagen: https://docs.microsoft.com/en-us/sql/relational-databases/scripting/search-text-with-regular-expressions?view=sql-server-2017

[18:32] Stefan Hagen: Search Text with Regular Expressions

[18:35] Ralf Handl (SAP SE): ODATA-1190 is OPEN

[18:35] Hubert Heijkers (IBM): I move to resolve ODATA-1190 as proposed

[18:35] Stefan Hagen: I second

[18:35] Matt Borges (SAP): I second

[18:35] Ralf Handl (SAP SE): ODATA-1190 is RESOLVED as proposed

[18:35] Ralf Handl (SAP SE): iii.ODATA-1208 Specify the finest possible granularity for Duration

[18:36] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1208

[18:36] Ralf Handl (SAP SE): Description

Edm.Duration allows to expressing via the Precision facet which number of decimal places can be stored/sent.

We have applications which don't even support second granularity for durations and only can store durations in days, hours, or minutes (all three variants exist).

[18:37] Ralf Handl (SAP SE): Proposal:

Two possible solutions:

Extend Precision for Edm.Duration to allow negative values in V4.01 CSDL documents: -1 meaning minute granularity, -2 hour granularity, and -3 day granularity.

Add a Measures term DurationGranularity with allowed values "days", "hours", and "minutes". Absence of the annotation means "seconds with sub-seconds according to Precision".

[18:42] Ralf Handl (SAP SE): Mike: Microsoft can always store at least seconds

[18:42] Ralf Handl (SAP SE): Hubert: can also store at least seconds

[18:43] Ralf Handl (SAP SE): Stefan: IoT experience indicates that it is valuable to have this information

[18:44] Ralf Handl (SAP SE): ODATA-1208 is OPEN

[18:44] Ralf Handl (SAP SE): Mike: use annotation

[18:44] Stefan Hagen: Stefanalso for annotation

[18:44] Ralf Handl (SAP SE): Hubert: either

[18:44] Ralf Handl (SAP SE): Ralf: either

[18:45] Ralf Handl (SAP SE): Matt: annotation

[18:46] Stefan Hagen: I move to resolve ODATA-1208 as proposed picking the annotation i.e. the above second option (updated proposal)

[18:46] Hubert Heijkers (IBM): I second

[18:46] Matt Borges (SAP): I second

[18:47] Ralf Handl (SAP SE): ODATA-1208 is RESOLVED with the annotation proposal

[18:47] Ralf Handl (SAP SE): iv.ODATA-1203 Allow numeric indexes in Path constructs within annotations

[18:47] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1203

[18:47] 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.

[18:52] Ralf Handl (SAP SE): Mike: restrict to collections of non-entities

[18:54] Ralf Handl (SAP SE): Mike: we did this in Protocol: indexing only for collection of primitive or complex

[18:55] Ralf Handl (SAP SE): Updated proposal: Path expressions allow index segments after path segments that identify an ordered collection of primitive or complex types.

[18:56] Hubert Heijkers (IBM): I move to resolve ODATA-1203 as proposed

[18:56] Matt Borges (SAP): I second

[18:56] Ralf Handl (SAP SE): ODATA-1203 is RESOLVED as proposed

[18:57] Ralf Handl (SAP SE): 6.Next meetings [9:50 am PT]

a.Thursday September 20, 2018 during 8-10 am PDT (17:00-19:00 CEST)

b.Face-to-Face Thursday & Friday September 27 & 28, 2018 during 9-17 am PDT & 9-15 PDT (18:00-02:00 CEST & 18:00-00:00 CEST)

[18:57] Ralf Handl (SAP SE): 7.AOB and wrap up [9:55 am PT]

[18:58] Ralf Handl (SAP SE): Mike: reserve time next week for agenda of F2F

[18:58] Ralf Handl (SAP SE): Meeting is adjourned

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Montag, 10. September 2018 16:27
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-09-10

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday September 13, 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]

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

2. Approve agenda [8:05 am PT]

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

Minutes from Septenber 06, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63900/odata-meeting-228_on-20180906-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]

Upcoming

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

In progress

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

5. Issues [8:20 am PT]

APPLIED

i. …

Vocabularies: NEW or OPEN with concrete proposal

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

V4.01: NEW or OPEN

i. ODATA-1189 Conformance: Nullable for collections

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

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

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

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

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

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

viii. 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)

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

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

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-1171 Consider using matrix parameters for filter segments

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

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

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

xviii. ODATA-1135 Document use of JSON $schema

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

Data Aggregation: NEW or OPEN (deferred to F2F)

i. ODATA-1218 Transformations for recursive hierarchy processing

ii. ODATA-1207 Clarify need for @odata.id in nested response structures (deferred to F2F)

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

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

Vocabularies: deferred to F2F – examples, custom headers and query options, error codes

i. ODATA-1216 Terms for POST/PATCH/PUT with system query options to shape response

ii. ODATA-1214 Annotate constructor actions

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

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

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

vi. ODATA-1176 Capabilities: add new term SelectSupported

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

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

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

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

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

Vocabularies: NEW or OPEN that need more discussion

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

6. Next meetings [9:50 am PT]

Thursday September 20, 2018 during 8-10 am PDT (17:00-19:00 CEST)
Face-to-Face Thursday & Friday September 27 & 28, 2018 during 9-17 am PDT & 9-15 PDT (18:00-02:00 CEST & 18:00-00: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

odata message