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 2016-06-02


    1. > Action items due

                                                    i.     #0035: Identify the right open source license for the OASIS Open Source repositories for vocabularies and libraries (due March 31, 2016)

 

Please find below the proposal for two OASIS OData Open Repositories. Let’s review this and make any corrections. Once the TC approves, the next step is to request OASIS to setup the repos.

 

·        OASIS OData Open Repository for Open API

o   GitHub name

§  odata-openapi or OData-OpenAPI

o   Purpose statement

§  OData (Open Data Protocol) is an OASIS standard that defines best practices for building and consuming RESTful APIs. OData helps you focus on your business logic while building RESTful APIs without having to worry about the approaches to define request and response headers, status codes, HTTP methods, URL conventions, media types, payload formats and query options etc. OData also guides you about tracking changes, defining functions/actions for reusable procedures and sending asynchronous/batch requests etc. Additionally, OData provides facility for extension to fulfill any custom needs of your RESTful APIs.

§  OData RESTful APIs are easy to consume. The OData metadata, a machine-readable description of the data model of the APIs, enables the creation of powerful generic client proxies and tools. Some of them can help you interact with OData even without knowing anything about the protocol.

§  OData RESTful APIs are even easier to consume if they provide an API description based on the OpenAPI Specification, enabling the use of OpenAPI tools.

§  This repository provides tools for producing OpenAPI descriptions for OData services.

o   Description

§  Tools for producing API descriptions for OData services that adhere to the OpenAPI Specification

o   Open source license

§  Apache License v2.0

o   Maintainers

§  Person 1 – Ralf Handl, ralf.hand@sap.com, ralfhandl, SAP SE

§  Person 2 – Mike Pizzo, mikep@microsoft.com, mikepizzo, Microsoft

o   Planned work items

§  XSLT transformation from OData CSDL XML to OpenAPI JSON

§  example XML files

§  example openapi.json files

§  example files for the live odata.org services

·        OASIS OData Open Repository for Vocabularies

o   GitHub name

§  odata-vocabularies or OData-Vocabularies

o   Purpose statement

§  Vocabularies are a powerful extension mechanism for OData services, allowing to annotate service metadata with additional semantic information.

§  This repository contains the most recent copies of the standard OData vocabularies authored by the OASIS OData Technical committee, as well as pre-standard and community vocabularies.

o   Description

§  Standard, pre-standard, and community vocabularies for annotating OData services

o   Open source license

§  Apache License v2.0

o   Maintainers

§  Person 1 – Ralf Handl, ralf.hand@sap.com, ralfhandl, SAP SE

§  Person 2 – Mike Pizzo, mikep@microsoft.com, mikepizzo, Microsoft

o   Planned work items

§  Maintain and evolve existing standard OASIS OData vocabularies

§  Define and evolve Validation vocabulary

§  Define and evolve Service Catalog vocabulary

 

From: odata@lists.oasis-open.org [mailto:odata@lists.oasis-open.org] On Behalf Of Ram Jeyaraman
Sent: June 1, 2016 6:05 PM
To: odata@lists.oasis-open.org
Subject: [odata] Agenda for OData TC meeting 2016-06-02

 

Here [1] is the agenda for the OData TC (Technical Committee) meeting scheduled on Thursday June 2, 2016 during 8-10am Pacific Time. 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:00am]
    1. Self-registration link: https://www.oasis-open.org/apps/org/workgroup/odata/event.php?event_id=41465      

 

  1. Approve agenda [8:05am]

 

  1. Approve minutes from previous meeting(s) [8:10am]
    1. Minutes from May 5, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58201/odata-meeting-informal_on-20160505-minutes.html
    2. Minutes from May 12, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58164/odata-meeting-130_on-20160512-minutes.html
    3. Minutes from May 19, 2016 TC meeting: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/58202/odata-meeting-131_on-20160519-minutes.html

 

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

                                                    i.     #0035: Identify the right open source license for the OASIS Open Source repositories for vocabularies and libraries (due March 31, 2016)

                                                   ii.     #0036: Register the OData- headers and preferences with IANA (due July 31, 2016)

 

  1. V4.0 Errata 3 [8:20am]
    1. Public review comment resolution log

                                                    i.     https://lists.oasis-open.org/archives/odata/201605/msg00033.html

