RE: [odata] Agenda for OData TC meeting on 2017-04-06

[16:43] Stefan Hagen: RegInfo{Voting Members: 1 of 10 (10%) (used for quorum calculation)}

[16:48] Stefan Hagen: RegInfo{Voting Members: 1 of 10 (10%) (used for quorum calculation)}

[16:57] Stefan Hagen: RegInfo{Voting Members: 1 of 10 (10%) (used for quorum calculation)}

[16:59] Stefan Hagen: RegInfo{Voting Members: 2 of 10 (20%) (used for quorum calculation)}

[17:00] Stefan Hagen: RegInfo{Voting Members: 3 of 10 (30%) (used for quorum calculation)}

[17:01] Stefan Hagen: RegInfo{Voting Members: 4 of 10 (40%) (used for quorum calculation)}

[17:01] Stefan Hagen: RegInfo{Voting Members: 5 of 10 (50%) (used for quorum calculation)}

[17:05] Stefan Hagen: RegInfo{Voting Members: 7 of 10 (70%) (used for quorum calculation)}

[17:05] Stefan Hagen: We seem to be quorate ...

[17:05] Stefan Hagen: Note Screen share (and voice connect via): https://sap.emea.pgiconnect.com/OData-TC/

[17:06] Ralf Handl (SAP SE): 2.Approve agenda [8:05 am PT]

[17:07] Ralf Handl (SAP SE): Agenda is approved

[17:07] Ralf Handl (SAP SE): 3.Approve minutes from previous meeting(s) [8:10 am PT]

a.Minutes from March 30, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/60407/odata-meeting-168_on-20170330-minutes.html

[17:07] Ralf Handl (SAP SE): Minutes are approved

[17:08] 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:08] Ralf Handl (SAP SE): 5.V4.01 [8:20 am PT]

a.Issues for V4.01_CSD02 ready for resolution

[17:08] Ralf Handl (SAP SE): v.ODATA-1063 Allow $format and custom query options for all requests

[17:10] Ralf Handl (SAP SE): ODATA-1063 is OPEN

[17:11] Hubert Heijkers (IBM): I move to resolve ODATA-1063 as proposed.

[17:11] Mike Pizzo: I second

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

[17:12] Ralf Handl (SAP SE): iv.ODATA-1061 Allow key expressions in Path constructs within annotations

[17:12] Ralf Handl (SAP SE): <Annotation Term="Display.visible" Path="/this.container/Settings/FeatureXxxIsAvailable" />

[17:13] Ralf Handl (SAP SE): <Annotation Term="Display.visible" Path="/this.container/SettingsCollection('FeatureXxx')/IsAvailable" />

[17:15] Ralf Handl (SAP SE): ODATA-1061 is OPEN

[17:15] Ralf Handl (SAP SE): <Annotation Term="Display.title" Path="/this.container/Products(ID=ProductID)Name" />

[17:16] Ralf Handl (SAP SE): <Annotation Term="Display.title" Path="/this.container/Products(ID=ProductID)/Name" />

[17:17] Ralf Handl (SAP SE): <Annotation Term="Display.title" Path="/this.container/Products(IProductID)Name" />

[17:17] Ralf Handl (SAP SE): <Annotation Term="Display.title" Path="/this.container/Products(ProductID)Name" />

[17:17] Ralf Handl (SAP SE): <Annotation Term="Display.title" Path="/this.container/Products(ProductID)/Name" />

[17:18] Ralf Handl (SAP SE): <Annotation Term="Display.title" Path="/this.container/OrderItems(OrderID=42,ItemID=2)/Price" />

[17:24] Ralf Handl (SAP SE): <Annotation Term="Display.title" Path="/this.container/Products(Product/ID)/Name" /> -- path for fetching key value

[17:25] Ralf Handl (SAP SE): Only literals and paths allowed as "key values", no arithmetic expressions or functions

[17:26] Hubert Heijkers (IBM): I move to resolve ODATA-1061 as per the amended proposal.

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

