RE: [odata] Agenda for OData TC meeting on 2016-07-21

anonymous111 asked for a victim, I choose... anonymous11

Room information was updated by: anonymous1111

<place room="room" info="info" call-in="call-in" here="here"></place>

anonymous111111 asks: null

Magic 8-Ball says: Outlook not so good

anonymous3111 asked for a victim, I choose... anonymous2

anonymous3111111 asks: null

Magic 8-Ball says: Concentrate and ask again

anonymous2111 asked for a victim, I choose... KenBaclawski

anonymous2111111 asks: null

Magic 8-Ball says: You may rely on it

Ralf Handl (SAP): Voting Members: 4 of 11 (36%)

Ralf Handl (SAP): Voting Members: 5 of 11 (45%)

Ralf Handl (SAP): Voting Members: 6 of 11 (54%)

Ralf Handl (SAP): Achieved quorumyes

Ralf Handl (SAP): 2.Approve agenda [6:05am PT]

Ralf Handl (SAP): Add discussion on OpenAPI

Ralf Handl (SAP): Discuss OpenAPI before going into V4.01 issues

Ralf Handl (SAP): Adapted agenda is approved

Ralf Handl (SAP): 3.Approve minutes from previous meeting(s) [6:10am PT]

a.Minutes from July 14, 2016 TC meeting: https://www.oasis-open.org/committees/download.php/58508/odata-meeting-137_on-20160714-minutes.html

Ralf Handl (SAP): Minutes are approved

Ralf Handl (SAP): 4.Review action items [Action item list: https://www.oasis-open.org/apps/org/workgroup/odata/members/action_items.php] [6:15am PT]

a.Action items due

i.None

Ralf Handl (SAP): 5. Discuss way forward OpenAPI

Ralf Handl (SAP): Recap: Ram asked about RAML and whether we should consider that

Ralf Handl (SAP): Hubert: Current OpenAPI-based format doesn't feel like OData

Ralf Handl (SAP): Different interests

Ralf Handl (SAP): - OpenAPI representation, potentially lossy, x- stuff might distract or even impede

Ralf Handl (SAP): - RAML representation, potentially lossy, extensions might distract or even impede

Ralf Handl (SAP): - full-fidelity JSON format, no interest in OpenAPI, JSON Schema, RAML, ... - just lossless JSON $metadata

Ralf Handl (SAP): Hubert: pure OpenAPI part of our current spec is lossy anyway

Ralf Handl (SAP): Mark: considering to omit x- extensions and not risk to confuse OpenAPI tools that can't ignore x- extensions

Ralf Handl (SAP): Susan: have an open discussion on which way to go

Ralf Handl (SAP): Mike: write summary/intro to kickstart that discussion

Ralf Handl (SAP): Decide in future meeting on how to set up this discussion

Ralf Handl (SAP): 6.V4.01 [6:20am PT]

a.Issues for V4.01_WD01 in New or Open state

i.Ripe for resolution

1.ODATA-923 $expand for $metadata to include referenced schemas

Ralf Handl (SAP): ODATA-923 is OPEN

Mike Pizzo: Note: in generic client scenario, the client has the namespace-or-alias qualified type name, or entity set name from @odata.context.

Mike Pizzo: Scenario-wise, what the client really wants is the ability to get the metadata necessary to understand a particular response.  So, given a context, it wants to (minimally) get back the recursive set of types referenced by that context (and probably wouldn't really care about any additional types defined in the namespaces used by the referenced types).

Mike Pizzo: also note, service can't just include referenced files; it has to make sure there are no conflicts in the defined aliases.

Ralf Handl (SAP): Mike to get feedback from implementation team(s) and flesh out proposal

Ralf Handl (SAP): ii.OData Protocol

1.ODATA-919 Specify the result type for each operation based on operator types

Ralf Handl (SAP): Ralf to contact Evan whether he can round off the proposal

Ralf Handl (SAP): 2.ODATA-942 How should headers applied to a batch affect statements within a batch

Mike Pizzo: Michael Pizzo added a comment - a few seconds ago

For each header, possibilities on a batch could be:

 1) Not defined at the batch level

 2) Defined and applies to the batch itself, not individual requests

 3) Applies to each request within the batch (perhaps as a default, overridden (or combined?) if the statement contains the same header)

Ralf Handl (SAP): Mark takes over this issue

Ralf Handl (SAP): iii.Annotations

1.ODATA-571 Add annotation for properties that are (not) part of the default selection if no $select is specified

Mike Pizzo: Mark will go through the existing headers defined in [Protocol] and propose which of these behaviors is most appropriate (and which require further discussion)

