OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (ODATA-1512) Delta: distinguish "soft-deleted" and "hard-deleted" entities

Ralf Handl created ODATA-1512:

             Summary: Delta: distinguish "soft-deleted" and "hard-deleted" entities
                 Key: ODATA-1512
                 URL: https://issues.oasis-open.org/browse/ODATA-1512
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: Vocabularies
         Environment: Question
            Reporter: Ralf Handl

One of our business object framework would like to only include "soft-deleted" entities ({{@removed:\{reason:"changed"}}}) in standard delta responses, and provide "hard-deleted" entities ({{@removed:\{reason:"deleted"}}}) via a separate call to a bound function.

Is that something the TC wants to allow expressing in the standard Capabilities vocabulary, or is it rather something for an SAP-specific vocabulary?

This message was sent by Atlassian Jira

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]