[17:27] Ralf Handl (SAP SE): ODATA-1061 is RESOLVED

[17:27] Ralf Handl (SAP SE): iii.ODATA-1058 Add ability to annotate revisions with information on all elements

[17:28] Ralf Handl (SAP SE): ii.ODATA-1057 Add path segment /$each

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

[17:33] Mike Pizzo: I move we resolve ODATA-1057 as proposed

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

[17:33] Ralf Handl (SAP SE): ODATA-1057 is RESOLVED

[17:34] Ralf Handl (SAP SE): iii.ODATA-1058 Add ability to annotate revisions with information on all elements

[17:34] Mike Pizzo: https://issues.oasis-open.org/browse/ODATA-1058

[17:34] Ralf Handl (SAP SE): The proposal is to create a 'Revision' term in the Core vocabulary that may be applied to any element. Elements defined in a schema may then evolve over time and with their complete revision history intact. The proposal is as follows:

<Term Name="Revision" Type="CsdlMetamodel.RevisionType">

<Annotation Term="OData.Description" String="Defines an annotation to mark a revision." />

</Term>

[17:35] Mike Pizzo: <EnumType Name="RevisionKind">

<Member Name="Add"/>

<Member Name="Insert"/>

<Member Name="Change"/>

<Member Name="Delete"/>

<Member Name="Deprecate"/>

</EnumType>

[17:36] Mike Pizzo: <ComplexType Name="RevisionType">

<Property Name="Version" Type="Edm.String">

<Annotation Term="OData.Description" String="An 'm.n.e' string value composed of three decimal values separated by '.'. These values express major, minor, and errata version numbers for this revision where 'm' is an integer representing a major version. Major versions are expected to provide similar but extended functionality, but may be incompatible in any way. The minor version 'n' may include additional features and may not remove any features from previous minor versions of the same major version. The set of allowable values must include all allowable values of previous minor versions of the same major version. The errata version 'e' is used to mark a change that fixes something that was broken in the including minor version. By its nature, an errata version may include incompatible changes to fix a prior version."/>

</Property>

<Property Name="Type" Type="CsdlMetamodel.RevisionKind">

<Annotation Term="Core.Description" String="An enumerated value expressing the type of revision." />

</Property>

<Property Name="Description" Type="String">

<Annotation Term="Core.Description" String="Text description of the reason for the revision." />

</Property>

</ComplexType>

[17:37] Ralf Handl (SAP SE): Expection: revisions cumulate over time, so revision needs to state which version it was introduced

[17:42] anonymous morphed into Martin Zurmuehl (SAP SE)

[17:44] Ralf Handl (SAP SE): <Property Name="NewProp" ...>

  <Annotation Term="Core.Revision" Qualifier="first">

    <Record>

      <PropertyValue Property="Version" String="10.4.1" />

      <PropertyValue Property="Type" EnumMember="Core.RevisionKind/Insert" />

    </Record>

  </Annotation>

</Property>

[17:46] Ralf Handl (SAP SE): In JSON:

"@Core.Revision#first":{"Version":"10.4.1","Type":"Insert"}

[17:47] Ralf Handl (SAP SE): Multiple revisions of the same model element:

<Property Name="NewProp" ...>

  <Annotation Term="Core.Revision" Qualifier="first">

    <Record>

      <PropertyValue Property="Version" String="10.4.1" />

      <PropertyValue Property="Type" EnumMember="Core.RevisionKind/Insert" />

    </Record>

  </Annotation>

  <Annotation Term="Core.Revision" Qualifier="second">

    <Record>

      <PropertyValue Property="Version" String="10.4.2" />

      <PropertyValue Property="Type" EnumMember="Core.RevisionKind/Deprecate" />

    </Record>

  </Annotation>

</Property>

[17:48] Mike Pizzo: <Annotation Term="Core.Revision" Qualifier="v10_4_1">

    <Record>

      <PropertyValue Property="Type" EnumMember="Core.RevisionKind/Insert" />

    </Record>

  </Annotation>

