OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (ODATA-1485) Clarify canonical URLs for stream properties

Ralf Handl created ODATA-1485:

             Summary: Clarify canonical URLs for stream properties
                 Key: ODATA-1485
                 URL: https://issues.oasis-open.org/browse/ODATA-1485
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
            Reporter: Ralf Handl

 * It would help if JSON Format 4.5.12 would not simply generically refer to _OData Version 4.01 Part 2: URL Conventions_ but somehow stated that the stream property URL conventions are the same as for other properties. I see that [4.7 Addressing a Property Value|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#sec_AddressingaPropertyValue] actually implicitly makes such a statement but a more explicit statement would still help.
 * Since examples speak more than 1000 words I would most appreciate if in [11.2.4 Requesting Individual Properties|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_RequestingIndividualProperties] or in [11.4.8 Managing Stream Properties|https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_ManagingStreamProperties], an example could be added. In 11.4.8, one could then add one example with the canonical URL and one with a different mediaReadLink.


This message was sent by Atlassian Jira

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]