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: [odata] Agenda for OData TC meeting on 2017-10-12 - chat transcript


[15:16] Room information was updated by: Stefan Hagen
OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #191
- Thursday, 12 October 2017, 08:00am to 10:00am PDT
  - i.e. 2017-10-12 17:00 to 19:00 CEST (UTC+2)
  - other timezone? Try eg.:
  - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=10&day=12&hour=15&min=0&sec=0&p1=47&p2=69&p3=179
 
UsefulPlaces:
- Chat:
  - http://webconf.soaphub.org/conf/room/odatatc   # ... this place 
- ScreenShare and Voice:
  - https://sap.emea.pgiconnect.com/OData-TC/
[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=43999 
 
2.        Approve agenda [8:05 am PT]
 
3.        Approve minutes from previous meeting(s) [8:10 am PT]
 
        Minutes from October 05, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61713/odata-meeting-190_on-20171005-minutes.html 
 
4.        Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
 
        Action items due
                                  i.    None
 
 
5.        Publication of Vocabularies  [8:20 am PT]
 
        We did add new terms to vocabularies in Errata, so we could publish Errata 04 to provide new official snapshots
        Do we want to take that chance and re-check Errata 03 for typos or sections that need clarification?
 
 
6.        Issues [8:50 am PT]
 
        Vocabularies: APPLIED
                i.    ODATA-958 Capabilities: FilterRestrictions and SortRestrictions for navigation properties
               ii.    ODATA-1055 DeepInsertSupport: allow applying to entity sets and collection-valued navigation properties
              iii.    ODATA-1064 Add ability to annotate collections to return only count and NextLink
              iv.    ODATA-1098 xxxRestrictions can be applied more broadly
 
        Vocabularies: NEW or OPEN
 
              i.    ODATA-1099 Add annotations to describe custom query options and custom headers
 
                  META 1: use issue-specific branches for new terms, types, properties, or add them to master branch and mark them as experimental?
                  META 2: add examples to term definitions as shown here via annotation Core.Example?
 
             ii.    ODATA-1112 Default page size for server-driven paging
            iii.    ODATA-1067 Consider ability to define computed default values
            iv.    ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
             v.    ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
 
 
7.        Next meetings [9:50 am PT]
 
        Thursday October 19, 2017 during 8-10 am PDT
 
8.        AOB and wrap up [9:55 am PT]
 
 
Meeting Member URL:
- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43999" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43999
  - Please use starting approx. 15 minutes before the meeting for self registration. Thanks.
  - Self registration deep link (as a service):
    - https://www.oasis-open.org/apps/org/workgroup/odata/record_my_attendance.php?event_id=43999&confirmed=1

 

[16:08] Stefan1: KeepAlive

 

[16:41] Stefan Hagen: H4Q::Voting Members: 1 of 12 (8%) (used for quorum calculation)
[16:55] Stefan Hagen: H4Q::Voting Members: 1 of 12 (8%) (used for quorum calculation)

 

Room Information:
OASIS Open Data Protocol (OData) TC OData TC Weekly Meeting (Conference Call) #191
- Thursday, 12 October 2017, 08:00am to 10:00am PDT
  - i.e. 2017-10-12 17:00 to 19:00 CEST (UTC+2)
  - other timezone? Try eg.:
  - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=10&day=12&hour=15&min=0&sec=0&p1=47&p2=69&p3=179
 
UsefulPlaces:
- Chat:
  - http://webconf.soaphub.org/conf/room/odatatc   # ... this place 
- ScreenShare and Voice:
  - https://sap.emea.pgiconnect.com/OData-TC/
[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=43999 
 
2.        Approve agenda [8:05 am PT]
 
3.        Approve minutes from previous meeting(s) [8:10 am PT]
 
        Minutes from October 05, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61713/odata-meeting-190_on-20171005-minutes.html 
 
4.        Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]
 
        Action items due
                                  i.    None
 
 
5.        Publication of Vocabularies  [8:20 am PT]
 
        We did add new terms to vocabularies in Errata, so we could publish Errata 04 to provide new official snapshots
        Do we want to take that chance and re-check Errata 03 for typos or sections that need clarification?
 
 
6.        Issues [8:50 am PT]
 
        Vocabularies: APPLIED
                i.    ODATA-958 Capabilities: FilterRestrictions and SortRestrictions for navigation properties
               ii.    ODATA-1055 DeepInsertSupport: allow applying to entity sets and collection-valued navigation properties
              iii.    ODATA-1064 Add ability to annotate collections to return only count and NextLink
              iv.    ODATA-1098 xxxRestrictions can be applied more broadly
 
        Vocabularies: NEW or OPEN
 
              i.    ODATA-1099 Add annotations to describe custom query options and custom headers
 
                  META 1: use issue-specific branches for new terms, types, properties, or add them to master branch and mark them as experimental?
                  META 2: add examples to term definitions as shown here via annotation Core.Example?
 
             ii.    ODATA-1112 Default page size for server-driven paging
            iii.    ODATA-1067 Consider ability to define computed default values
            iv.    ODATA-1005 Make sure we have capabilities for all new 4.01 functionality
             v.    ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)
 
 
