RE: Agenda for OData TC Face-to-Face meeting part 1 on 2018-09-27 and pa

[8:55] Room information was updated by: Ralf Handl (SAP SE)

Here [1] is a draft agenda for the OData TC (Technical Committee) Face-to-Face meeting Part 1 scheduled on Thursday September 26, 2018 during 9 am to 5 pm PDT (18:00 to 02:00+1 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.Thursday Morning [9:00 am PT]

a.Roll call [9:00 am PT]

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

b.Approve agenda [9:05 am PT]

c.Approve minutes from previous meeting(s) [9:10 am PT]

i.Minutes from September 20, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63957/odata-meeting-230_on-20180920-minutes.html

d.V4.01: NEW or OPEN [9:15 am PT]

i.ODATA-868 Describe HTTP encoding for streamed requests and responses

ii.ODATA-1231 Remove $Kind for entity container children

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

iv.ODATA-1230 $filter(...) and $search(...) segments in paths and expressions

v.ODATA-1228 Support non-batch mechanism for long URLs

vi.ODATA-1224 Make [OData-]EntityId header optional if the same as Location header

vii.ODATA-1223 Add OData- prefix back to Entity-Id and Isolation headers

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

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

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

xi.ODATA-1183 Allow Singletons to be null

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

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

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

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

xvi.ODATA-1114 If-Then-Else in $batch requests

xvii.ODATA-1135 Document use of JSON $schema

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

2.Thursday Afternoon [1:30 pm PT]

a.Vocabularies: with proposal

i.ODATA-1229 Introduce LocalTime annotation to apply to string datatype

ii.ODATA-1227 Improve description of filter _expression_ restrictions

iii.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

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

v.ODATA-1176 Capabilities: add new term SelectSupported

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

b.Wrap up for remote participants [2:55 pm PT]

c.Discussion on Data Aggregation (on-site to prepare issues for Friday Morning) [3:30 pm PT]

i.ODATA-947 Transformation for computing ratios with aggregated values

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

3.Friday Morning [9:00 am PT]

a.Approve agenda [9:05 am PT]

b.Data Aggregation: NEW or OPEN (deferred to F2F) [9:10 am PT]

i.ODATA-945 Correct examples 53 and 54

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

iii.ODATA-947 Transformation for computing ratios with aggregated values

c.V4.01: NEW or OPEN  [11:00 am PT]

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

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

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

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

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

4.Friday Afternoon [1:30 pm PT]

a.OpenAPI-related vocabulary issues

i.ODATA-1214 Annotate constructor actions

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

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-1140 ODATA-884 / Add details to HTTPResponseCode term

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

b.Miscellaneous

5.Next meetings [2:50 pm PT]

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

b.Thursday October 11, 2018 during 8-10 am PDT (17:00-19:00 CEST)

6.AOB and wrap up [2:55 pm 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

[9:01] Ralf Handl (SAP SE): Voting Members: 8 of 10 (80%) (used for quorum calculation)

[9:01] Ralf Handl (SAP SE): Quorum achieved: yes

[9:02] Ralf Handl (SAP SE): Voting Members: 9 of 10 (90%) (used for quorum calculation)

[9:02] Ralf Handl (SAP SE): Almost full attendance!

[9:02] Ted Jones (Red Hat): I am not hearing anything.

[9:04] Ralf Handl (SAP SE): Can you hear us now?

[9:04] Ted Jones (Red Hat): No

[9:04] Ralf Handl (SAP SE): @Matt: can you hear us?

[9:05] Michael Pizzo: matt can you hear anything on the call?

[9:05] Matt Borges (SAP): I can hear you guys

[9:05] Matt Borges (SAP): You can't hear me though

[9:06] Ted Jones (Red Hat): Ah.. must be on my end then

[9:06] Ralf Handl (SAP SE): Ok, we can hear Matt

[9:07] Ted Jones (Red Hat): Can you hear me?

[9:07] Hubert Heijkers (IBM): We can not

[9:07] Ted Jones (Red Hat): Let me try rejoining...

[9:13] Ralf Handl (SAP SE): Hi Ted, we can try calling you: which number?

[9:14] Ted Jones (Red Hat): 3142259801

[9:15] Ralf Handl (SAP SE): Did we reach you?

[9:16] Ralf Handl (SAP SE): Mike is trying now

[9:17] Ted Jones (Red Hat): Nothing yet

[9:18] Stefan Hagen: @Ralf: I will not join voice, but in case I can understand from chat, when the to be minuted part of the meeting is "in", I can provide the draft  for first day before tomorrow (your timezone there in Seattle)

[9:19] Ralf Handl (SAP SE): @Stefan: thanks!

[9:20] Ralf Handl (SAP SE): Finally we can hear Ted and vice versa!

[9:20] Ralf Handl (SAP SE): and:

[9:20] Ralf Handl (SAP SE): Voting Members: 10 of 10 (100%) (used for quorum calculation)

[9:20] Ralf Handl (SAP SE): Full attendance!

[9:20] Ralf Handl (SAP SE): b.Approve agenda [9:05 am PT]

[9:22] Ralf Handl (SAP SE): No changes, the agenda is approved

[9:22] Ralf Handl (SAP SE): c.Approve minutes from previous meeting(s) [9:10 am PT]

i.Minutes from September 20, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63957/odata-meeting-230_on-20180920-minutes.html

[9:22] Ralf Handl (SAP SE): No remarks, minutes are approved

[9:22] Ralf Handl (SAP SE): i.Minutes from September 20, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63957/odata-meeting-230_on-20180920-minutes.html

d.V4.01: NEW or OPEN [9:15 am PT]

i.ODATA-868 Describe HTTP encoding for streamed requests and responses

[9:22] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-868

[9:24] Hubert Heijkers (IBM): I move to resolve ODATA-868 as proposed

[9:24] George Ericson (Dell): Second

[9:24] Mark Biamonte (Progress): I second

[9:25] Ralf Handl (SAP SE): ODATA-868 is RESOLVED as proposed

[9:25] Ralf Handl (SAP SE): ii.ODATA-1231 Remove $Kind for entity container children

[9:25] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1231

[9:39] Ralf Handl (SAP SE): ODATA-1231 is OPEN

[9:40] Michael Pizzo: I move to resolve ODATA-1231 as proposed.

[9:40] Hubert Heijkers (IBM): I second

[9:41] Ralf Handl (SAP SE): ODATA-1231 is RESOLVED as proposed

[9:41] Ralf Handl (SAP SE): Side-discussion on chat tool

[9:41] Ralf Handl (SAP SE): George proposes to use Skype chat feature in the future

[9:42] Ralf Handl (SAP SE): @Stefan: would that work for you, too?

[9:42] Michael Pizzo: George: does this bring us closer or further from having entity sets and singletons be nav props on "entity container" (entity container as a singleton)

[9:43] Michael Pizzo: using $Type and $Collection is more consistent with nav props.  Nav props also currently use $NavigationProperty. We could get rid of that if we were able to differentiate a property as being property or nav prop based on the type (entity or primitive/complex).

[9:44] Michael Pizzo: Current model is more explicit; what is part of the object and what is related.

[9:44] Ralf Handl (SAP SE): iii.ODATA-1221 Apply, as much as possible, our JSON Format to our annotations as well

[9:44] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1221

[9:47] Ralf Handl (SAP SE): Proposal:

Use same representation for constant expressions as for primitive values in JSON format, i.e. no object wrapper such as

"@some.binary.term":{"$Binary":"..." }

Instead use the plain value:

"@some.binary.term":"..."

This puts some burden on clients to "know" or look up the term definition to determine the actual type of a JSON string value, but that has to be done for JSON data responses anyway.

Call out that this may require out-of-band knowledge for terms of type Collection(Edm.PrimitiveType).

Same argument applies to model element path expressions: here the client knows from the term definition that the value is a model element path or one of its concreter sub-types, so the value can simply be a string containing the path without object wrapper:

"NonExpandableProperties":["Customer","Country"]

Instance path expressions still need the object wrapper to distinguish them from actual string values:

"@Core.Description":{"$Path","CompanyName"}

[9:49] Ralf Handl (SAP SE): Hubert: most visible PRO is that representation of "record expressions" with constant property values in CSDL JSON is then identical to representation of structured type instances in JSON Format

[10:08] Ralf Handl (SAP SE): Mike likes aligning CDSL JSON and JSON Format

[10:23] Ralf Handl (SAP SE): Ralf is concerned about the additional effort for clients to extract the same information from metadata: after this alignment clients need to read/know the term definitions. This affects startup time of UI applications and is critical

[10:23] Michael Pizzo: I move we resolve ODATA-1221 as proposed.

[10:24] Mark Biamonte (Progress): I second

[10:24] Ralf Handl (SAP SE): ODATA-1221 is RESOLVED as proposed

[10:28] Ralf Handl (SAP SE): This affects the resolution of ODATA-1170

[10:28] Ralf Handl (SAP SE): Hubert moves to reopen ODATA-1170

[10:29] Ralf Handl (SAP SE): Gerald seconds

[10:29] Ralf Handl (SAP SE): ODATA-1170 is OPEN again

[10:30] Ralf Handl (SAP SE): Amended proposal is to use the same mechanism as in JSON Format for data: annotate the enum "property" with @odata.type:

"@com.odata.v4.technical.scenario.TermEnum@odata.type": "#Namespace1_Alias.ENString",

"@com.odata.v4.technical.scenario.TermEnum": "String1,String3"

[10:30] Ralf Handl (SAP SE): Hubert: servers are allowed to do this

[10:30] Ralf Handl (SAP SE): Ralf: do we need a mechanism for clients to request this?

[10:32] Ralf Handl (SAP SE): George: servers MAY use a preference

[10:32] Ralf Handl (SAP SE): Prefer:include-annotations=odata.type

[10:33] Ralf Handl (SAP SE): Mike: odata.type is format-specific control information, it is not an annotation

[10:34] Ralf Handl (SAP SE): Ralf: could use format parameter odata.metadata=full as in JSON Format

[10:48] Ralf Handl (SAP SE): Hubert: specify now that this format parameter is allowed.

[10:49] Ralf Handl (SAP SE): This currently only means @odata.type for constant annotation values

[10:49] Ralf Handl (SAP SE): For none: never

[10:50] Ralf Handl (SAP SE): For minimal: only for terms/properties of type Edm.PrimitiveType

[10:51] Ralf Handl (SAP SE): --> only if value is not Boolean, String, or Double

[10:51] Ralf Handl (SAP SE): For full: for all primitive values that are not Boolean, String, or Double

[10:54] Ralf Handl (SAP SE): Side note: we need @odata.type also for Record expressions if there are derived types and the record is not of the declared type. This is currently missing

[11:09] Hubert Heijkers (IBM): I move to resolve ODATA-1170 as per the amended proposal

[11:09] Michael Pizzo: I second

[11:09] Ralf Handl (SAP SE): ODATA-1170 is RESOLVED with the amended proposal

[11:10] Ralf Handl (SAP SE): Ten minutes break, until 11:20

[11:21] Ralf Handl (SAP SE): We are back

[11:22] Ralf Handl (SAP SE): iv.ODATA-1230 $filter(...) and $search(...) segments in paths and expressions

[11:22] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1230

[11:23] Ralf Handl (SAP SE): Proposal:

Add /$filter(...) segment that can be used in commonExpr after a collection-valued navigation property

Change syntax of /$filter path segment to also use parentheses instead of an = sign

Prefer Nav/$filter(...)/$count to Nav/$count($filter=...), same for $search

Support _expression_ or parameter within parens.

[11:32] Ralf Handl (SAP SE): This came up as a better way for data aggregation than the current expand() transformation

[11:38] Ralf Handl (SAP SE): replace /expand(bla,<filter>)/<do something> with compute(bla/$filter(<filter>) as f_bla)/<do something with f_bla>

[11:39] Ralf Handl (SAP SE): Mike: /$count($filter=...) is easier to implement than a generic /$filter(...) segment that can then be composed with /$count

[11:40] Ralf Handl (SAP SE): Mike: existing syntax was inspired by $expand=NavProp($filter=...)

[11:41] Ralf Handl (SAP SE): ODATA-1230 is OPEN

[11:45] Ralf Handl (SAP SE): Gerald to open an issue for removing expand() transformation

[11:47] Hubert Heijkers (IBM): I move to resolve ODATA-1230 as proposed

[11:47] Michael Pizzo: I second

[11:48] Ralf Handl (SAP SE): ODATA-1230 is RESOLVED as proposed

[11:48] Ralf Handl (SAP SE): v.ODATA-1228 Support non-batch mechanism for long URLs

[11:48] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1228

[11:49] Ralf Handl (SAP SE): Proposal:

Define a /$query segment that can be appended to a resource. Clients make POST requests to this endpoint, with no query options specified, and a content-type of text/plain. The body of the request is a string following the syntax rules of the query portion of the URL, using the same percent-encoding rules.

Open a new issue to track defining an application/json representation of the payload that could include structured representations of things like $filter, $expand, $select, etc.

[11:52] Ralf Handl (SAP SE): Mike: is by definition a GET request

[11:55] Ralf Handl (SAP SE): Use cases: overlong $filter, overlong $select, overlong list of function parameters

[11:59] Ralf Handl (SAP SE): Could later extend this to other verbs, e.g. by using the X-HTTP-Method header to specify a verb other than GET.

[12:07] Ramesh Reddy(Red Hat): https://stackoverflow.com/questions/4526273/what-does-enctype-multipart-form-data-mean/28380690#28380690

[12:12] Ralf Handl (SAP SE): We use content-type text/plain instead of application/x-www-form-urlencoded because we do not want to pass multiple "form" parameters and only want to transport the plain-text query part.

[12:18] Michael Pizzo: Note: application/x-www-form-urlencoded claims to be a desirable format for query strings, but it requires encoding spaces as "+", which we do not want to do.

[12:23] Ralf Handl (SAP SE): We expect only one line of text containing the percent-encoded query part, optionally followed by whitespace or CRLF

[12:25] Ralf Handl (SAP SE): only optionally CRLF as trailing whitespace is already covered by the ABNF of our query options

[12:25] Ralf Handl (SAP SE): ODATA-1228 is OPEN

[12:25] Michael Pizzo: I move we resolve ODATA-1228 as proposed

[12:25] Matt Borges (SAP): I second

[12:25] Ralf Handl (SAP SE): ODATA-1228 is RESOLVED as proposed

[12:26] Ralf Handl (SAP SE): vi.ODATA-1224 Make [OData-]EntityId header optional if the same as Location header

[12:26] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1224

[12:26] Ralf Handl (SAP SE): Proposal:

Make the [OData-]EntityId header optional if it has the same value then the Location header.

[12:27] Ralf Handl (SAP SE): ODATA-1224 is OPEN

[12:34] Michael Pizzo: We could have done this in 4.0, with some impact on the client (they would have to look at the entity-id and, if missing, the location header).  At this point, a service would either have to always return it anyway (in order to support 4.0) or add logic to omit only for 4.01. From a client perspective, it is one more thing that a client would have to be aware of moving from 4.0 to 4.01, which (at this point) is of dubious value.

[12:35] Hubert Heijkers (IBM): I move to close ODATA-1224 without action.

[12:35] Michael Pizzo: I second

[12:36] Ralf Handl (SAP SE): ODATA-1224 is CLOSED without action

[12:39] Ralf Handl (SAP SE): Lunch break until 1:30 pm PDT

[13:34] Ralf Handl (SAP SE): We are almost back

[13:42] Ralf Handl (SAP SE): Next up: https://issues.oasis-open.org/browse/ODATA-1232

[13:42] Ralf Handl (SAP SE): Support Union types

[13:42] Ralf Handl (SAP SE): Proposal:

Define an annotation that restricts the set of derived types for a given property/navprop/instance/parameter. Note that types further derived from the specified types are allowed.

<Term Name="RestrictedTypes" Type="Collection(Edm.String)" AppliesTo="EntitySet Singleton Property NavigationProperty Function Action Parameter">

  <Annotation Term="Description" String="The type of the annotated element is restricted to be one of the specified derived types (or their descendents)"/>

</Term>

[13:43] Ralf Handl (SAP SE): Ralf: seems to have the same purpose as

      <Term Name="DerivedTypeConstraint" Type="Collection(Core.QualifiedTypeName)" AppliesTo="Property TypeDefinition">

        <Annotation Term="Core.Description" String="Values are restricted to types derived from the declared type and listed in this collection" />

        <Annotation Term="Core.LongDescription"

          String="Types listed in this collection that are not derived form the declared type of the annotated model element are ignored" />

      </Term>

[13:44] Ralf Handl (SAP SE): Need to extend AppliesTo list

[13:45] Ralf Handl (SAP SE): ODATA-1232 is OPEN

[13:46] Ralf Handl (SAP SE): Hubert: change proposal to update the existing term Validation.DerivedTypeConstraint

[13:47] Ralf Handl (SAP SE): Extend AppliesTo list

[13:47] Ralf Handl (SAP SE): Explicitly state that types derived from the "allowed" types are also fine

[13:50] Michael Pizzo: Updated proposal:

DerivedTypeConstraint already exists, just nee to extend its use and clarify:

Proposal:

1) Add "EntitySet, Singleton, NavigationProperty, Function, Action, and Parameter to AppliesTo.

2) Clarify in the description that types derived from allowed types are also allowed

