RE: Agenda for OData TC meeting on 2018-12-13

[‎13.‎12.‎2018 17:04]

We'll have to use the Skype chat today, SoapHub seems to be down

[‎13.‎12.‎2018 17:06]

Voting Members: 8 of 10 (80%) (used for quorum calculation)

[‎13.‎12.‎2018 17:07]

Achieved quorum: yes

[‎13.‎12.‎2018 17:08]

2. Approve agenda [8:05 am PT]

[‎13.‎12.‎2018 17:09]

Ralf: shortly discuss ODATA-1177 - Add "JSON properties" to OData

[‎13.‎12.‎2018 17:11]

After 5.c Data Aggregation

[‎13.‎12.‎2018 17:11]

Agenda is approved with this change

[‎13.‎12.‎2018 17:11]

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

Minutes from December 06, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64392/odata-meeting-239_on-20181206-minutes.html

[‎13.‎12.‎2018 17:12]

Minutes are approved

[‎13.‎12.‎2018 17:12]

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

[‎13.‎12.‎2018 17:12]

i. #0037 Concept for Google Protocol Buffers as a data format – Hubert Heijkers – 2019-03-28

1. In progress

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

[‎13.‎12.‎2018 17:13]

Feedback on preferences

[‎13.‎12.‎2018 17:13]

My feedback is similar to the discussions that have occurred around the message headers your'e registering; the names you've chosen are very general, and the protocol you're defining is very specific. Why are these being renamed?

[‎13.‎12.‎2018 17:14]

No Title

Looking at them I think of general interest and independent of OData are

· callback as an add-on to respond-async can be used with any payload format – respond-async defined in - https://tools.ietf.org/html/rfc7240 - author is James Sneell

· maxpagesize as an add-on to the "next" link relation, see https://www.iana.org/assignments/link-relations/link-relations.xhtml.

· Can be used in Atom with <link rel="next" ... /> as we do it in the OData Atom format

· Can be used with a link header with this relation, see https://tools.ietf.org/html/rfc5988 - author is Mark Nottingham

· omit-values – interesting for other JSON or “name-value pair” formats

· track-changes – can be used with other payload formats that allow representing “diffs”, e.g. JSON PATCH - https://tools.ietf.org/html/rfc6902 - author is Mark Nottingham

The remaining ones are less obvious:

· allow-entityreferences – needs a concept and representation of “references” to be useful

· continue-on-error – needs a “batch” or “bulk” format

· include-annotations – needs annotations

It would be great to discuss this on the mailing list and get feedback from the experts:

· Do they agree to the general usefulness of the first four where we see reuse in combination with existing HTTP features?

· Do they see reuse for the remaining three were we are (or at least I am) not aware of existing concepts other than in OData?

[‎13.‎12.‎2018 17:16]

James Snell, not Sneell

[‎13.‎12.‎2018 17:18]

Mark will reply to the mailing list

[‎13.‎12.‎2018 17:19] Michael Pizzo:

Suggest for last bullet, something along the lines of "Do they see common use cases for the remaining three that may not be as generally applicable?"

[‎13.‎12.‎2018 17:20]

5. Issues [8:20 am PT]

a) APPLIED

[‎13.‎12.‎2018 17:20]

i. https://github.com/oasis-tcs/odata-vocabularies/issues/32 - public comment on Core.EntityExampleValue

1. https://github.com/oasis-tcs/odata-vocabularies/pull/33

[‎13.‎12.‎2018 17:28]

I move to resolve https://github.com/oasis-tcs/odata-vocabularies/issues/32 as proposed in https://github.com/oasis-tcs/odata-vocabularies/pull/33

The action couldn’t be completed. Please try again later.

[‎13.‎12.‎2018 17:28] Michael Pizzo:

I second

[‎13.‎12.‎2018 17:28]

Motion passes

The action couldn’t be completed. Please try again later.

[‎13.‎12.‎2018 17:28]

i. ODATA-1255 Correct usage of $count

1. https://github.com/oasis-tcs/odata-abnf/pull/12

The action couldn’t be completed. Please try again later.

[‎13.‎12.‎2018 17:29]

Discussion was about $apply=groupby((Name),aggregate(Sales($count as SalesCount),Sales(Amount with sum as Total)))

The action couldn’t be completed. Please try again later.

