[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:all-tabpanel ]

Michael Pizzo updated ODATA-482:
--------------------------------

    Proposal: 
1) Allow payloads to contain Base64-encoded streams
    a) GET response payloads
    b) POST/PUT/PATCH requests
    c) Delta payloads
2) Media streams in the payload are named using the name of the property
3) Media-entity stream is represented with a property named "$value"
4) Generalize $expand to also allow stream properties and represent the related content in Base64-encoded form. 

For stream property: GET People(1)?$expand=photo
For media entity: GET Resumes(1)?$expand=$value

Expand=*  =>only navigation properties - streams are not included automatically by * but may be included explicitly.

  was:
Generalize $expand to also allow stream properties and represent the related content in Base64-encoded form. 
Allow $expand=$value for media entities to inline the corresponding media resource in Base64-encoded form as an artificial property, e.g. "$value" or "@odata.media".


> 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
>              Labels: Extension
>             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)