Ralf Handl (SAP): I move to close ODATA-571 without action

Hubert Heijkers: I second

Ralf Handl (SAP): ODATA-571 is closed without action

Ralf Handl (SAP): 2.ODATA-735 Enhance the CSDL for instance annotations

Ralf Handl (SAP): ODATA-735 is OPEN

Ralf Handl (SAP): Need more information on use cases

Ralf Handl (SAP): And benefits for clients

Ralf Handl (SAP): Inclination to close it without action

Ralf Handl (SAP): Postponed

Ralf Handl (SAP): 3.ODATA-811 Define propagation and (partial) overriding of annotations

Ralf Handl (SAP): ODATA-811 is OPEN

Ralf Handl (SAP): Mike: agree that annotations are propagated along usage (type definition to property, ...)

Ralf Handl (SAP): Mike: agree that annotations are propagated along inheritance (base type to derived type)

Mike Pizzo: -Annotations are applied wherever the type is used.

-Annotations are propagated along inheritance

-Annotations defined in a derived type take precedence over the same type defined in the base type.

     -For structured annotations, should we apply merge (PATCH) semantics or replace (PUT) semantics?

Mike Pizzo: -For collection-values annotations, should it replace or append?

Ralf Handl (SAP): Ralf to get concrete scenarios for PATCH semantics for structured terms

Ralf Handl (SAP): Postponed

Ralf Handl (SAP): 4.ODATA-859 Define term, semantics for inserting error information into a (mostly) successful response

Ralf Handl (SAP): This instance annotation can appear everywhere in a response, even on a property

Ralf Handl (SAP): Could be used for in-stream errors when streaming responses, see ODATA-868

Ralf Handl (SAP): ODATA-859 is OPEN

Ralf Handl (SAP): Potential changes to the term definition

Ralf Handl (SAP): - make term array-valued

Ralf Handl (SAP): - just one complex type with details - recursively

Hubert Heijkers: <Term Name="Notification" Type="Core.NotificationType">

        <Annotation Term="Core.Description" String="Instance annotation for warning and info notifications" />

      </Term>

      <ComplexType Name="NotificationType">

        <Property Name="code" Type="Edm.String" Nullable="false" />

        <Property Name="message" Type="Edm.String" Nullable="false">

          <Annotation Term="Core.IsLanguageDependent" />

        </Property>

        <Property Name="severity" Type="Core.NotificationSeverity" Nullable="false" />

        <Property Name="target" Type="Edm.String" Nullable="true">

          <Annotation Term="Core.Description"

            String="A path to the target of the notification detail, relative to the annotated instance" />

        </Property>

        <Property Name="details" Type="Collection(Common.NotificationType)" Nullable="false" />

      </ComplexType>

      <TypeDefinition Name="NotificationSeverity" UnderlyingType="Edm.String">

        <Annotation Term="Validation.AllowedValues">

          <Record>

            <PropertyValue Property="Values">

              <Collection>

                <Record>

                  <PropertyValue Property="Value" String="success" />

                </Record>

                <Record>

                  <PropertyValue Property="Value" String="info" />

                </Record>

                <Record>

                  <PropertyValue Property="Value" String="warning" />

                </Record>

                <Record>

                  <PropertyValue Property="Value" String="error" />

                </Record>

              </Collection>

            </PropertyValue>

          </Record>

        </Annotation>

      </TypeDefinition>

Hubert Heijkers: <Term Name="Notifications" Type="Collection(Core.NotificationType)">

        <Annotation Term="Core.Description" String="Instance annotation for warning and info notifications" />

      </Term>

Ralf Handl (SAP): Mike and Ralf prefer "Messages" instead of "Notifications"

Ralf Handl (SAP): DMTF has "ExtendedInformation" which is a collection of "Messages"

Ralf Handl (SAP): Mark: "notification" more common in sense of push notifications

Ralf Handl (SAP): ODATA-859 is OPEN

Mike Pizzo: I second

Hubert Heijkers: I move to resolve ODATA-859 as proposed.

Mike Pizzo: I second again

Ralf Handl (SAP): ODATA-859 is resolved as proposed

Ralf Handl (SAP): 5.ODATA-883 Validation Vocabulary: add MultipleOf term

Ralf Handl (SAP): ODATA-883 is OPEN

Ralf Handl (SAP): Mike: doesn't add burden as it is a term, not a CSDL construct

Mike Pizzo: I move we approve ODATA-883 as proposed

Hubert Heijkers: I second

Ralf Handl (SAP): ODATA-883 is resolved as proposed

Ralf Handl (SAP): 6.ODATA-884 Add term ErrorCodes to describe possible codes in error messages (public comment c201510e00019)

