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] Commented: (ODATA-126) Metadata as an OData service

    [ http://tools.oasis-open.org/issues/browse/ODATA-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33133#action_33133 ] 

Ralf Handl commented on ODATA-126:

The transformation steps needed are:
- Keep edmx:Edmx wrapper element, change xmlns:edmx to new edmx and make Version=4.0"
- Translate edmx:Edmx/edmx:Runtime/edmx:ConceptualModels into edmx:DataServices
- Keep Schema element, change xmlns to new edm, remove all other xmlns:xxx attributes
- Keep EntityType, ComplexType, EnumType, EntityContainer, remove Association (and maybe more)
- Keep NavigationProperty, use Relationship and ToRole to extract Type from corresponding Association/End, using Multiplicity="*" for Collection(...)

Here are two files, one V3 produced with Visual Studio, one V4 transformed manually, to be used for testing an automatic transformation:
- https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/examples/MetadataService/TestV3.edmx
- https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/examples/MetadataService/TestV4.edmx

> 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]