[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-659) ATOM format spec doesn't say if atom:content is optional in request payload
[ https://issues.oasis-open.org/browse/ODATA-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66716#comment-66716 ] Michael Pizzo commented on ODATA-659: ------------------------------------- Deferred due to inactivity on Atom format 2017-6-29. > ATOM format spec doesn't say if atom:content is optional in request payload > --------------------------------------------------------------------------- > > Key: ODATA-659 > URL: https://issues.oasis-open.org/browse/ODATA-659 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Improvement > Components: ATOM Format > Affects Versions: V4.0_CS02 > Reporter: Evan Ireland > Priority: Minor > > ATOM format spec section 10.2 "Element atom:content" does not indicate if the element can be omitted in client-to-server requests. > The ATOM syndication spec allows atom:content to be optional, perhaps we should be clear about that too. > (Having the element included in request payload seems to offer no value, as the server should know a retrieval URL, and if the client wanted to set or change the MIME type of a media entity they need to do it with the HTTP Content-Type header anyway). > Also, if the client does include atom:content, and they set the "type" attribute, is there any expectation that the server should take note of it? (Considering that the client would be expected to set the Content-Type header in POST/PUT). -- 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]