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 2019-09-12 - chat transcript


[‎12.‎09.‎2019 17:01] 

[1] Agenda

              1. Roll call [8:00 am]

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

Voting Members: 1 of 9 (11%) (used for quorum calculation) 

 

[‎12.‎09.‎2019 17:03] 

Voting Members: 3 of 9 (33%) (used for quorum calculation) 

 

[‎12.‎09.‎2019 17:05] 

Voting Members: 4 of 9 (44%) (used for quorum calculation) 

 

[‎12.‎09.‎2019 17:06] 

Voting Members: 5 of 9 (55%) (used for quorum calculation) 

 

[‎12.‎09.‎2019 17:06] 

              2. Approve agenda [8:05 am]

 

[‎12.‎09.‎2019 17:06] 

Agenda is approved

 

[‎12.‎09.‎2019 17:07] 

              3. Approve minutes from previous meeting(s)

                            a. Minutes from July 25, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/65680/Minutes%20of%202019-07-25%20Meeting%20%23266.docx 

 

[‎12.‎09.‎2019 17:07] 

Minutes are approved

 

[‎12.‎09.‎2019 17:07] 

No Title

              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:15 am]

                            a. Upcoming

                                          i.            #0039 Concept for Compact JSON data format – Hubert Heijkers – 2019-10-31

                                          ii.           #0037 Concept for binary data format – Hubert Heijkers – 2020-03-26

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

 

[‎12.‎09.‎2019 17:07] 

i: postponed due to other workload

 

[‎12.‎09.‎2019 17:09] 

iii: no feedback on latest submission, Chet Ensign will register headers and preferences with IANA

 

[‎12.‎09.‎2019 17:10] 

             5. Issues [8:20 am]

                           a. APPLIED

                                          i.            none

 

[‎12.‎09.‎2019 17:10] 

                           b. V4.01: NEW or OPEN

                                          i.            ODATA-1331 Override entity set when extending an entity container (public comment)

 

[‎12.‎09.‎2019 17:11] 

No Title

Description: See https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/odata-discussion/5g3mk2A7yG8/tluOLeO2AgAJ
 
What is the expected behavior when an Entity Container extends another Entity Container and there is an Entity Set with the same name in both? 
The spec says: "All children of the “base” entity container are added to the “extending” entity container." and "An entity set is identified by its name, a simple identifier that MUST be unique within its entity container."
 
Does that mean this case is invalid?
 
IIUC, 4.01 adds covariance, i.e., the ability for Structural Types to redeclare Properties defined in the base Structural Type with a subtype. It would be nice if the same were possible for Entity Containers, i.e., if an Entity Container that extends another Entity Container could redeclare Entity Sets with a subtype

 

[‎12.‎09.‎2019 17:14] 

ODATA-1331 is OPEN

 

[‎12.‎09.‎2019 17:15]  Mike Pizzo: 

Support covariance in extending an entity container. Existing entity sets/singletons can be redefined using types derived from the type defined in the extended entity container.

 

[‎12.‎09.‎2019 17:15]  Ericson, George: 

Move to resolve ODATA-1331 as proposed

 

[‎12.‎09.‎2019 17:16]  Mike Pizzo: 

I second

 

[‎12.‎09.‎2019 17:16] 

ODATA-1331 is RESOLVED with the above proposal

 

[‎12.‎09.‎2019 17:16] 

                                          ii.           ODATA-1330 JSON Batch: explicitly state that continue-on-error=true

 

[‎12.‎09.‎2019 17:17] 

ODATA-1330 is OPEN

 

[‎12.‎09.‎2019 17:19]  Mike Pizzo: 

I move to resolve ODATA-1330 as proposed.

 

[‎12.‎09.‎2019 17:19]  Ericson, George: 

Second

 

[‎12.‎09.‎2019 17:19] 

ODATA-1330 is RESOLVED as proposed

 

[‎12.‎09.‎2019 17:19] 

                                          iii.           ODATA-1328 Simplify query rules by removing $expand select option

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

 

[‎12.‎09.‎2019 17:25] 

Allowing to specify $expand in two places increases the likelihood of specifying contradictory additional options nested within $expand

 

[‎12.‎09.‎2019 17:25] 

ODATA-1328 is OPEN

 

[‎12.‎09.‎2019 17:26]  Mike Pizzo: 

I move to resolve ODATA-1328 as proposed.

 

[‎12.‎09.‎2019 17:26]  Krause, Gerald: 

I second

 

[‎12.‎09.‎2019 17:26] 

ODATA-1328 is RESOLVED as proposed

 

[‎12.‎09.‎2019 17:28]  Mike Pizzo: 

I move to accept the application of ODATA-1328 to the ABNF as captured in https://github.com/oasis-tcs/odata-abnf/pull/20

(and merge the PR)

 

[‎12.‎09.‎2019 17:28]  Krause, Gerald: 