7.        Next meetings [9:50 am PT]
 
        Thursday October 19, 2017 during 8-10 am PDT
 
8.        AOB and wrap up [9:55 am PT]
 
 
Meeting Member URL:
- URL = "" href="https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43999" target="_blank">https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=43999
  - Please use starting approx. 15 minutes before the meeting for self registration. Thanks.
  - Self registration deep link (as a service):
    - https://www.oasis-open.org/apps/org/workgroup/odata/record_my_attendance.php?event_id=43999&confirmed=1

 

[17:02] Stefan Hagen: H4Q::Voting Members: 2 of 12 (16%) (used for quorum calculation)
[17:02] Stefan Hagen: H4Q::Voting Members: 4 of 12 (33%) (used for quorum calculation)
[17:03] Stefan Hagen: H4Q::Voting Members: 5 of 12 (41%) (used for quorum calculation)
[17:03] Stefan Hagen: H4Q::Voting Members: 6 of 12 (50%) (used for quorum calculation)
[17:04] Stefan Hagen: 1 voting member missing for quorum, we have registered: Hubert, Mark, Matt, Mike, Ralf, and Stefan

 

[17:05] Martin Zurmuehl (SAP SE): Qourum reached!

 

[17:05] Stefan Hagen: H4Q::Voting Members: 7 of 12 (58%) (used for quorum calculation) yes indeed

 

[17:05] Ralf Handl (SAP SE): Voting Members: 7 of 12 (58%) (used for quorum calculation)
[17:05] Ralf Handl (SAP SE): Achieved quorum: yes
[17:06] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT]
[17:07] Ralf Handl (SAP SE): New issues:
[17:07] Ralf Handl (SAP SE): - https://issues.oasis-open.org/browse/ODATA-1119

 

[17:07] anonymous morphed into George Ericson (Dell)

 

[17:07] George Ericson (Dell): Watching, but not on call yet.

 

[17:07] Ralf Handl (SAP SE): - https://issues.oasis-open.org/browse/ODATA-1120
[17:08] Ralf Handl (SAP SE): - https://issues.oasis-open.org/browse/ODATA-1121
[17:09] Ralf Handl (SAP SE): No further additions, agenda is approved
[17:09] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT]
a.Minutes from October 05, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61713/odata-meeting-190_on-20171005-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] [8:15am PT]
a.Action items due
i.None
[17:10] Ralf Handl (SAP SE): 5.Publication of Vocabularies  [8:20 am PT]
a.We did add new terms to vocabularies in Errata, so we could publish Errata 04 to provide new official snapshots 
b.Do we want to take that chance and re-check Errata 03 for typos or sections that need clarification?
[17:15] Ralf Handl (SAP SE): Park this until George has dialled in, we need to know which "quality level" he needs: is CS01 / Committee Specification sufficient, or is (Errata to) OASIS Standard required
[17:15] Ralf Handl (SAP SE): 6.Issues [8:50 am PT]
a.Vocabularies: APPLIED
[17:15] Ralf Handl (SAP SE): Mike: process ODATA-1119 and ODATA-1120 first
[17:16] Ralf Handl (SAP SE): - https://issues.oasis-open.org/browse/ODATA-1119

 