[17:49] Ralf Handl (SAP SE): Alternative: collection-valued annotation:

<Property Name="NewProp" ...>

  <Annotation Term="Core.Revision">

    <Collection>

      <Record>

        <PropertyValue Property="Version" String="10.4.1" />

        <PropertyValue Property="Type" EnumMember="Core.RevisionKind/Insert" />

      </Record>

      <Record>

        <PropertyValue Property="Version" String="10.4.2" />

        <PropertyValue Property="Type" EnumMember="Core.RevisionKind/Deprecate" />

      </Record>

    </Collection>

  </Annotation>

</Property>

[17:51] Mike Pizzo: Updated term definition:

[17:51] Mike Pizzo: <Term Name="Revision"  Type="Collection(CsdlMetamodel.RevisionType)">

<Annotation Term="OData.Description" String="Defines an annotation to mark a revision." />

</Term>

[17:51] Ralf Handl (SAP SE): George, Martin, Mark, and Mike like the collection-valued notation

[17:52] Ralf Handl (SAP SE): It also allows ordering of revisions by version/time

[17:53] Ralf Handl (SAP SE): Example for description via annotation:

      <Record>

        <PropertyValue Property="Version" String="10.4.2" />

        <PropertyValue Property="Type" EnumMember="Core.RevisionKind/Deprecate" />

        <Annotation Term="Core.Description" String="Cool new property requested by BigCustomer" />

      </Record>

[17:54] Ralf Handl (SAP SE): Example for description via property:

      <Record>

        <PropertyValue Property="Version" String="10.4.2" />

        <PropertyValue Property="Type" EnumMember="Core.RevisionKind/Deprecate" />

        <PropertyValue Property="Description" String="Cool new property requested by BigCustomer" />

      </Record>

[17:55] Ralf Handl (SAP SE): Example for description via annotation:

      "@Core.Revision":[{

        "Version":"10.4.2",

        "Type":"Add" />

        "@Core.Description":"Cool new property requested by BigCustomer"

}]

[17:56] Ralf Handl (SAP SE): Example for description via annotation:

      "@Core.Revision":[{

        "Version":"10.4.2",

        "Type":"Add",

        "Description":"Cool new property requested by BigCustomer"

}]

[17:58] Ralf Handl (SAP SE): Mike has slight preference for second variant with explicit Description property

[17:58] Stefan Hagen: @George: I registered your attendance.

[17:58] Ralf Handl (SAP SE): Is more explicit in the term definition

[17:58] Ralf Handl (SAP SE): <EnumType Name="RevisionKind">

<Member Name="Add"/>

<Member Name="Insert"/>

<Member Name="Change"/>

<Member Name="Delete"/>

<Member Name="Deprecate"/>

</EnumType>

[17:59] Ralf Handl (SAP SE): Ralfs preference: New, Changed, Deprecated

[18:00] Ralf Handl (SAP SE): Mike: Added, Changed, Deprecated

[18:00] Ralf Handl (SAP SE): George: Add, Change, Deprecate

[18:00] Ralf Handl (SAP SE): Mike: keep "Deleted" and add an optional property "ChildElement"

[18:03] Mike Pizzo: If RevisionKind is changed, you could add a structured property that was membername and revisionkind...

[18:03] Mike Pizzo: (including deleted)

[18:04] Ralf Handl (SAP SE): Example for Deleted:

<EntityType Name="...

  <Annotation Term="Core.Revision">

    <Collection>

      <Record>

        <PropertyValue Property="Version" String="10.4.2" />

        <PropertyValue Property="Type" EnumMember="Core.RevisionKind/Deleted" />

        <PropertyValue Property="Description" String="Unused property removed" />

        <PropertyValue Property="ChildElement" String="SomeRandomProperty" />

      </Record>

    </Collection>

  </Annotation>

</EntityType>

[18:09] Ralf Handl (SAP SE): George: Deletion should only happen when moving to the next major version, so Deleted annotation is not really necessary

