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: [OASIS Issue Tracker] (ODATA-988) Produce lightweight JSON CSDL and separately define Swagger/OAI generation

     [ https://issues.oasis-open.org/browse/ODATA-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-988:

Clean OData-to-OpenAPI Mapping: https://www.oasis-open.org/committees/download.php/59301/odata-openapi-v1.0-wd01-2016-11-07.docx 

OData CSDL JSON will be based on the OpenUI5 OData V4 Metadata JSON Format, https://openui5.hana.ondemand.com/#docs/guide/87aac894a40640f89920d7b2a414499b.html

  was:Clean OData-to-OpenAPI Mapping: https://www.oasis-open.org/committees/download.php/59301/odata-openapi-v1.0-wd01-2016-11-07.docx 

> Produce lightweight JSON CSDL and separately define Swagger/OAI generation
> --------------------------------------------------------------------------
>                 Key: ODATA-988
>                 URL: https://issues.oasis-open.org/browse/ODATA-988
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL JSON 
>    Affects Versions: V4.01_WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.01_WD01
> For the past year we have investigated defining a JSON representation of metadata based on JSON Schema and, more recently, Swagger.  Because this was to serve as a JSON alternate to XML for describing the service it had to have full fidelity with the XML representation.
> JSON Schema was defined as a validation language and lacks many of the core concepts necessary for defining a service model, such as inheritance, relationships, identity, etc. While JSON Schema itself is extensible, the desire to align with Swagger further restricted how we could define OData extensions.
> The current draft for a Swagger/JSON Schema aligned metadata representation is a compromise both from a Swagger/JSON Schema perspective as well as from an OData perspective. Limitations in JSON Schema and Swagger make trying to describe OData concepts through extensions cumbersome and verbose for OData consumers. The added extensions also make it verbose for JSON Schema/Swagger tools and community.
> OAI is itself investigating relaxing its reliance on JSON Schema, allowing other suitable formats to be plugged in based on supported payload formats.

This message was sent by Atlassian JIRA

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