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-10-18 - chat transcript


[17:01] 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 October 18, 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=46278 
 
2.Approve agenda [8:05 am PT]
 
3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from Octobrer 11, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64065/odata-meeting-233_on-20181011-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-12-06
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.ODATA-1227 Improve description of filter _expression_ restrictions
1.https://github.com/oasis-tcs/odata-vocabularies/commit/88f6efe8f91b66b147a2fb168f4f560b2c5684ad 
ii.ODATA-1222 Validation: add terms MinItems and MaxItems
1.https://github.com/oasis-tcs/odata-vocabularies/pull/21 
 
b.Pull Requests for partially applied issues
i.ODATA-1241 Support common expressions as values in URL-JSON 
1.https://github.com/oasis-tcs/odata-abnf/pull/5 
ii.ODATA-1230 /$filter() segments in paths and expressions
1.https://github.com/oasis-tcs/odata-abnf/pull/6 
iii.ODATA-1229 Introduce LocalDateTime TypeDef to apply to string datatype
1.https://github.com/oasis-tcs/odata-vocabularies/pull/23 
iv.ODATA-1223 Add OData- prefix back to EntityId header
1.https://github.com/oasis-tcs/odata-abnf/pull/3 
v.ODATA-1208 Specify the finest possible granularity for Duration
1.https://github.com/oasis-tcs/odata-vocabularies/pull/22 
vi.ODATA-1188 Allow using instance annotations in $select and $expand
1.https://github.com/oasis-tcs/odata-vocabularies/pull/24 
2.https://github.com/oasis-tcs/odata-abnf/pull/7
vii.ODATA-868 Describe HTTP encoding for streamed requests and responses
1.https://github.com/oasis-tcs/odata-abnf/pull/4 
 
c.V4.01: NEW or OPEN 
i.ODATA-1243 Clarify whether $orderby and string comparison with ge, gt, le, lt is language-specific
ii.ODATA-1242 Clarify that resolved relative URIs in batch responses cannot contain content-ID references
iii.ODATA-1239 Define a mechanism to distinguish between inserted and updated entities in a Delta Response
iv.ODATA-1238 Clarifications for select-list in ContextUrl
v.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)
vi.ODATA-1168 Clarify the use of ETags for Avoiding Update Conflicts
vii.ODATA-1165 Describe $expand and $select via prose text and examples, remove ABNF snippets
viii.ODATA-1135 Document use of JSON $schema
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
 
d.Data Aggregation: NEW or OPEN
i.ODATA-1218 Transformations for recursive hierarchy processing
ii.ODATA-1207 Clarify need for @odata.id in nested response structures
iii.ODATA-947 Transformation for computing ratios with aggregated values
iv.ODATA-945 Correct examples 53 and 54
 
e.Vocabularies: NEW or OPEN 
i.ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation
ii.ODATA-1216 Terms for POST/PATCH/PUT with system query options to shape response
iii.ODATA-1214 Annotate constructor actions
iv.ODATA-1200 ODATA-884 / Support sample values for types, parameters, request/response bodies
v.ODATA-1194 Add term Core.Example to allow including annotation examples in term definitions
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-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-1177 Allow referencing a (JSON) schema for Edm.Untyped properties
ii.ODATA-1107 Introduce instance annotation to specify which types an instance "implements"
iii.ODATA-1060 Improve specification of element response requirements
 
