[
https://issues.apache.org/jira/browse/OLINGO-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538039#comment-14538039
]
Kevin Ratnasekera commented on OLINGO-567:
------------------------------------------
Hi Ramesh,
Yes, I agree with you on this one with some exceptions. But the part you
extracted is from the odata.metadata=minimal format. (3.1.1 section)
Media entities and stream properties MAY in addition contain the following
annotations:
· odata.mediaEtag: the ETag of the stream, as appropriate
· odata.mediaContentType: the content type of the stream
If you take a look at the following part which is the odata.metadata=full
format. ( 3.1.2 section )
Media entities and stream properties MAY in addition contain the following
annotations:
· odata.mediaReadLink: the link used to read the stream
· odata.mediaEditLink: the link used to edit/update the stream
· odata.mediaEtag: the ETag of the stream, as appropriate
· odata.mediaContentType: the content type of the stream
so here mediaReadLink and mediaEditLink annotations are considered as MAY not
MUST as the previous case. So when considering the two sections, I think all
the media entity related annotations are MAY not MUST ( As it is mentioned in
the spec ), but for the two case there must be a reason why for
odata.metadata=minimal, MAY is used only for the mediaEtag and
MediaContentType, for odata.metadata=full case, MAY is used for additionally
mediaReadLink and mediaEditLink. So as you mentioned in comment, whether
include the mediaEtag, mediaContentType for Media properties and Stream
properties is an decision that a particular framework can make. But this is
true for minimal case. But for the full case I think this desicion can further
include the other media related annotations such mediaReadLink and
mediaEditLink including mediaEtag and mediaContentType.
WDYT? The statement you pointed out,
In addition, odata annotations MUST appear in the payload for cases where
actual values are not the same as the computed values and MAY appear otherwise.
To my knowledge, I think this true for all the annotation not only for media
related ones.
Regards
Kevin
> Support odata.metadata=full on server side serialization
> --------------------------------------------------------
>
> Key: OLINGO-567
> URL: https://issues.apache.org/jira/browse/OLINGO-567
> Project: Olingo
> Issue Type: Improvement
> Components: odata4-server
> Affects Versions: (Java) V4 4.0.0-beta-02
> Reporter: Christian Amend
> Assignee: Christian Amend
> Fix For: (Java) V4 4.0.0
>
> Attachments:
> odata_metadata=full_support_for_V4_4_0_0-beta-02-Version2.patch,
> odata_metadata=full_support_for_V4_4_0_0-beta-02-Version2_examples.txt,
> odata_metadata=full_support_for_V4_4_0_0-beta-02-Version3.patch,
> odata_metadata=full_support_for_V4_4_0_0-beta-02-Version4.patch,
> odata_metadata=full_support_for_V4_4_0_0-beta-02.patch
>
>
> Support odata.metadata=full on server side serialization. Currently we throw
> a not supported exception during serializer creation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
