COAR Notify: Accept

This pattern is used to acknowledge and accept a request (Offer). This should be interpreted to mean that the target intends to act on the request in some way. It does not imply any kind of outcome beyond this.

Properties

`@context`

The @context must include:

`id`

Notify payloads must describe an AS 2.0 activity. The activity has an id which must be a URI, and the use of URN:UUID is recommended. An HTTP URI may be used instead, but in such cases the URI should resolve to a useful resource.

`inReplyTo`

In this particular example: inReplyTo is specified because this is a response to a previous notification. inReplyTo takes the URI (URN:UUID or HTTP URI) which identifies the activity for which this is a response.

`origin`

The origin describes the system which has sent the notification. The origin has:

An id which is an HTTP URI identifying the sending system
A type which should include the value Service from AS 2.0.
An inbox which is the HTTP URI of the LDN inbox for the origin

`target`

The target describes the system which is intended to receive the notification. The target has:

An id which is an HTTP URI identifying the receiving system
A type which should include the value Service from AS 2.0.
An inbox which is the HTTP URI of the LDN inbox for the target

`type`

The activity has a type with the value Accept

Example JSON-LD Payload

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://purl.org/coar/notify"
  ],
  "id": "urn:uuid:4fb3af44-d4f8-4226-9475-2d09c2d8d9e0",
  "inReplyTo": "urn:uuid:0370c0fb-bb78-4a9b-87f5-bed307a509dd",
  "origin": {
    "id": "https://generic-service.com/system",
    "inbox": "https://generic-service.com/system/inbox/",
    "type": "Service"
  },
  "target": {
    "id": "https://some-organisation.org",
    "inbox": "https://some-organisation.org/inbox/",
    "type": "Organization"
  },
  "type": "Accept"
}

Get raw JSON-LD