ATOM format spec doesn't say if atom:content is optional in request payload

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor
    • None
    • Affects Version/s: V4.0_CS02
    • Component/s: ATOM Format
    • None
    • Hide

      Allow request payload to omit atom:content for media entities.

      Specify whether the server must, should, should not, or must not take note of the type attribute if the request payload does include atom:content.

      Show
      Allow request payload to omit atom:content for media entities. Specify whether the server must, should, should not, or must not take note of the type attribute if the request payload does include atom:content.

      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).

            Assignee:
            Unassigned
            Reporter:
            evan.ireland.2
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: