[OASIS Issue Tracker] Commented: (ODATA-34) Control verbosity of $metadata response: include annotations or documentation

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

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

Ralf Handl commented on ODATA-34:
---------------------------------

For the new JSON format the OData-IncludeVocabularies header would only be relevant for the "odata=fullmetadata" case, in which case I'd prefer if it would affect the response.

> Control verbosity of $metadata response: include annotations or documentation
> -----------------------------------------------------------------------------
>
>                 Key: ODATA-34
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-34
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>          Components: OData CSDL v1.0, OData Protocol v1.0, OData URL Conventions v1.0
>    Affects Versions: WD01
>            Reporter: Ralf Handl
>             Fix For: WD01
>
>
> Metadata documents may contain Documentation, ValueAnnotation and TypeAnnotation elements that quite increase the size of the document.
> It is desirable for (especially mobile) clients to control the size of the response and include e.g. only annotations of vocabularies the client can understand.
> This may be done via headers (Prefer, Accept?), system query options, or by exposing $metadata as an OData service itself, see ODATA-126:
> GET ~/$metadata/EntityTypes('Model.Person')?$expand=Annotations
> Ideally combined with filtering on expanded entities, see ODATA-32.

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