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

Declare OData object/concept name for tombstone before its usage in Result Maintenance and ATOM format describing sections inside ODQP proposal pages 6 and later

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V4.0_WD01
    • Fix Version/s: V4.0_WD01
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      [Closed]

      Description

      Inside the current revision of the proposal for an OData Delta Query Protocol i.e. [OData Delta Query Protocol Design 2012-12-19.docx](https://www.oasis-open.org/committees/download.php/47755/OData%20Delta%20Query%20Protocol%20Design%202012-12-19.docx) the term tombstone should IMO better be introduced before its first appearance on page 6 (result maintenance and atom format describing sections).

      I suggest to do this inside the section "Delta Responses" on pages 3 or 4 since it is simply a "deleted-link" with a cooler name, right? ... which is part of the response and not the request.

      Update:
      Old proposal was to "Define the term tombstone (virtual entity handle for deleted entities) before using it."
      Following the feedback in a comment by Mike it is now proposed to replace instead (as addressed in upcoming revision).

        Attachments

          Activity

          sdrees Stefan Drees (Inactive) created issue -
          sdrees Stefan Drees (Inactive) made changes -
          Field Original Value New Value
          Summary Name OData object/concept name for tombstone before its usage in Result Maintenance and ATOM format describing sections inside ODQP proposal pages 6 and later Declare OData object/concept name for tombstone before its usage in Result Maintenance and ATOM format describing sections inside ODQP proposal pages 6 and later
          sdrees Stefan Drees (Inactive) made changes -
          Proposal Define the term tombstone (virtual entity handle for deleted entities) before using it. Remove the use of "tombstone" and consistently use "deleted entry" to not introduce a new concept just explaining a wording variation.
          Description Inside the current revision of the proposal for an OData Delta Query Protocol i.e. [OData Delta Query Protocol Design 2012-12-19.docx](https://www.oasis-open.org/committees/download.php/47755/OData%20Delta%20Query%20Protocol%20Design%202012-12-19.docx) the term tombstone should IMO better be introduced before its first appearance on page 6 (result maintenance and atom format describing sections).

          I suggest to do this inside the section "Delta Responses" on pages 3 or 4 since it is simply a "deleted-link" with a cooler name, right? ... which is part of the response and not the request.
          Inside the current revision of the proposal for an OData Delta Query Protocol i.e. [OData Delta Query Protocol Design 2012-12-19.docx](https://www.oasis-open.org/committees/download.php/47755/OData%20Delta%20Query%20Protocol%20Design%202012-12-19.docx) the term tombstone should IMO better be introduced before its first appearance on page 6 (result maintenance and atom format describing sections).

          I suggest to do this inside the section "Delta Responses" on pages 3 or 4 since it is simply a "deleted-link" with a cooler name, right? ... which is part of the response and not the request.

          Update:
          Old proposal was to "Define the term tombstone (virtual entity handle for deleted entities) before using it."
          Following the feedback in a comment by Mike it is now proposed to replace instead (as addressed in upcoming revision).
          mikep Michael Pizzo (Inactive) made changes -
          Proposal Remove the use of "tombstone" and consistently use "deleted entry" to not introduce a new concept just explaining a wording variation. Remove the use of "tombstone" and consistently use "deleted entry" to not introduce a new concept just explaining a wording variation.
          Changes applied as proposed: Rewritten as suggested in version 1.3: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47996/OData%20Delta%20Query%20Protocol%20Design%202013-1-23.docx
          Environment [Proposed]
          sdrees Stefan Drees (Inactive) made changes -
          ralfhandl Ralf Handl made changes -
          Component/s OData Protocol v1.0 [ 10267 ]
          ralfhandl Ralf Handl made changes -
          Environment [Proposed] [Closed]
          Status Closed [ 6 ] Open [ 1 ]
          ralfhandl Ralf Handl made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          ralfhandl Ralf Handl made changes -
          Status Resolved [ 5 ] Applied [ 10002 ]
          ralfhandl Ralf Handl made changes -
          Status Applied [ 10002 ] Closed [ 6 ]

            People

            • Assignee:
              mikep Michael Pizzo (Inactive)
              Reporter:
              sdrees Stefan Drees (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: