[jira] [Commented] (OLINGO-570) Implement OData Json Metadocument Serializer/Parser

["Ramesh Reddy (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OLINGO-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350156#comment-15350156 ] 

Ramesh Reddy commented on OLINGO-570:
-------------------------------------

The best course of action right now is to follow the XSLT transformation that has been provided by the OASIS OData specification for converting the XML metadata format into OData JSON metadata format. This JSON metadata format also is Swagger 2.0 format.

IMO, one concern in putting large effort into developing native JSON serializers for metadata is to Swagger upcoming 3.0 release and changes affecting in the OData specification due to that. 

so, what I am proposing is not a native JSON metadata serializers, but a simple transformation of XML format, obviously this means there will NOT a JSON based parser. 

Now on client side, the user can Swagger java libraries to build their application access. 

any comments?

> Implement OData Json Metadocument Serializer/Parser
> ---------------------------------------------------
>
>                 Key: OLINGO-570
>                 URL: https://issues.apache.org/jira/browse/OLINGO-570
>             Project: Olingo
>          Issue Type: Improvement
>          Components: odata4-client, odata4-server
>    Affects Versions: (Java) V4 4.0.0-beta-02
>            Reporter: Christian Amend
>            Assignee: Ramesh Reddy
>              Labels: gsoc2015, java, mentor, xml
>         Attachments: jsonMeta1.diff, jsonMeta2.diff, jsonMeta3.diff, jsonMeta4.diff, jsonMetaDeserializer1.diff, jsonMetaDeserializer2.diff, jsonMetaDeserializer3.diff, jsonMetaDeserializer4.diff
>
>
> The Olingo project is currently working on implementing the V4 OData specification published by oasis. The current version of the specification only specifies a metadata document in xml format. This can be problematic on android devices where no native xml parser is available. In a newer version of this specification a new metadata format will be specified in Json.
> The goal of this issue would be to implement a serializer which can create a payload based on the new specification. Afterwards the Olingo client library must be able to consume the Json metadata document by implementing a parser.
> This issue could be implemented by a Student who takes part in the GSoC. The metadata document is already available as an xml format which could give a student a very good entry point to learn more about OData and the Olingo library. Learning opportunities would be about Json payload creation as well as parsing of Json payloads. This would also include understanding the latest OData V4 specification. If you are interested comment this issue or write a mail to dev@olingo.apache.org .
> Sources:
> Olingo Website: http://olingo.apache.org/
> OData.org: http://www.odata.org/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)