Ralf Handl (SAP): Align with term defined in ODATA-859, e.g. "code" instead of "ErrorCode"

Ralf Handl (SAP): Could be applied to entity sets, singletons, action/function imports, actions/functions

Ralf Handl (SAP): <Annotation Term=Core.ErrorCodes Qualifier=Update></Annotation>

<Annotation Term=Core.ErrorCodes Qualifier=Delete></Annotation>

<Annotation Term=Core.ErrorCodes Qualifier=Create></Annotation>

Mike Pizzo: From discussion:

Mike Pizzo: -Swagger returns HTTP status codes; should we align? Perhaps nest OData error codes under HTTP status codes?

 -Could be applied to entityset, singleton, function, or action.

 -Consider aligning with new inline messages defined in ODATA-859

 -Clarify that this was non-limiting. Intended use is for generating API documentation

 -Can specify via qualifier what http methods each set of possible error codes apply to, i.e.:

     <Annotation Term="Core.ErrorCodes" Qualifier="Delete"></Annotation>

     <Annotation Term="Core.ErrorCodes" Qualifier="Create"></Annotation>

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

a.Thursday July 28, 2016 during 8-10am PT?

Ralf Handl (SAP): Meeting after next:

Ralf Handl (SAP): August 11th for four hours

Ralf Handl (SAP): Decide next week whether to meet on August 4th for two hours

Ralf Handl (SAP): August 18th two hours

Ralf Handl (SAP): September 8th two hours

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

Ralf Handl (SAP): Meeting is adjourned

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Handl, Ralf
Sent: Donnerstag, 21. Juli 2016 14:59
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting on 2016-07-21

Here [1] is a draft agenda for the OData TC (Technical Committee) meeting scheduled on Thursday July 21, 2016 during 6-10am PDT (15: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 [6:00am PT]

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

2. Approve agenda [6:05am PT]

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

a. Minutes from July 14, 2016 TC meeting: https://www.oasis-open.org/committees/download.php/58508/odata-meeting-137_on-20160714-minutes.html

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

a. Action items due

i. None

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

a. Issues for V4.01_WD01 in New or Open state

i. Ripe for resolution

1. ODATA-923 $expand for $metadata to include referenced schemas

ii. OData Protocol

1. ODATA-919 Specify the result type for each operation based on operator types

2. ODATA-942 How should headers applied to a batch affect statements within a batch

iii. Annotations

1. ODATA-571 Add annotation for properties that are (not) part of the default selection if no $select is specified

2. ODATA-735 Enhance the CSDL for instance annotations

3. ODATA-811 Define propagation and (partial) overriding of annotations

4. ODATA-859 Define term, semantics for inserting error information into a (mostly) successful response

5. ODATA-883 Validation Vocabulary: add MultipleOf term

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

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

8. ODATA-960 Absolute paths in annotations, e.g. capabilities depending on properties of a singleton

iv. New Query Capabilities

1. ODATA-614 Allow $expand, $select, ... with POST/PATCH/PUT in combination with return=representation to specify the response shape

2. ODATA-827 introduce $compute query option

3. ODATA-933 Allow using instance annotations in $filter

4. ODATA-954 Key-As-Segment for multi-part keys

v. Set Operations

1. ODATA-836 Allow applying actions to a filtered collection of entities

vi. Enumerations

1. ODATA-849 Add possibility for enumeration types to "extend" another enumeration type

2. ODATA-494 Define inheritance for enumeration types

3. ODATA-874 Allow Edm.String as underlying type for enumeration types

vii. OData CSDL

1. ODATA-618 Allow using term names in positions that allow type names

2. ODATA-929 Nullable facet should default to false for collection types, rather than being unspecified

3. ODATA-674 Specify navigation property binding combined with containment *

4. ODATA-935 Allow singletons to be members of an entity set

5. ODATA-959 Allow path in an edm:key to also use a primitive property of a non null-able navigation property (recursively) of the entity type.

viii. OData JSON Format

1. ODATA-868 Describe format for In-Stream errors

2. ODATA-557 Allow exponential notation for Edm.Decimal

ix. Interfaces

1. ODATA-619 Attach action and function signatures to terms, i.e. make a term definition an interface definition

6. Next meeting [9:50am PT]

a. Thursday July 28, 2016 during 8-10am PT?

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

[2] References

· Conference call details: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/56760/TC%20meeting%20dial-in%20details.htm

· Chat room: http://webconf.soaphub.org/conf/room/odatatc

[3] Timeline

· https://www.oasis-open.org/committees/document.php?document_id=56024&wg_abbrev=odata

odata message