Linked Open Research Cloud

• A notification’s payload MUST be serialized as either HTML+RDFa, JSON-LD, or Turtle, and use text/html or application/xhtml+xml, application/ld+json, text/turtle media types respectively in the HTTP Content-Type header.
• A notification MUST use a CC0 1.0 Universal license.

In this section the data shapes for the following notifications are provided:

In addition to the required data shapes, notifications can include anything else that may help with its reuse and the discovery of the resources it refers to. This does not mean that the body of the referred resources should be copied here.

Article data shape

MUST include:

<>
  a as:Announce ;
  as:updated "2017-09-05T21:11:58.611Z"^^xsd:dateTime ;
  schema:license <https://creativecommons.org/publicdomain/zero/1.0/> ;
  as:object <https://csarven.ca/linked-research-decentralised-web> .

<https://csarven.ca/linked-research-decentralised-web>
  a schema:ScholarlyArticle .

• The subject URI of the as:Announce is not explicitly declared (<>) because eventually it will be parsed as the notification’s URL.
• A valid xsd:dateTime is expected for as:updated.
• CC0 1.0 Universal license is expected.
• The value of as:object is the primary object of the announce, ie. the article.
• A class along the lines of schema:ScholarlyArticle, sioc:Post, foaf:Document, biblio:Paper, bibo:Document, as:Article.

SHOULD include:

<>
  as:actor <https://csarven.ca/#i> .

<https://csarven.ca/linked-research-decentralised-web>
  schema:license <https://creativecommons.org/licenses/by/4.0/> .

• as:actor is the URI of the agent that sent the notification.
• URI of an open/free culture license on the article is expected.

Note

The property for the license would normally match that of what is in article, hence it is not enforced here. Senders may want to use eg. schema:license, dcterms:license, dcterms:rights, cc:license, doap:license.

Annotation data shape

MUST include:

<>
  a as:Announce ;
  as:updated "2017-09-05T21:11:58.611Z"^^xsd:dateTime ;
  schema:license <https://creativecommons.org/publicdomain/zero/1.0/> ;
  as:object <http://example.org/annotation> .
  as:target <http://example.net/article#introduction> .

<http://example.org/annotation>
  a oa:Annotation ;
  oa:motivatedBy oa:assessing .

• The subject URI of the as:Announce is not explicitly declared (<>) because eventually it will be parsed as the notification’s URL.
• A valid xsd:dateTime is expected for as:updated.
• CC0 1.0 Universal license is expected.
• The value of as:object is the primary object of the announce, ie. the annotation.
• The value of as:target is the target of the announce, ie. the annotated object.
• oa:Annotation to indicate that the primary object is an annotation.
• oa:motivatedBy for the motivation of the annotation eg. assessment, a peer review.

SHOULD include:

<>
  as:actor <https://csarven.ca/#i> .
<http://example.org/annotation>
  schema:license <https://creativecommons.org/licenses/by/4.0/> .

• as:actor is the URI of the agent that sent the notification.
• URI of an open/free culture license on the annotation is expected.

Note

The property for the license would normally match that of what is in the article, hence it is not enforced here. Senders may want to use eg. schema:license, dcterms:license, dcterms:rights, cc:license, doap:license.

Citation data shape

MUST include:

<http://example.org/article#argument>
  cito:citesAsEvidence <http://example.net/observation#results> .

• Inherit article data shape’s MUSTs with the exception that the citing entity, eg. http://example.org/article#argument can be an instance of any class.
• The citing entity cites the cited entity in a specific or general way eg. cito:citesAsEvidence, schema:citation.

Note

In order to foster better discovery, senders may want to use terms from the Citation Typing Ontology (CiTO) or schema.org’s citation property. Alternative citation properties are only permitted if they are mentioned in this section.

SHOULD include:

• Inherit article data shape’s SHOULDs.

Notifications can be sent to LORC’s Inbox in different ways:

• A typical LDN sender discovers the inbox of a target resource, eg. this article, so that the inbox URL is not hardcoded in sender’s application. There are conforming LDN sender applications which you can use to send notifications, or you are welcome to use your own.
• Sending notifications directly into this article’s inbox (see the object of the ldp:inbox relation) is still welcome. For example, using curl it can be sent with curl -i -X POST -H'Content-Type: text/html' https://linkedresearch.org/inbox/linkedresearch.org/cloud/ --data-raw 'Replace this with your HTML+RDFa payload'. If the response is HTTP/1.1 201 Created you are good to go. The HTTP Location header value is where the notification can be dereferenced from. See more examples at Call for Linked Research and use LORC’s Inbox; https://linkedresearch.org/inbox/linkedresearch.org/cloud/, for the request URL.
• If you are using tools like dokieli, notifications can be sent to LORC with the click of a button. To send a notification about the article, use the Share feature (from menu) and enter https://linkedresearch.org/cloud in the To field. Annotations and citations are soon to be automatic.