I second

 

[‎12.‎09.‎2019 17:28] 

No objection, motion passes

 

[‎12.‎09.‎2019 17:29] 

                                          iv.          ODATA-1325 Explicitly state server behaviour when a client uses $select/$expand for an update response

 

[‎12.‎09.‎2019 17:30] 

Clients need a guaranteed way to get certain information in the response to PATCH/PUT such as an updated ETag.  Clarify that if the client specifies a $select and/or $expand for the response of a PATCH/PUT request, that the server MUST respond with a a response body including the ETag.

 

[‎12.‎09.‎2019 17:31] 

ODATA-1325 is OPEN

 

[‎12.‎09.‎2019 17:37]  Mike Pizzo: 

Proposal: Clarify that if the client specifies a $select and/or $expand for the response of a PATCH/PUT request, that the server MUST respond with a a response body. If the service uses ETags for optimistic concurrency, the response MUST include ETags.

 

[‎12.‎09.‎2019 17:38]  Ericson, George: 

Move to resolve OData-1325 as proposed.

 

[‎12.‎09.‎2019 17:39]  Mike Pizzo: 

I second

 

[‎12.‎09.‎2019 17:39] 

ODATA-1325 is RESOLVED as proposed

 

[‎12.‎09.‎2019 17:40] 

                            v.           ODATA-1324 Incorrect text about mediaEditLink control information

 

[‎12.‎09.‎2019 17:40] 

n section 4.5.12 in JSON format doc, the text says that the mediaEditLink control information needs to be included if it differs from the id.  It should be if it differs from the conventional URL of the media stream which is the media entity's ID appended with "/$value".

 

[‎12.‎09.‎2019 17:41] 

ODATA-1324 is OPEN

 

[‎12.‎09.‎2019 17:43]  Mike Pizzo: 

Revised proposal: In section 4.5.12 in JSON format doc, the text says that the mediaEditLink control information needs to be included if it differs from the id. It should be if it differs from the conventional URL of the media stream.

 

[‎12.‎09.‎2019 17:45]  Mike Pizzo: 

Reword to say that the mediaEditLink control information needs to be included if it differs from the conventional URL of the media stream.

 

[‎12.‎09.‎2019 17:46]  Ericson, George: 

Move to resolve OData 1324 as proposed.

 

[‎12.‎09.‎2019 17:46]  Mike Pizzo: 

I second

 

[‎12.‎09.‎2019 17:47] 

ODATA-1324 is RESOLVED with the revised proposal

 

[‎12.‎09.‎2019 17:49] 

George: have a Glossary, e.g. as a separate document, or a dedicated section in each document

 

[‎12.‎09.‎2019 17:50] 

Mike to follow up with Chet Ensign if there is an OASIS template/guideline for this

 

[‎12.‎09.‎2019 17:50] 

George to open an issue to track this

 

[‎12.‎09.‎2019 17:51] 

                                          vi.          ODATA-1323 Clarify representation of GEO literals in annotations (XML, JSON)

 

[‎12.‎09.‎2019 17:53] 

Ralf: use GeoJSON for CSDL JSON

 

[‎12.‎09.‎2019 17:57] 

George: defer until we have more information on the use case and consumer of these annotations

 

[‎12.‎09.‎2019 17:57] 

Mike: could use WKT in XML

 

[‎12.‎09.‎2019 17:57] 

Mike: to be consistent we would want to add Geo="..." attribute

 

[‎12.‎09.‎2019 17:58] 

Ralf: cross-check with (discontinued) XML/Atom format

 

[‎12.‎09.‎2019 17:59] 

ODATA-1323 is OPEN

 

[‎12.‎09.‎2019 18:01] 

                           c. Vocabularies: NEW or OPEN with concrete proposal

                                         i.            ODATA-1327 Extend applicability of Core.MediaType and Core.AcceptableMediaTypes to no          n-stream (string/binary) properties and terms

 

[‎12.‎09.‎2019 18:01] 

ODATA-1327 is OPEN

 

[‎12.‎09.‎2019 18:02] 

We have some cases where the value of a String-typed Term may be expected to contain JSON, XML or SQL (i.e. the annotation values have a constrained media type).

It would be helpful if we could change the description of Core.MediaType and Core.AcceptableMediaTypes to state that it is also applicable to regular (non-stream) properties of type Edm.Binary or Edm.String, as well as changing the AppliesTo so those terms can be applicable to Term elements of type Edm.Binary or Edm.String.

 

[‎12.‎09.‎2019 18:03]  Mike Pizzo: 

I move to resolve ODATA-1327 as proposed.

 

[‎12.‎09.‎2019 18:03]  Ericson, George: 

Second

 

[‎12.‎09.‎2019 18:04] 

ODATA-1327 is RESOLVED as proposed

 