6.Next meetings [9:50 am PT]
a.Thursday October 25, 2018 during 8-10 am PDT (17:00-19:00 CEST)
b.Thursday November 01, 2018 during 8-10 am PDT (16:00-18:00 CET)  public holiday in Germany
c.Thursday November 08, 2018 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
[17:02] Ralf Handl (SAP SE): Voting Members: 4 of 9 (44%) (used for quorum calculation)
[17:02] Ralf Handl (SAP SE): Note: I forgot to mark Hubert as on leave before the meeting, so the calculated count is off
[17:03] Ralf Handl (SAP SE): Voting Members: 5 of 9 (55%) (used for quorum calculation)
[17:06] Ralf Handl (SAP SE): Voting Members: 6 of 9 (66%) (used for quorum calculation)
[17:07] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT]
[17:07] Ralf Handl (SAP SE): Gerald: add https://issues.oasis-open.org/browse/ODATA-1244 to Data Aggregation issues
[17:08] Ralf Handl (SAP SE): Mike & George: discuss ix.ODATA-1064 Add ability to annotate collections to return only count and NextLink
[17:09] Ralf Handl (SAP SE): Gerald: no need to discuss ODATA-1244 today, just have it on the list
[17:09] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from Octobrer 11, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64065/odata-meeting-233_on-20181011-minutes.html
[17:09] Ralf Handl (SAP SE): Minutes are approved
[17:09] 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-12-06
b.In progress
i.#0036 Register the OData- headers and preferences with IANA  Mark Biamonte  2018-07-26
[17:10] Ralf Handl (SAP SE): 5.Issues [8:20 am PT]
[17:10] Ralf Handl (SAP SE): ix.ODATA-1064 Add ability to annotate collections to return only count and NextLink
[17:10] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1064
[17:10] Ralf Handl (SAP SE): Presentation: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/64089/Example%20of%20need%20to%20return%20NavigationLink..pptx
[18:26] Ralf Handl (SAP SE): Mike: this seems to be a special case of people wanting more control over which control information is part of the response, somewhere between minimal and full metadata
[18:29] Ralf Handl (SAP SE): To be continued next week
[18:30] Ralf Handl (SAP SE): a.APPLIED
i.ODATA-1227 Improve description of filter _expression_ restrictions
1.https://github.com/oasis-tcs/odata-vocabularies/commit/88f6efe8f91b66b147a2fb168f4f560b2c5684ad
[18:30] Ralf Handl (SAP SE): "@Core.Description": "These properties only allow a subset of filter expressions. A valid filter _expression_ for a single property can be enclosed in parentheses and combined by `and` with valid expressions for other properties."
[18:32] Michael Pizzo: I move we close ODATA-1227 as applied
[18:32] George Ericson (Dell): Second
[18:32] Ralf Handl (SAP SE): ODATA-1227 is CLOSED as applied
[18:33] Ralf Handl (SAP SE): ii.ODATA-1222 Validation: add terms MinItems and MaxItems
1.https://github.com/oasis-tcs/odata-vocabularies/pull/21
[18:34] Ralf Handl (SAP SE): new terms
        "MaxItems": {
            "$Kind": "Term",
            "$Type": "Edm.Int64",
            "$AppliesTo": [
                "Collection"
            ],
            "@Core.Description": "The annotated collection must have at most the specified number of items."
        },
        "MinItems": {
            "$Kind": "Term",
            "$Type": "Edm.Int64",
            "$AppliesTo": [
                "Collection"
            ],
            "@Core.Description": "The annotated collection must have at least the specified number of items."
        }
[18:35] Ralf Handl (SAP SE): <Term Name="MaxItems" Type="Edm.Int64" Nullable="false" AppliesTo="Collection">
        <Annotation Term="Core.Description" String="The annotated collection must have at most the specified number of items." />
      </Term>
       <Term Name="MinItems" Type="Edm.Int64" Nullable="false" AppliesTo="Collection">
        <Annotation Term="Core.Description" String="The annotated collection must have at least the specified number of items." />
      </Term>
[18:35] George Ericson (Dell): On 1064: proposing possibilities: 
1) add annotation@IncludeControl=(navigationLink, associationLink... control attributes.)  apply to EntityContainer or other meta
2) add qualifier to header: Accept: Application/Json;odata.metadata='minimum+navigationLink+associationLink+...}
 
Need to check whether or not Redfish requires navigationLink.
[18:37] Michael Pizzo: I move we close ODATA-1222 as applied
[18:37] Matt Borges (SAP): I second
[18:37] Ralf Handl (SAP SE): ODATA-1222 is CLOSED as applied
[18:38] Ralf Handl (SAP SE): b.Pull Requests for partially applied issues
i.ODATA-1241 Support common expressions as values in URL-JSON 
1.https://github.com/oasis-tcs/odata-abnf/pull/5
[18:39] Ralf Handl (SAP SE): Test cases:
  <TestCase Name="5.1.1.1.12 Logical Operator Examples" Rule="boolCommonExpr">
    <Input>["Joe","Smith"] in (["John","Doe"],["Jane","Smith"])</Input>
  </TestCase>
  <TestCase Name="5.1.1.1.12 Logical Operator Examples" Rule="boolCommonExpr">
    <Input>[FirstName,LastName] in (["John","Doe"],["Jane","Smith"])</Input>
  </TestCase>
