[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-126) Metadata as an OData service
[ http://tools.oasis-open.org/issues/browse/ODATA-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-126:
-----------------------------
Proposal:
Define CSDL schema for CSDL and allow application/atomsvc+xml and application/json as additional representations of ~/$metadata, returning an Atom or JSON service document for accessing the metadata of the service.
~/$metadata/$metadata will return the constant schema for CSDL, and we should end the recursion there.
CSDL: https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/MetadataService.edmx
Diagram: https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/examples/MetadataService/EntityDesignerDiagram.png?op=dl&rev=0&isdir=0
was:
Define CSDL schema for CSDL and allow application/atomsvc+xml and application/json as additional representations of ~/$metadata, returning an Atom or JSON service document for accessing the metadata of the service.
~/$metadata/$metadata will return the constant schema for CSDL, and we should end the recursion there.
Draft of ER model for metadata service: https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/examples/MetadataService/EntityDesignerDiagram.png?op=dl&rev=0&isdir=0
Removed typos
- EntityType and ComplexType inherit from Type, so no Key, Fullname and Name
- Navigation property Schema consistently had wrong type: EntityContainer -> Schema
- NamedEntities not directly related to Schema, only to EntityContainer
- ParameterType was used via NavigationProperty, but is complex type -> Property
- Include/Uri -> Include/Namespace
- Introduced complex type KeyProperty to reflect our new Alias attribute for key properties
- Cleaned up Nullable facet: optionality in XML-CSDL no longer reflected, instead MetadataService will show default value
> Metadata as an OData service
> ----------------------------
>
> Key: ODATA-126
> URL: http://tools.oasis-open.org/issues/browse/ODATA-126
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: New Feature
> Components: OData CSDL, OData Protocol , OData URL Conventions
> Affects Versions: V4.0_WD01
> Environment: [Proposed]
> Reporter: Ralf Handl
> Assignee: Ralf Handl
> Fix For: V4.0_WD01
>
>
> Instead of a monolithic XML metadata document the metadata could be made available as an OData service with a fixed schema:
> Entity types
> - EntitySet
> - EntityType
> - Property
> - ValueAnnotation
> - ...
> Entity sets
> - EntitySets
> - EntityTypes
> - Properties
> - VallueAnnotations
> - ...
> This meta-service could be accessed via a canonical URL, ideally ~/$metadata/ with $format=atom/json or a corresponding Accept header.
> This would allow accessing only parts of the metadata document the client is interested in and simplify parsing for clients: they only need to know how to interpret "normal" OData feed and entity response payloads without needing a separate metadata format.
> It would also conveniently provide a JSON format for metadata.
> Accepted: https://www.oasis-open.org/committees/download.php/48097/odata-meeting-23_on-20130130_31-F2F-minutes.html#odata-126
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]