[OASIS Issue Tracker] (ODATA-482) Allow inlining stream properties and media resources

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

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

Michael Pizzo edited comment on ODATA-482 at 9/24/15 4:10 PM:
--------------------------------------------------------------

Re-using $expand may be a bit messy since the expand options don't apply
Would the request to expand binary be a hint or required?
   --what if service is willing to return some binary values inline but not others?



was (Author: mikep):
Re-using $expand may be a bit messy since the expand options don't apply


> Allow inlining stream properties and media resources
> ----------------------------------------------------
>
>                 Key: ODATA-482
>                 URL: https://issues.oasis-open.org/browse/ODATA-482
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format, OData JSON Format, OData Protocol, OData URL Conventions
>    Affects Versions: V4.0_CS01
>         Environment: New Query Capabilities
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.01_WD01
>
>
> Stream properties are similar to navigation properties as they "defer" content to a separate resource. It would be nice to be able to inline that related content similarly to related entities.
> This could be done by generalizing $expand, by adding a special query option $inline or $include for stream properties, or in $select as proposed in ODATA-10.



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