[17:22] Michael Pizzo: 1) Remove "Collection" in AppliesTo in our capabilities vocabulary. 
2) Add a new term, "CollectionPropertyRestrictions", that can be applied to collection-valued structural properties to describe support for new filter/sort/page type functionality: 
 
<Term Name="CollectionPropertyRestrictions" Type="Collection(Capabilities.CollectionPropertyRestrictions)" AppliesTo="EntitySet"> 
<Annotation Term="Core.Description" String="Describes restrictions on operations applied to collection-valued structural properties" /> 
</Term> 
<ComplexType Name="CollectionPropertyRestrictions"> 
<Property Name="CollectionProperty" Type="Edm.PropertyPath"> 
<Annotation Term="Core.Description" String="Restricted Collection-valued property" /> 
</Property> 
<Property Name="FilterFunctions" Type="Collection(Edm.String)"> 
<Annotation Term="Core.Description" 
String="List of functions and operators supported in $filter. If null, all functions and operators may be attempted" /> 
</Property> 
<Property Name="FilterRestrictions" type ="Capabilities.FilterRestrictionsType"> 
<Annotation Term="Core.Description" String="Restrictions on $filter expressions" /> 
</Property> 
<Property Name="SearchRestrictions" Type="Capabilities.SearchRestrictionsType"> 
<Annotation Term="Core.Description" String="Restrictions on $search expressions" /> 
</Property> 
<Property Name="SortRestrictions" type ="Capabilities.FilterRestrictionsType"> 
<Annotation Term="Core.Description" String="Restrictions on $orderby expressions" /> 
</Property> 
<Property Name="CountRestrictions" Type="Capabilities.CountRestrictionsType"> 
<Annotation Term="Core.Description" String="Restrictions on /$count path suffix and $count=true system query option" /> 
</Property> 
<Property Name="TopSupported" Type="Core.Tag" DefaultValue="true"> 
<Annotation Term="Core.Description" String="Supports $top" /> 
</Property> 
<Property Name="SkipSupported" Type="Core.Tag" DefaultValue="true"> 
<Annotation Term="Core.Description" String="Supports $skip" /> 
</Property> 
</ComplexType>

 

[17:23] Ralf Handl (SAP SE): ODATA-1119 is OPEN

 

[17:34] Michael Pizzo: Fixed a couple typos:
[17:34] Michael Pizzo: <Term Name="CollectionPropertyRestrictions" Type="Collection(Capabilities.CollectionPropertyRestrictionsType)" AppliesTo="EntitySet">
    <Annotation Term="Core.Description" String="Describes restrictions on operations applied to collection-valued structural properties" />
</Term>
<ComplexType Name="CollectionPropertyRestrictionsType">
  <Property Name="CollectionProperty" Type="Edm.PropertyPath">
    <Annotation Term="Core.Description" String="Restricted Collection-valued property" />
  </Property>
  <Property Name="FilterFunctions" Type="Collection(Edm.String)">
    <Annotation Term="Core.Description"
      String="List of functions and operators supported in $filter. If null, all functions and operators may be attempted" />
  </Property>
  <Property Name="FilterRestrictions" type ="Capabilities.FilterRestrictionsType">
    <Annotation Term="Core.Description" String="Restrictions on $filter expressions" />
  </Property>
  <Property Name="SearchRestrictions" Type="Capabilities.SearchRestrictionsType">
    <Annotation Term="Core.Description" String="Restrictions on $search expressions" />
  </Property>
  <Property Name="SortRestrictions" type ="Capabilities.SortRestrictionsType">
    <Annotation Term="Core.Description" String="Restrictions on $orderby expressions" />
  </Property>
  <Property Name="CountRestrictions" Type="Capabilities.CountRestrictionsType">
    <Annotation Term="Core.Description" String="Restrictions on /$count path suffix and $count=true system query option" />
  </Property>
  <Property Name="TopSupported" Type="Core.Tag" DefaultValue="true">
     <Annotation Term="Core.Description" String="Supports $top" />
  </Property>
  <Property Name="SkipSupported" Type="Core.Tag" DefaultValue="true">
     <Annotation Term="Core.Description" String="Supports $skip" />
  </Property>
</ComplexType>
[17:40] Michael Pizzo: We could also add "SupportsInsert" to support POST to add a new item to the collection. Could also add "SupportsUpdate" and "SupportsDelete" that would only apply to ordered collections.

 

[17:42] Ralf Handl (SAP SE): Rather park this idea in a new issue and wait for active use case

 

[17:43] George Ericson (Dell): Makes sense.
[17:44] George Ericson (Dell): Adding that is.  My concern is to be able to represent, in Instance Annotations that all of the CRUD operations are covered.

 

[17:47] Ralf Handl (SAP SE): Then we might want to use "Insertable", "Updatable", "Deletable" as in the current XxxRestrictions

 

[17:47] Michael Pizzo: Updated proposal with Insertable, Updatable, and Deletable:
<Term Name="CollectionPropertyRestrictions" Type="Collection(Capabilities.CollectionPropertyRestrictionsType)" AppliesTo="EntitySet">
    <Annotation Term="Core.Description" String="Describes restrictions on operations applied to collection-valued structural properties" />
</Term>
<ComplexType Name="CollectionPropertyRestrictionsType">
  <Property Name="CollectionProperty" Type="Edm.PropertyPath">
    <Annotation Term="Core.Description" String="Restricted Collection-valued property" />
  </Property>
  <Property Name="FilterFunctions" Type="Collection(Edm.String)">
    <Annotation Term="Core.Description"
      String="List of functions and operators supported in $filter. If null, all functions and operators may be attempted" />
  </Property>
  <Property Name="FilterRestrictions" type ="Capabilities.FilterRestrictionsType">
    <Annotation Term="Core.Description" String="Restrictions on $filter expressions" />
  </Property>
  <Property Name="SearchRestrictions" Type="Capabilities.SearchRestrictionsType">
    <Annotation Term="Core.Description" String="Restrictions on $search expressions" />
  </Property>
  <Property Name="SortRestrictions" type ="Capabilities.SortRestrictionsType">
    <Annotation Term="Core.Description" String="Restrictions on $orderby expressions" />
  </Property>
  <Property Name="CountRestrictions" Type="Capabilities.CountRestrictionsType">
    <Annotation Term="Core.Description" String="Restrictions on /$count path suffix and $count=true system query option" />
  </Property>
  <Property Name="TopSupported" Type="Core.Tag" DefaultValue="true">
     <Annotation Term="Core.Description" String="Supports $top" />
  </Property>
  <Property Name="SkipSupported" Type="Core.Tag" DefaultValue="true">
     <Annotation Term="Core.Description" String="Supports $skip" />
  </Property>
  <Property Name="Insertable" Type="Edm.Boolean" DefaultValue="true">
     <Annotation Term="Core.Description" String="This collection supports inserts" />
  </Property>
  <Property Name="Updatable" Type="Edm.Boolean" DefaultValue="true">
     <Annotation Term="Core.Description" String="Members of this ordered collection can be updated by ordinal" />
  </Property>
  <Property Name="Deletable" Type="Edm.Boolean" DefaultValue="true">
     <Annotation Term="Core.Description" String="Members of this ordered collection can be deleted by ordinal" />
  </Property>
</ComplexType>
[17:48] Michael Pizzo: I move we approve ODATA-1119 as proposed.

 

[17:49] Hubert Heijkers (IBM): I second

 

[17:49] Martin Zurmuehl (SAP SE): I second

 

[17:49] Ralf Handl (SAP SE): ODATA-1119 is RESOLVED as proposed
[17:49] Ralf Handl (SAP SE): https://issues.oasis-open.org/browse/ODATA-1120
[17:50] Ralf Handl (SAP SE): Proposal:
1) Remove "Collection" from AppliesTo for DeepInsertSupport; keep "EntityContainer" and "EntitySet". 
2) Add DeepInsertSupport, CountRestrictions, NavigationRestrictions, IndexableByKey, TopSupported, SkipSupported, ExpandRestrictions, SearchRestrictions, InsertRestrictions, UpdateRestrictions, and DeleteRestrictions to our NavigationPropertyRestrictions.

 

[17:56] Michael Pizzo: We don't really need ExpandRestrictions, NavigationRestrictions, CountRestrictions as they already have property paths.

 

[17:57] Ralf Handl (SAP SE): I move to remove CountRestrictions from the proposal in ODATA-1119

 

[17:57] Michael Pizzo: I second

 

[17:57] Ralf Handl (SAP SE): Motion passes

 

[17:59] Michael Pizzo: Revised proposal:
 
1) Remove "Collection" from AppliesTo for DeepInsertSupport; keep "EntityContainer" and "EntitySet". 
2) Add DeepInsertSupport, IndexableByKey, TopSupported, SkipSupported, SearchRestrictions, InsertRestrictions, UpdateRestrictions, and DeleteRestrictions to our NavigationPropertyRestrictions.
[17:59] Michael Pizzo: I move we resolve ODATA-1120 as proposed.

 

[18:00] George Ericson (Dell): Second

 

[18:00] Ralf Handl (SAP SE): ODATA-1120 is OPEN

 

[18:00] Martin Zurmuehl (SAP SE): I second, after opening

 

[18:00] Ralf Handl (SAP SE): ODATA-1120 is RESOLVED as proposed
[18:01] Ralf Handl (SAP SE): i.ODATA-958 Capabilities: FilterRestrictions and SortRestrictions for navigation properties

 

[18:02] George Ericson (Dell): Second

 