[‎12.‎09.‎2019 18:04] 

                                         ii.           ODATA-1326 Enhance syntax of term Validation.OpenPropertyTypeConstraint

 

[‎12.‎09.‎2019 18:04] 

Term Validation.OpenPropertyTypeConstraint is of type Collection(Core.QualifiedTypeName).

This is too restrictive, I'd also be able to specify that a dynamic property of an open type can be collection-valued.

 

[‎12.‎09.‎2019 18:05] 

Also allow strings with Collection(...) as values of this term, where ... is the qualified name of a type is scope.

Note: this "rhymes" with the syntax of the Type attribute of CSDL XML, less so with the syntax of CSDL JSON.

 

[‎12.‎09.‎2019 18:10] 

ODATA-1326 is OPEN

 

[‎12.‎09.‎2019 18:11] 

Mike: add type definition for "type name or collection-type name", use that as type of OpenPropertyTypeConstraint

 

[‎12.‎09.‎2019 18:12] 

Mike: if the type constraint list an entity type, then this applies to/results in dynamic navigation properties

 

[‎12.‎09.‎2019 18:13]  Mike Pizzo: 

General idea is to define a new "TypeSpecification" type definition, used in OpenPropertyTypeConstraint, that is the qualified name of a type or collection of types. Basically, it's the same as what you can specify in the type attribute of a property or navigationproperty.

 

[‎12.‎09.‎2019 18:14] 

             6. Next meetings [9:50 am]

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

                           b.           Thursday September 26, 2019 during 8-10 am PDT (17:00-19:00 CEST)

                           c.           Thursday October 03, 2019 during 8-10 am PDT (17:00-19:00 CEST) – public holiday in Germany

                           d.           Thursday October 10, 2019 during 8-10 am PDT (17:00-19:00 CEST)

 

[‎12.‎09.‎2019 18:17] 

Mike: aim for September 26 to submit new V4.01 documents for public review

 

[‎12.‎09.‎2019 18:17] 

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

 

[‎12.‎09.‎2019 18:18] 

Meeting is adjourned, and thanks for the productive meeting

 

 

 

 

From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of Handl, Ralf
Sent: Mittwoch, 11. September 2019 14:23
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2019-09-12

 

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

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

 

      2. Approve agenda [8:05 am]

 

      3. Approve minutes from previous meeting(s)

           a. Minutes from July 25, 2019 TC meeting: https://www.oasis-open.org/committees/download.php/65680/Minutes%20of%202019-07-25%20Meeting%20%23266.docx

 

      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:15 am]

           a. Upcoming

                 i.    #0039 Concept for Compact JSON data format – Hubert Heijkers – 2019-10-31

                 ii.   #0037 Concept for binary data format – Hubert Heijkers – 2020-03-26

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

 

    5. Issues [8:20 am]

          a. APPLIED

                 i.    none

 

          b. V4.01: NEW or OPEN

                 i.    ODATA-1331 Override entity set when extending an entity container (public comment)

                 ii.   ODATA-1330 JSON Batch: explicitly state that continue-on-error=true

                 iii.  ODATA-1328 Simplify query rules by removing $expand select option

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

                 iv.  ODATA-1325 Explicitly state server behaviour when a client uses $select/$expand for an update response

                 v.   ODATA-1324 Incorrect text about mediaEditLink control information

                 vi.  ODATA-1323 Clarify representation of GEO literals in annotations (XML, JSON)

 

          c. Vocabularies: NEW or OPEN with concrete proposal

                i.    ODATA-1327 Extend applicability of Core.MediaType and Core.AcceptableMediaTypes to no  n-stream (string/binary) properties and terms

                ii.   ODATA-1326 Enhance syntax of term Validation.OpenPropertyTypeConstraint

 

          d. Vocabularies: NEW or OPEN that need more discussion

                i.    ODATA-1300 Capabilities: clarify CountRestrictions and ExpandRestrictions

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

                ii.   ODATA-1275 Describing and querying "JSON properties"

                iii.  ODATA-1214 Annotate constructor actions

                iv.  ODATA-1140 Add details to HttpResponse

                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 Allow describing possible responses to requests for a particular resource (public comment c201510e00019)

 

           e. Data Aggregation: NEW or OPEN

                 i.    ODATA-1332 Support augmenting entities with aggregated values from related entities

                 ii.   ODATA-1218 Transformations for recursive hierarchy processing

                 iii.  ODATA-945 Correct examples 53 and 54

 

     6. Next meetings [9:50 am]

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

          b.  Thursday September 26, 2019 during 8-10 am PDT (17:00-19:00 CEST)

          c.   Thursday October 03, 2019 during 8-10 am PDT (17:00-19:00 CEST) – public holiday in Germany

          d.  Thursday October 10, 2019 during 8-10 am PDT (17:00-19:00 CEST)

 

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

 

[2] References

 

[3] Timeline

 



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