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] Updated: (ODATA-324) Support external metadata references in payload

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

Michael Pizzo updated ODATA-324:

    Environment: [Applied]  (was: [Proposed])
       Assignee: Michael Pizzo

> Support external metadata references in payload
> -----------------------------------------------
>                 Key: ODATA-324
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-324
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ATOM Format , OData JSON Format, OData Protocol 
>    Affects Versions: V4.0_WD01
>         Environment: [Applied]
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>             Fix For: V4.0_WD01
> OData services may link to other external services. Where the target of that link is an entity or collection of entities we use navigation links.
> For cases where the type of the related entity is not known in metadata (either because it is a dynamic navigation property or the type is defined as Edm.EntityType or Collection(Edm.EntityType) in order to avoid referencing other type definitions from $metadata) clients consuming the feed need some way of discovering the type of a particular entity.
> We have two ways of conveying type information; we use odata.metadata to convey the metadata that describes the result, and odata.type to describe the type of a property within the result.
> Today we have only one odata.metadata annotation, at the top level, and we expect all odata.type annotations to be referenced from within that odata.metadata. This doesn't allow individual instances to link to entities in other services without referencing the metadata in their own service document.
> We have a similar requirement where an instance in a feed is a derived type of the base type but that derived type is not defined or referenced by the $metadata of the response.
> We have two (compatible) choices:
> 1) Allow odata.type to contain a full url to a metadata description of the related type, or
> 2) Allow the navigation property (whether present in the payload or not) to be annotated with the odata.metadata annotation.
> For derived types I prefer #1 as we already use odata.type for derived types. 
> For navigation properties I prefer #2 as it is more expressive and allows "rebasing" the root metadata for nested expanded content.

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]