[18:03] Michael Pizzo: (George seconded Mike's verbal motion to approve the application of ODATA-958)
[18:04] Michael Pizzo: I move we approve the application of ODATA-958.

 

[18:04] George Ericson (Dell): second

 

[18:04] Ralf Handl (SAP SE): ODATA-958 is CLOSED as applied
[18:05] Ralf Handl (SAP SE): ii.ODATA-1055 DeepInsertSupport: allow applying to entity sets and collection-valued navigation properties

 

[18:05] Michael Pizzo: I move we close ODATA-1055 as applied.

 

[18:06] George Ericson (Dell): second

 

[18:06] Ralf Handl (SAP SE): Note: "Collection" will be removed again by ODATA-1120
[18:07] Ralf Handl (SAP SE): ODATA-1055 is CLOSED as applied
[18:07] Ralf Handl (SAP SE): iv.ODATA-1098 xxxRestrictions can be applied more broadly

 

[18:21] Michael Pizzo: Now that we have a consistent place to annotate these starting from the entity set, we don't need to add them to the entity type. Further adding the ability to specify them in two places brings up the question of how to evaluate the effective restrictions if the same restriction is specified in a conflicting manner.
[18:22] Michael Pizzo: Now that we have a way to consistently apply these restrictions to both (nested) navigation properties and structural collection-valued properties, I move we rollback ODATA-1098 by removing "EntityType" from the set of restriction capability terms.

 

[18:22] George Ericson (Dell): second
[18:24] George Ericson (Dell): Move to reject application of ODATA-1098

 

[18:24] Michael Pizzo: process: reject application, reject resolution, re-resolve as removing EntityType.

 

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

 

[18:24] George Ericson (Dell): Move to reject the resolution of ODATA-1098

 

[18:24] Michael Pizzo: I second

 

[18:25] Ralf Handl (SAP SE): No objections, ODATA-1098 is OPEN (again)

 

[18:25] George Ericson (Dell): Move to remove EntityType from ODATA-1098
[18:26] George Ericson (Dell): Revised: Move to remove EntityType and Collection from ODATA-1098

 

[18:26] Mark Biamonte (Progress): I second

 

[18:27] Ralf Handl (SAP SE): ODATA-1098 is RESOLVED with the amended proposal
[18:27] Ralf Handl (SAP SE): iii.ODATA-1064 Add ability to annotate collections to return only count and NextLink

 

[18:46] Michael Pizzo: Issue: NavigationLink/AssociationLink here is really talking about a json minimal-metadata format compression feature, not a protocol feature.
[18:46] Michael Pizzo: How do we interpret the annotation for non-json metadata formats?
[18:46] Michael Pizzo: How do we interpret the annotation for json no-metadata formats?
[18:50] Michael Pizzo: One option would be to have a json-specific vocabulary to control json-specific serialization optimizations, but that's probably not worth it for this scenario.
[18:51] Michael Pizzo: I'm okay to be pragmatic, word this as generically as possible, and live with it as part of core, I just wanted to call out that it was a bit of a cheat.
[18:55] Michael Pizzo: For no-metadata cases, we currently say that count, nextlink, and deltalink are included in no-metadata cases, if requested.
[18:55] Michael Pizzo: What happens if I explicitly select a navigation property in no-metadata case?

 

[18:58] George Ericson (Dell): dropping

 

[18:58] Ralf Handl (SAP SE): Next week: discuss how to publish snapshots of vocabularies
[18:58] Ralf Handl (SAP SE): Week after next: IANA registration
[18:58] Ralf Handl (SAP SE): Hubert can't attend next week
[18:58] Ralf Handl (SAP SE): We will discuss issue proposals if we don't get quorum
[18:59] Ralf Handl (SAP SE): OpenAPI: way forward also next week
[18:59] Ralf Handl (SAP SE): 7.Next meetings [9:50 am PT]
a.Thursday October 19, 2017 during 8-10 am PDT
 
8.AOB and wrap up [9:55 am PT]
[19:00] Ralf Handl (SAP SE): Meeting is adjourned

 

[19:00] Stefan Hagen: @Ralf: minutes draft will be published tomorrow before noon CEST

 

[19:00] Ralf Handl (SAP SE): @Stefan: Cool, thanks!

 

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Dienstag, 10. Oktober 2017 18:40
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2017-10-12

 

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

 

2.        Approve agenda [8:05 am PT]

 

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

    1. Minutes from October 05, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/61713/odata-meeting-190_on-20171005-minutes.html

 

4.        Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [8:15am PT]

    1. Action items due

                                  i.    None

 

5.        Publication of Vocabularies  [8:20 am PT]

    1. We did add new terms to vocabularies in Errata, so we could publish Errata 04 to provide new “official” snapshots
    2. Do we want to take that chance and re-check Errata 03 for typos or sections that need clarification?

 

6.        Issues [8:50 am PT]

    1. Vocabularies: APPLIED

                                  i.    ODATA-958 Capabilities: FilterRestrictions and SortRestrictions for navigation properties

                                 ii.    ODATA-1055 DeepInsertSupport: allow applying to entity sets and collection-valued navigation properties

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

                                iv.    ODATA-1098 xxxRestrictions can be applied more broadly

 

    1. Vocabularies: NEW or OPEN

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

        1. META 1: use issue-specific branches for new terms, types, properties, or add them to master branch and mark them as experimental?
        2. META 2: add examples to term definitions as shown here via annotation Core.Example?

                                 ii.    ODATA-1112 Default page size for server-driven paging

                                iii.    ODATA-1067 Consider ability to define computed default values

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

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

 

7.        Next meetings [9:50 am PT]

    1. Thursday October 19, 2017 during 8-10 am PDT

 

8.        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]