b.      Next step

                                                    i.     Approve Errata 3 docs as Approved Errata

c.      Sample approval motions (needs Full Majority vote)

                                                    i.     I move that the TC approve OData version 4.0 Errata 03 Working Draft 02 and all associated artifacts packaged together in <link to ZIP file> as an Approved Errata and make it available with OData version 4.0 OASIS Standard. Further, I confirm that the errata corrections do not constitute Substantive Changes to the Standard.

                                                   ii.     I move that the TC approve OData JSON Format version 4.0 Errata 03 Working Draft 02 and all associated artifacts packaged together in <link to ZIP file> as an Approved Errata and make it available with OData JSON Format version 4.0 OASIS Standard. Further, I confirm that the errata corrections do not constitute Substantive Changes to the Standard.

 

  1. V4.01 issues [8:40am]

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

                                                     i.          OData protocol

1.      ODATA-937: Consider making odata- prefix optional in headers, preference values, format parameters [reopen and update resolution]

2.      ODATA-941: Attempting to modify a property with read-only permissions should fail

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

4.      ODATA-846: Add version 4.01 (resolve as we get close to CSD01)

                                                   ii.           Complex Types

1.      ODATA-560 - Allow arbitrary properties in referential constraints

                                                  iii.           Simplified Payload

1.      ODATA-809   Define non-message format for final response of async request

                                                  iv.           Batch

1.      ODATA-541 - Allow the If-Match header to reference the ETag that resulted from an earlier operation in a batch request

                                                   v.          Annotations

1.      ODATA-516 - Add super type Edm.AnyPath for Edm.PropertyPath, Edm.NavigationPropertyPath, and Edm.AnnotationPath

2.      ODATA-545 - Allow applying Capability terms CountRestrictions, TopSupported, SkipSupported etc. to all resources returning collections

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

4.      ODATA-631 - Allow expressing that a term can be applied any collection and is not restricted to entity sets

5.      ODATA-735 - Enhance the CSDL for instance annotations

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

7.      ODATA-816 - Add Capability term for filter _expression_ restrictions

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

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

10.   ODATA-940: Define a validation term for valid values

                                                  vi.           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-798 - Semantic Key or Alternate Key for entity types

                                                vii.           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

                                               viii.          OData CSDL

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

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

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

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

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

                                                  ix.          JSON Format

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

2.      ODATA-938: In 4.01 decide if we can support invoking actions with no params with no body

                                                   x.          Decimal

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

                                                   ii.          URL Conventions

1.      ODATA-933: Allow using instance annotations in $filter

                                                  iii.          Interfaces

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

2.      ODATA-696: Support "interfaces" for casting entities to multiple different types

                                                  iv.          Set operations

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

 

  1. Data aggregation [9:30am]

a.      Hierarchy discussion

b.      Issues

                                               i.          ODATA-905 Example 67: result row for USA, Sugar missing, Example 68: last total should be 7

                                              ii.          ODATA-904 Example 55: clarify groupby in combination with relationships of instance cardinality zero

                                             iii.          ODATA-909 ABNF for pathPrefix should also allow qualified ComplexTypeName

                                             iv.          ODATA-939: Add example for groupby single-valued navigation property

8.      OData CSDL JSON [9:40am]

a.      Parked issues

                                                    i.     ODATA-906 Consider how to specify an included namespace as a default in JSON CSDL

                                                   ii.     ODATA-890 Specify how to get from a JSON message to a JSON schema for validating this message

                                                  iii.     ODATA-863 Represent Terms similar to Types

 

  1. Next meeting [9:50am]

b.      Thursday June 9, 2016?

 

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

 

[2] References

 

[3] Timeline

 



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