[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-482) Allow inlining stream properties and media resources
[ https://issues.oasis-open.org/browse/ODATA-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59619#comment-59619 ] Matthew Borges commented on ODATA-482: -------------------------------------- Another approach instead of using base-64 encoding that we can consider is to return a multi-part mixed response when media streams/Edm.Stream properties are "expanded". I have also had requests for some of our products to provide a way to filter which media streams/Edm.Stream properties are actually "expanded". This can also be done with a generalized expand and a nested $filter or by adding a new system query option with similar syntax to $expand that allows a nested $filter. > 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: [Proposed] > Reporter: Ralf Handl > Fix For: V4.1_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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]