[OASIS Issue Tracker] (ODATA-923) Support subsetting returned metadata

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/ODATA-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65729#comment-65729 ] 

Michael Pizzo commented on ODATA-923:
-------------------------------------

Response would include full descriptions of each type. If the type contains navigation properties or bound operations that were not included in the response, the definition of those navigation properties or bound operations may not be included in the response. Client may have to make an additional request (to the same or different metadata document) to get the description of that (those) type(s). 

This would support describing existing results. You could also ask for individual types. You could even try to ask for types in an included namespace (worst case, you'd get the original (possibly empty) metadata document with (at least) the include to the referenced type).

You could not ask for "this type and the type of all navigation properties of this type" (to a given level).  We could add syntax for that if it became a concern, but wouldn't recommend doing so until we had some scenarios asking for it.


> Support subsetting returned metadata
> ------------------------------------
>
>                 Key: ODATA-923
>                 URL: https://issues.oasis-open.org/browse/ODATA-923
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: CSDL XML
>    Affects Versions: V4.0_ERRATA03
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>             Fix For: V4.01_CSD02
>
>
> After being able to partition large services into smaller ones using cross-service navigation we might want to support requesting multiple of these small files in one request, similar to expanding an entity and including related entities.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)