[‎13.‎12.‎2018 17:32] Hubert Heijkers:

I move to merge PR https://github.com/oasis-tcs/odata-abnf/pull/12 as proposed

[‎13.‎12.‎2018 17:32] Michael Pizzo:

I second

[‎13.‎12.‎2018 17:33]

Motion passes

[‎13.‎12.‎2018 17:33]

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

1. https://github.com/oasis-tcs/odata-csdl-schemas/pull/6

2. https://github.com/oasis-tcs/odata-vocabularies/pull/34

[‎13.‎12.‎2018 17:41]

Hubert likes the proposal

[‎13.‎12.‎2018 17:42]

Mike has concerns about allowing both notations

[‎13.‎12.‎2018 17:42] Michael Pizzo:

I am concerned with the client complexity of having an enum value that may appear in two different ways.

I would prefer to say, for example, that enum values are always expanded.

[‎13.‎12.‎2018 17:43]

Hubert's intention for the simplification was to get rid of the wrapper or enum values

[‎13.‎12.‎2018 17:46]

  "$Eq": [
    {
      "$Path": "FirstName"
    },
    "John"
    }
  ]

[‎13.‎12.‎2018 17:50]

{

"$Cast": {

"$Path": "Average"

"$Type": "Edm.Decimal"

}

[‎13.‎12.‎2018 17:50]

"@True.Or.False": {
  "$Eq": [
    {
      "$Cast@type": "#ODATA1221.Color",
      "value": "Taupe"
    },
    {
      "@type": "#ODATA1221.Color",
      "value": "GreyBrown"
    }
  ]
}

[‎13.‎12.‎2018 17:51]

"@True.Or.False": {
  "$Eq": [
    {
      "$Cast": "Taupe",
      "value": "ODATA1221.Color"
    },
    {
      "$Cast": "GreyBrown ",
      "value": "ODATA1221.Color"
    }
  ]
}

[‎13.‎12.‎2018 17:55]

"@True.Or.False": {
  "$Eq": [
    {
      "$Cast": "Taupe",
      "$Type": "ODATA1221.Color"
    },
    {
      "$Cast": "GreyBrown ",
      "$Type": "ODATA1221.Color"
    }
  ]
}

[‎13.‎12.‎2018 17:58] Michael Pizzo:

I would rather not have a cast that is required based on format.

[‎13.‎12.‎2018 18:01]

The "Compact JSON" work-in-progress uses the same {@type:..,value:...} object wrapper

[‎13.‎12.‎2018 18:02]

Add note to issue that this already can be resolved via the $Cast construct

[‎13.‎12.‎2018 18:02]

b. V4.01

i. ODATA-1265 Clarify property paths used in a lambda predicate _expression_

[‎13.‎12.‎2018 18:17] Michael Pizzo:

Current text implies that you can do:

[‎13.‎12.‎2018 18:18] Michael Pizzo:

http://host/service/Oders?$filter=Items/any(d:d/Quantity gt MaxQuantity)

[‎13.‎12.‎2018 18:18] Michael Pizzo:

Where MaxQuantity is a property of the order.

[‎13.‎12.‎2018 18:20] Michael Pizzo:

Which would be the same as: http://host/service/Oders?$filter=Items/any(d:d/Quantity gt $it/MaxQuantity)

But, if the filter was nested within an expand, then the unqualified would be "scoped" to the expanded item, while $it always applies to the root.

[‎13.‎12.‎2018 18:24] Michael Pizzo:

Orders?$expand=Items($filter=AvailableDiscounts/any(d:D/Amount gt ItemAmount)

Where ItemAmount would be defined on an item.

[‎13.‎12.‎2018 18:26]

Gerald to craft a proposal for additional clarifying text and an example

[‎13.‎12.‎2018 18:26]

[‎13.‎12.‎2018 18:26] Michael Pizzo:

::D

[‎13.‎12.‎2018 18:26]

[‎13.‎12.‎2018 18:26] Michael Pizzo:

/:D

[‎13.‎12.‎2018 18:26] Ericson, George:

: d

[‎13.‎12.‎2018 18:27]

ODATA-1265 is OPEN

[‎13.‎12.‎2018 18:30]

c. Data Aggregation:

i. ODATA-1244 Add a function to determine aggregated values within common expressions

[‎13.‎12.‎2018 18:38] Michael Pizzo:

COuld I do: $filter=Products/any(p: p/aggregate(p/Sales with average) gt 10)

[‎13.‎12.‎2018 18:38] Michael Pizzo:

[‎12/‎13/‎2018 9:38 AM]

COuld I do: $filter=Products/any(p: p/aggregate(Amount with average) gt 10)

We saved this conversation. You'll see it soon in the Conversations tab in Skype for Business and in the Conversation History folder in Outlook.

[‎13.‎12.‎2018 19:00]

Gerald has the challenge to write up what we discussed

[‎13.‎12.‎2018 19:00]

6. Next meetings [9:50 am PT]

1. Thursday December 20, 2018 during 8-10 am PST (17:00-19:00 CET)

2. Thursday January 10, 2019 during 8-10 am PST (17:00-19:00 CET) – moderated by Mike Pizzo

3. Thursday January 17, 2019 during 8-10 am PST (17:00-19:00 CET)

[‎13.‎12.‎2018 19:02]

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

[‎13.‎12.‎2018 19:02]

No other business

[‎13.‎12.‎2018 19:02]

Meeting is adjourned

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 12. Dezember 2018 12:45
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-12-13

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday December 13, 2018 during 8-10 am PST (17:00-19:00 CET). 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=46286

2. Approve agenda [8:05 am PT]

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

Minutes from December 06, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64392/odata-meeting-239_on-20181206-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 – 2019-03-28

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. https://github.com/oasis-tcs/odata-vocabularies/issues/32 - public comment on Core.EntityExampleValue

https://github.com/oasis-tcs/odata-vocabularies/pull/33

ii. ODATA-1255 Correct usage of $count

https://github.com/oasis-tcs/odata-abnf/pull/12

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

V4.01

i. ODATA-1265 Clarify property paths used in a lambda predicate _expression_

Data Aggregation:

i. ODATA-1244 Add a function to determine aggregated values within common expressions

V4.01: NEW or OPEN

i. ODATA-1257 Do URLs within a Batch Request need to be URL Encoded?

ii. ODATA-1249 edm.xsd: ActionImport and IncludeInServiceDocument

iii. ODATA-1248 csdl.schema.json: add descriptions to all schema elements

iv. ODATA-1245 Extract _expression_ syntax into own sub-section next to $filter

v. ODATA-1263 Requirement for 204 (No Content) with 11.4.3 "Update an Entity" is not backwards compatible

vi. ODATA-1262 Reconsider name of type Edm.Untyped

vii. ODATA-1261 Allow $pagesize system query option

viii. ODATA-1260 Clarify read-write access via URLs differing from the canonical/read/edit URL

ix. ODATA-1259 Clarify @type (@odata.type) and metadata=full

x. ODATA-1266 Geo literals with three dimensions

xi. ODATA-1250 GeoJSON, SRID, and LineString

xii. ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific

xiii. ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references

xiv. ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

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

xvi. ODATA-1253 Abstract type definition Core.Number as a super-type of all numeric types

xvii. ODATA-1246 Allow BaseType to be a ComplexType

xviii. ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta Response

xix. ODATA-1238 Clarifications for select-list in ContextUrl

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

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

xxii. ODATA-1135 Document use of JSON $schema

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

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

Data Aggregation: NEW or OPEN

i. ODATA-1256 Harmonize usage of custom aggregates with structured aggregatable properties

ii. ODATA-1218 Transformations for recursive hierarchy processing

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

iv. ODATA-945 Correct examples 53 and 54

Vocabularies: NEW or OPEN with concrete proposal

i. ODATA-1176 Capabilities: add new term SelectSupport

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

Vocabularies: NEW or OPEN that need more discussion

i. ODATA-1264 CRUD descriptions on entity sets

ii. ODATA-1214 Annotate constructor actions

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

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

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

vi. ODATA-1060 Improve specification of element response requirements

vii. ODATA-884 Enable enumerating the valid requests and responses for a particular resource.

6. Next meetings [9:50 am PT]

Thursday December 20, 2018 during 8-10 am PST (17:00-19:00 CET)
Thursday January 10, 2019 during 8-10 am PST (17:00-19:00 CET) – moderated by Mike Pizzo
Thursday January 17, 2019 during 8-10 am PST (17:00-19:00 CET)

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