Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-898

Note the different sets of properties to be expected within atom:content

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Deferred
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: V4.0_CSD03
    • Fix Version/s: None
    • Component/s: ATOM Format
    • Labels:
      None
    • Proposal:
      Hide

      In 6.5 Element atom:content:

      Remove the “the” from the “the properties” in the first sentence, and add: An entity in a payload may be a complete entity, a projected entity (see System Query Option $select [OData-Protocol]), or a partial entity update (see Update an Entity in [OData-Protocol]).

      Show
      In 6.5 Element atom:content: Remove the “the” from the “the properties” in the first sentence, and add: An entity in a payload may be a complete entity, a projected entity (see System Query Option $select [OData-Protocol] ), or a partial entity update (see Update an Entity in [OData-Protocol] ).

      Description

      The JSON format spec describes three scenarios: An entity in a payload may be a complete entity, a projected entity (see System Query Option $select [OData-Protocol]), or a partial entity update (see Update an Entity in [OData-Protocol]). For symmetry reasons, the ATOM Format Spec should make a similar statement.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              gerald.krause1 Gerald Krause
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: