This pattern is used to indicate that a previously received Notify notification was un-processable for some reason. The reason is given in the summary
property.
@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.
object
The object
describes the resource which is the main focus of this notification.
In this particular example:
id
which is the HTTP URI of the "landing page" for the resource.type
which should include the value AboutPage from schema.org.ietf:cite-as
which contains the persistent HTTP URI (sometimes called the "PID") which is to be used to cite or link to the resource.ietf:item
containing the details of the actual content resource. The ietf:item
has:
id
containing the HTTP URI of the content file for the resource.type
describing the content file.mediaType
which contains the MIME Type of the content file.origin
The origin
describes the system which has sent the notification.
The origin
has:
id
which is an HTTP URI identifying the sending systemtype
which should include the value Service from AS 2.0.inbox
which is the HTTP URI of the LDN inbox for the origin
summary
In this particular example:
The summary
is used to describe the reason (in plain text) that the request could not be processed.
target
The target
describes the system which is intended to receive the notification.
The target
has:
id
which is an HTTP URI identifying the receiving systemtype
which should include the value Service from AS 2.0.inbox
which is the HTTP URI of the LDN inbox for the target
type
The activity
has a type
which should include Flag & coar-notify:UnprocessableNotification
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://purl.org/coar/notify"
],
"id": "urn:uuid:49dae4d9-4a16-4dcf-8ae0-a0cef139254c",
"inReplyTo": "urn:uuid:0370c0fb-bb78-4a9b-87f5-bed307a509dd",
"object": {
"id": "https://research-organisation.org/repository/preprint/201203/421/",
"ietf:cite-as": "https://doi.org/10.5555/12345680",
"ietf:item": {
"id": "https://research-organisation.org/repository/preprint/201203/421/content.pdf",
"mediaType": "application/pdf",
"type": [
"Article",
"sorg:ScholarlyArticle"
]
},
"type": "sorg:AboutPage"
},
"origin": {
"id": "https://some-organisation.org",
"inbox": "https://some-organisation.org/inbox/",
"type": "Organization"
},
"summary": "Unable to process URL: http://www.example.com/broken-url - returns HTTP error 404",
"target": {
"id": "https://generic-service.com/system",
"inbox": "https://generic-service.com/system/inbox/",
"type": "Service"
},
"type": [
"Flag",
"coar-notify:UnprocessableNotification"
]
}
Workflow | System | Participants | Use-case(s) |
---|