[18:40] Ralf Handl (SAP SE): More:
  <TestCase Name="5.1.1.14.2 simple array" Rule="commonExpr">
    <Input>FirstName in ["Miller","Smith"]</Input>
  </TestCase>
  <TestCase Name="5.1.1.14.2 array with single-quoted OData strings" Rule="commonExpr">
    <Input>FirstName in ["Miller",'Smith']</Input>
  </TestCase>
  <TestCase Name="5.1.1.14.2 empty array" Rule="commonExpr">
    <Input>FirstName in []</Input>
  </TestCase>
  <TestCase Name="5.1.1.14.2 mixed array" Rule="commonExpr">
    <Input>["Hello",42,true,false,null,'World']</Input>
  </TestCase>
  <TestCase Name="5.1.1.14.2 array of property names" Rule="commonExpr">
    <Input>[FirstName,LastName]</Input>
  </TestCase>
  <TestCase Name="5.1.1.14.2 empty object" Rule="commonExpr">
    <Input>{}</Input>
  </TestCase>
  <TestCase Name="5.1.1.14.2 object with concrete values" Rule="commonExpr">
    <Input>{"FirstName":"John","LastName":"Doe","Sizes":["Large","Small"]}</Input>
  </TestCase>
  <TestCase Name="5.1.1.14.2 object with _expression_ values" Rule="commonExpr">
    <Input>{"FirstName":Customer/FirstName,"LastName":Manager/LastName,"Sizes":[1, 2 add 3]}</Input>
  </TestCase>
  <TestCase Name="5.1.1.14.2 array with 'untyped' values" Rule="commonExpr">
    <Input>[[],{},true,false,null,42,{"no property name":"value","@something":true}]</Input>
  </TestCase>
[18:56] Ralf Handl (SAP SE): Mike: restrict paren-style lists to right side of "in" operator
[18:56] Ralf Handl (SAP SE): Ralf: require at least two items with a comma inbetween?
[18:58] Ralf Handl (SAP SE): Allowed:
a in [1,2]
[18:58] Ralf Handl (SAP SE): a in ([1,2])
[18:58] Michael Pizzo: I don't want to have to have special code in order to check for membership in a single versus multiple values.
[18:59] Ralf Handl (SAP SE): [1,2] eq ([1,2])
[19:02] Ralf Handl (SAP SE): Time's up, continue discussion next week
[19:02] Ralf Handl (SAP SE): Consider scrapping "in (...)" and allow only "in [...]"
[19:02] Ralf Handl (SAP SE): 6.Next meetings [9:50 am PT]
a.Thursday October 25, 2018 during 8-10 am PDT (17:00-19:00 CEST)
b.Thursday November 01, 2018 during 8-10 am PDT (16:00-18:00 CET)  public holiday in Germany
c.Thursday November 08, 2018 during 8-10 am PST (17:00-19:00 CET)
[19:04] Ralf Handl (SAP SE): Tentative agreement to skip meeting on November 01
[19:04] Ralf Handl (SAP SE): 7.AOB and wrap up [9:55 am PT]
[19:04] 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, 17. Oktober 2018 10:23
To: odata@lists.oasis-open.org
Subject: [CAUTION] [odata] Agenda for OData TC meeting on 2018-10-18

 

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

 

2.        Approve agenda [8:05 am PT]

 

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

    1. Minutes from Octobrer 11, 2018 TC meeting: https://www.oasis-open.org/committees/download.php/64065/odata-meeting-233_on-20181011-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-12-06

    1. In progress

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

 

5.        Issues [8:20 am PT]

    1. APPLIED

                                  i.    ODATA-1227 Improve description of filter _expression_ restrictions

        1. https://github.com/oasis-tcs/odata-vocabularies/commit/88f6efe8f91b66b147a2fb168f4f560b2c5684ad

                                 ii.    ODATA-1222 Validation: add terms MinItems and MaxItems

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

 

    1. Pull Requests for partially applied issues

                                  i.    ODATA-1241 Support common expressions as values in URL-JSON

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

                                 ii.    ODATA-1230 /$filter(…) segments in paths and expressions

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

                                               iii.      ODATA-1229 Introduce LocalDateTime TypeDef to apply to string datatype

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

                               iv.    ODATA-1223 Add OData- prefix back to EntityId header

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

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

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

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

        1. https://github.com/oasis-tcs/odata-vocabularies/pull/24
        2. https://github.com/oasis-tcs/odata-abnf/pull/7

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

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

 

    1. V4.01: NEW or OPEN

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

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

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

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

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

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

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

                              viii.    ODATA-1135 Document use of JSON $schema

                                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

 

    1. Data Aggregation: NEW or OPEN

                                  i.    ODATA-1218 Transformations for recursive hierarchy processing

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

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

                                iv.    ODATA-945 Correct examples 53 and 54

 

    1. Vocabularies: NEW or OPEN

                                  i.    ODATA-1226 Ambiguity with Capabilities.ChangeTracking annotation

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

                                iii.    ODATA-1214 Annotate constructor actions

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

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

                                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-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

 

    1. Vocabularies: NEW or OPEN that need more discussion

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

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

                                iii.    ODATA-1060 Improve specification of element response requirements

 

6.        Next meetings [9:50 am PT]

    1. Thursday October 25, 2018 during 8-10 am PDT (17:00-19:00 CEST)
    2. Thursday November 01, 2018 during 8-10 am PDT (16:00-18:00 CET) – public holiday in Germany
    3. Thursday November 08, 2018 during 8-10 am PST (17:00-19:00 CET)

 

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]