[ https://issues.oasis-open.org/browse/ODATA-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48242#comment-48242 ]
Ralf Handl commented on ODATA-589:
----------------------------------
After talking to JavaScript programmers that would consume the parsed metadata I made the following changes:
- hashes instead of arrays if multi-occurring child elements have a unique key (e.g. Namespace identifies schemas, Name identifies Schema children, Name identifies properties within a structured type, Name identifies function/action parameters)
- lowerCamelCased names for CSDL elements and attributes (e.g. nullable, maxLength): more in sync with mainstream JavaScript naming conventions
- pluralized names for multi-occuring CSDL elements (e.g. entityTypes, properties): more in sync with mainstream JavaScript naming conventions
The links now lead to updated versions of the XSL transformation and example JSON files. In addition there is
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/examples/MetadataService.json
created from
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/examples/MetadataService.edmx
> Add a JSON version of the Metadata document
> -------------------------------------------
>
> Key: ODATA-589
> URL: https://issues.oasis-open.org/browse/ODATA-589
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: New Feature
> Components: OData CSDL
> Affects Versions: V4.1_WD01
> Reporter: Matthew Borges
> Fix For: V4.1_WD01
>
>
> Add a JSON version of the CSDL and metadata document. This seems like a natural feature to support since all other responses (including the metadata service responses) can be formatted using JSON.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
