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-1290) Can an etag value of "*" be used in If-Match to force update?

Michael Pizzo created ODATA-1290:

             Summary: Can an etag value of "*" be used in If-Match to force update?
                 Key: ODATA-1290
                 URL: https://issues.oasis-open.org/browse/ODATA-1290
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: JSON Format, Protocol
    Affects Versions: V4.0_OS
         Environment: Proposed
            Reporter: Evan Ireland
             Fix For: V4.01_CS02

[http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Data_Modification] states: Use of ETags for Avoiding Update Conflicts
 If an ETag value is specified in an If-Match or If-None-Match header of a Data Modification Request or Action Request, the operation MUST only be invoked if the if-match or if-none-match condition is satisfied.

The ETag value specified in the if-match or if-none-match request header may be obtained from an ETag header of a response for an individual entity, or may be included for an individual entity in a format-specific manner.

Issue requiring clarification: we carefully need to distinguish between ODataâs meaning of âentity = an instance of an entity type" and HTTPâs meaning of âentity = the thing whose representation is transferredâ. ETags (= entity tags) refer to the HTTP meaning, and thus links/references/relationships are âHTTP entitiesâ that can have their own ETags.

Also clarify:
 * Can a "HTTP entity" / "link entity" identified by {{xxx/$ref}} have an ETag?
 * Is the ETag of a "link entity" logically independent of the ETags of the linked OData entities at either end?
 * If {{xxx}} is a collection resource, can the references returned by {{GET xxx/$ref}} contain {{@odata.etag}} control information to carry the individual ETag of each "link entity"?
 * AreÂ{{EntitySet/$ref}}Âand {{EntitySet(<key>)/$ref}} only accidentally allowed by the ABNF and the prose text in [Protocol 11.2.8:ÂRequesting Entity References|http://docs.oasis-open.org/odata/odata/v4.01/cs01/part1-protocol/odata-v4.01-cs01-part1-protocol.html#sec_RequestingEntityReferences] or are these valid resource paths?

This message was sent by Atlassian JIRA

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