[13:51] Hubert Heijkers (IBM): I move to resolve ODATA-1232 as proposed.

[13:51] Michael Pizzo: I second

[13:54] Ralf Handl (SAP SE): ODATA-1232 is RESOLVED as proposed

[13:55] Ralf Handl (SAP SE): vii.ODATA-1223 Add OData- prefix back to Entity-Id and Isolation headers

[13:55] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1223

[13:56] Ralf Handl (SAP SE): ODATA-1223 is OPEN

[13:57] Ralf Handl (SAP SE): Mike: do it for entity-id.

[13:57] Ralf Handl (SAP SE): Mike: don't do it for Isolation, instead come up with a list of more possible values

[13:58] Ralf Handl (SAP SE): Hubert: would that be a generic header or something rather specific to services backed by a database?

[13:59] Matt Borges (SAP): https://en.wikipedia.org/wiki/Isolation_(database_systems)

[14:00] Matt Borges (SAP): https://en.wikipedia.org/wiki/Snapshot_isolation

[14:07] Michael Pizzo: So, for Isolation, we would define: Serializable, RepeatableRead, ReadCommitted, ReadUncommitted, and Snapshot.

[14:10] Ralf Handl (SAP SE): Mike to create separate issue for Isolation

[14:10] Ralf Handl (SAP SE): Limit ODATA-1223 to just Entity-Id

[14:11] Mark Biamonte (Progress): I move to resolve OData-1223 as proposed

[14:11] Hubert Heijkers (IBM): I second

[14:12] Ralf Handl (SAP SE): ODATA-1223 is RESOLVED with the amended proposal

[14:15] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1233

[14:15] Ralf Handl (SAP SE): Add (but don't support) ANSI/ISO isolation levels to registered Isolation header

[14:15] Ralf Handl (SAP SE): ODATA-1233 is OPEN

[14:16] Michael Pizzo: I move we resolve ODATA-1233 as proposed.

[14:22] Mark Biamonte (Progress): I second

[14:22] Ralf Handl (SAP SE): ODATA-1233 is RESOLVED as proposed

[14:23] Ralf Handl (SAP SE): viii.ODATA-1188 Allow using instance annotations in $select and $expand

[14:23] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1188

[14:23] Ralf Handl (SAP SE): Proposal:

Allow using instance annotations of type (collection of) primitive or complex in $select and instance annotations of type (collection of) entity in $expand.

Example

GET Stuff?$select=@Core.Messages($top=5)

Services can signal this capability to clients with the tagging term Capabilities.AnnotationValuesInQuerySupported.

<Term Name="AnnotationValuesInQuerySupported" Type="Core.Tag" DefaultValue="True"

      AppliesTo="EntityContainer">

    <Annotation Term="Core.Description"

                String="Supports annotation values within system query options" />

</Term>

[14:25] Ralf Handl (SAP SE): ODATA-1188 is OPEN

[14:25] Ralf Handl (SAP SE): Point out that "annotations" does not include control information

[14:46] Hubert Heijkers (IBM): I move to resolve ODATA-1188 as proposed

[14:46] Mark Biamonte (Progress): I second

[14:46] Ralf Handl (SAP SE): ODATA-1188 is RESOLVED as proposed

[14:47] Ralf Handl (SAP SE): ix.ODATA-1180 Cast between enumeration types and integer types

[14:47] Ralf Handl (SAP SE): https://issues.oasis-open.org/projects/ODATA/issues/ODATA-1229?filter=allopenissues

[14:48] Ralf Handl (SAP SE): Wrong URL, use ix.ODATA-1180 Cast between enumeration types and integer types

[14:49] Ralf Handl (SAP SE): Proposal:

Casting between enumeration types and integer types (of sufficient width) is possible based on the numeric value.

This cast MUST be explicit, using the cast() function in URLs or the cast _expression_ in CSDL.

Call this out in URL Conventions, section 5.1.1.10.1 cast.

[14:49] Michael Pizzo: George and Mike aren't fond of this, and would never want anyone to do it, but won't block if others have scenarios.

[14:50] Michael Pizzo: Also, support needs to be optional.

[14:52] Michael Pizzo: Preferred wording: Services MAY support casting enumeration members to the underlying string values using the explicit cast function.

[14:53] Michael Pizzo: oops; typo. Preferred wording: Services MAY support casting enumeration members to the underlying *numeric* values using the explicit cast function.

[14:54] Ralf Handl (SAP SE): I move to resolve ODATA-1180 with the amended proposal

[14:54] Ramesh Reddy(Red Hat): I second

[14:54] Ralf Handl (SAP SE): ODATA-1180 is RESOLVED as proposed

[14:55] Ralf Handl (SAP SE): x.ODATA-1171 Consider using matrix parameters for filter segments

[14:55] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1171

[14:57] Michael Pizzo: There doesn't seem to be much support for matrix parameters in the industry.  The syntax is not significantly different that the original proposed syntax.

[14:58] Michael Pizzo: I move to close ODATA-1171 with no action.

[14:58] Ralf Handl (SAP SE): I second

[14:59] Ralf Handl (SAP SE): ODATA-1171 is CLOSED without action

[15:01] Ralf Handl (SAP SE): xi.ODATA-1183 Allow Singletons to be null

[15:01] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1183

[15:18] Michael Pizzo: Question: what should a service return in a 4.0 client for a null singleton?

[15:19] Michael Pizzo: Options: 404, 501, or an object that contains only a contextUrl

[15:24] Hubert Heijkers (IBM): I move to resolve ODATA-1183 as per the amended proposal

[15:25] Mark Biamonte (Progress): I second

[15:25] Ralf Handl (SAP SE): ODATA-1183 is RESOLVED as proposed

[15:26] Ralf Handl (SAP SE): Thanks!

[15:26] Ralf Handl (SAP SE): We'll continue tomorrow

[15:27] Ralf Handl (SAP SE): At 9:00 PDT

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Donnerstag, 27. September 2018 08:35
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] RE: Agenda for OData TC Face-to-Face meeting part 1 on 2018-09-26 and part 2 on 2018-09-27

Reordered issues

Added agenda for Friday

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 26. September 2018 21:46
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC Face-to-Face meeting part 1 on 2018-09-26

Here [1] is a draft agenda for the OData TC (Technical Committee) Face-to-Face meeting Part 1 scheduled on Thursday September 27, 2018 during 9 am to 5 pm PDT (18:00 to 02:00+1 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. Thursday Morning [9:00 am PT]

Roll call [9:00 am PT]

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

Approve agenda [9:05 am PT]

Approve minutes from previous meeting(s) [9:10 am PT]

i. Minutes from September 20, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/63957/odata-meeting-230_on-20180920-minutes.html

V4.01: NEW or OPEN [9:15 am PT]

i. ODATA-868 Describe HTTP encoding for streamed requests and responses

ii. ODATA-1231 Remove $Kind for entity container children

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

iv. ODATA-1230 $filter(...) and $search(...) segments in paths and expressions

v. ODATA-1228 Support non-batch mechanism for long URLs

vi. ODATA-1224 Make [OData-]EntityId header optional if the same as Location header

vii. ODATA-1223 Add OData- prefix back to Entity-Id and Isolation headers

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

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

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

xi. ODATA-1183 Allow Singletons to be null

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

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

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

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

xvi. ODATA-1114 If-Then-Else in $batch requests

xvii. ODATA-1135 Document use of JSON $schema

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

2. Thursday Afternoon [1:30 pm PT]

Vocabularies: with proposal

i. ODATA-1229 Introduce LocalTime annotation to apply to string datatype

ii. ODATA-1227 Improve description of filter _expression_ restrictions

iii. ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

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

v. ODATA-1176 Capabilities: add new term SelectSupported

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

Wrap up for remote participants [2:55 pm PT]

Discussion on Data Aggregation (on-site to prepare issues for Friday Morning) [3:30 pm PT]

i. ODATA-947 Transformation for computing ratios with aggregated values

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

3. Friday Morning [9:00 am PT]

Approve agenda [9:05 am PT]

Data Aggregation: NEW or OPEN (deferred to F2F) [9:10 am PT]

i. ODATA-945 Correct examples 53 and 54

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

iii. ODATA-947 Transformation for computing ratios with aggregated values

V4.01: NEW or OPEN [11:00 am PT]

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

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

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

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

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

4. Friday Afternoon [1:30 pm PT]

OpenAPI-related vocabulary issues

i. ODATA-1214 Annotate constructor actions

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

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-1140 ODATA-884 / Add details to HTTPResponseCode term

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

Miscellaneous

5. Next meetings [2:50 pm PT]

Thursday October 04, 2018 during 8-10 am PDT (17:00-19:00 CEST)
Thursday October 11, 2018 during 8-10 am PDT (17:00-19:00 CEST)

6. AOB and wrap up [2:55 pm 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