The @context
must include:
id
Notify notifications 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.
type
The activity
has a type
which should include at least the value Announce from AS 2.0.
actor
The activity
should have an actor
describing the party responsible for initiating this activity
. The actor
:
id
which must be an HTTP URI.type
which should be one of: Application, Group, Organization, Person or Service from AS 2.0.context
This activity
has a context
. The context
has:
id
which is the HTTP URI of the "landing page" for the resource.type
.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.inReplyTo
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
This activity
has an object
. The object
has:
id
which is the HTTP URI of the "landing page" for the resource.type
.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.origin
The activity
has an origin
describing the system which has sent the notification. The origin
has:
id
which is an HTTP URI identifying the generic-service.type
which should include the value Service from AS 2.0.inbox
which is the HTTP URI of the LDN inbox for the generic-servicetarget
The activity
has a target
describing the system which is intended to receive the notification. The target
has:
id
which is an HTTP URI identifying the generic-organisation.type
which should include the value Service from AS 2.0.inbox
which is the HTTP URI of the LDN inbox for the generic-organisation{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://purl.org/coar/notify"
],
"actor": {
"id": "https://generic-service.com",
"name": "Generic Service",
"type": "Service"
},
"context": {
"id": "https://some-organisation.org/resource/0021",
"ietf:cite-as": "https://doi.org/10.4598/12123487",
"type": "Document"
},
"id": "urn:uuid:94ecae35-dcfd-4182-8550-22c7164fe23f",
"inReplyTo": "urn:uuid:0370c0fb-bb78-4a9b-87f5-bed307a509dd",
"object": {
"id": "https://generic-service.com/resource/1234",
"ietf:cite-as": "https://doi.org/10.9357/123003",
"type": "Document"
},
"origin": {
"id": "https://generic-service.com/system",
"inbox": "https://generic-service.com/system/inbox/",
"type": "Service"
},
"target": {
"id": "https://some-organisation.org/system",
"inbox": "https://some-organisation.org/system/inbox/",
"type": "Service"
},
"type": "Announce"
}
ID | Scenario | Use-case(s) | Participating Systems |
---|---|---|---|
2 | Author requests review with possible endorsement (via repository) | Peer-review, Endorsement | Repository <-> Overlay Journal |
6 | Author submits to overlay journal using repository to host resource and reviews | Peer-review, Endorsement | Overlay Journal <-> Repository |
2 | Author requests review with possible endorsement (via repository) | Peer-review, Endorsement | Repository <-> Overlay Journal |
5 | Repository requests review (on behalf of corresponding author) | Peer-review | Repository <-> Review Service |
9 | Author requests reviews from review service, via repository | Peer-review | Repository <-> Review Service |
9 | Author requests reviews from review service, via repository | Peer-review | Repository <-> Review Service |