[18:09] Ralf Handl (SAP SE): So no ChildElement, and directly annotate the added/changed/deprecated model element

[18:10] Mike Pizzo: George points out annotating the structured object would require multiple records with the same version...

[18:12] Ralf Handl (SAP SE): Mike: use "Kind" for property name and enumtype name suffix instead of "Type"

[18:12] Ralf Handl (SAP SE): Martin: use "Kind"

[18:14] Ralf Handl (SAP SE): George: XML uses "Kind" for enumerations

[18:15] Ralf Handl (SAP SE): Enumeration member names: Added, Modified, Deprecated

[18:16] Mike Pizzo: The proposal is to create a 'Revision' term in the Core vocabulary that may be applied to any element.  Elements defined in a schema may then evolve over time and with their complete revision history intact. The proposal is as follows:

<Term Name="Revision"  Type="Collection(CsdlMetamodel.RevisionType)">

<Annotation Term="OData.Description" String="Defines an annotation to mark a revision." />

</Term>

The members of the collection are sequential.

<ComplexType Name="RevisionType">

<Property Name="Version" Type="Edm.String">

<Annotation Term="OData.Description" String="An 'm.n.e' string value composed of three decimal values separated by '.'.  These values express major, minor, and errata version numbers for this revision where 'm' is an integer representing a major version.  Major versions are expected to provide similar but extended functionality, but may be incompatible in any way. The minor version 'n' may include additional features and may not remove any features from previous minor versions of the same major version.  The set of allowable values must include all allowable values of previous minor versions of the same major version. The errata version 'e' is used to mark a change that fixes something that was broken in the including minor version.  By its nature, an errata version may include incompatible changes to fix a prior version."/>

</Property>

<Property Name="Kind" Type="CsdlMetamodel.RevisionKind">

<Annotation Term="Core.Description" String="An enumerated value expressing the type of revision." />

</Property>

<Property Name="Description" Type="String">

<Annotation Term="Core.Description" String="Text description of the reason for the revision." />

</Property>

</ComplexType>

<EnumType Name="RevisionKind">

<Member Name="Added"/>

<Member Name="Modified"/>

<Member Name="Deprecated"/>

</EnumType>

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

[18:18] Martin Zurmuehl (SAP SE): I move we resolve ODATA-1058 as proposed (revised proposal see chat)

[18:18] Mike Pizzo: I second

[18:18] Ralf Handl (SAP SE): ODATA-1058 is RESOLVED

[18:18] Martin Zurmuehl (SAP SE): proposal is updated in jira

[18:19] Ralf Handl (SAP SE): i.ODATA-1005 Make sure we have capabilities for all new 4.01 functionality

[18:53] Stefan Hagen: Skipped

[18:53] Stefan Hagen: 5.2 Document walkthrough

[18:53] Stefan Hagen: 5.2.1 Part 1: Protocol

[18:53] Stefan Hagen: URL = "">https://www.oasis-open.org/committees/download.php/60437/odata-v4.01-wd02-part1-protocol-2017-04-05.docx

[18:53] Stefan Hagen: All walk through the document, discuss and perform online changes during the meeting.

[19:00] Ralf Handl (SAP SE): 6.Next meeting [9:50 am PT]

a.Thursday April 13, 201, 2017 during 8-10 am PDT  already confirmed

b.Thursday April 20, 201, 2017 during 8-10 am PDT?

[19:00] Ralf Handl (SAP SE): Mark can't attend week after next

[19:01] Ralf Handl (SAP SE): 7.AOB and wrap up [9:55 am PT]

[19:01] Ralf Handl (SAP SE): Meeting is adjourned

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Mittwoch, 5. April 2017 11:29
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2017-04-06

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

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

2. Approve agenda [8:05 am PT]

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

a. Minutes from March 30, 2017 TC meeting: https://www.oasis-open.org/committees/download.php/60407/odata-meeting-168_on-20170330-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]

a. Action items due

i. None

5. V4.01 [8:20 am PT]

a. Issues for V4.01_CSD02 ready for resolution