Page Comparison

...

From the usage scenarios described in Section 2.1, the use cases depicted in Figure 1 have been derived.

Figure 1 - Use cases

The actors of the use case are divided in two types of users, namely, the NanoPub Author and the NanoPub User. While the former interacts with the system for the purpose of annotating an assertion, publishing the assertion or managing the assertions he published, the later consumes the published assertions by means of searching, retrieving and citing the assertions.

...

From the use cases described in the last session, we have decided to split the expected functionality of the system in two separate applications, namely, ORKA and NanoPub Store. ORKA is responsible for providing support to users who want to annotate a triple originated from a graph analysis tool by changing the triple's predicate. The edited triple is then transformed into a nanopublication adding the provenance of the author and keeping the relationship with the original triple. The NanoPub Store is responsible for storing the nanopublications created in the Triple Annotator as well as allowing users to search for stored nanopublications and cite them.

Figure 2 - General architecture of ORKA and NanoPub Store applications

Figure 2 depicts the general architecture of ORKA (yellow) and NanoPub (green) applications. The applications have been divided in the following three main integrated but independent layers:

...

Current:

{
 "subject": "aspirin",        // original triple subject
 "subjectUri": "http://example.com/aspirin",
 "predicate": "treats",       // original triple predicate
 "predicateUri": "http://example.com/treats",
 "object": "smoking",         // original triple object
 "objectUri": "http://example.com/smoking",
 "returnUri": "http://semlab1.liacs.nl:8081/annotator-demo/complete.html",        // return button url
 "returnLabel": "Annotation Demo"
}

Previous:

{
  “subject”: {               // original triple subject
    “label”: “”,
    “uri”: “”
  },
  “predicate”: {    // original triple predicate
    “label”: “”,
    “uri”: “”
  },// return button label
}

Extensions under consideration:

  “object”“referrer_context”: {       // free original triple object
    “label”: “”,
choice of key-value pairs for convenience of the referrer
       “uri”key1: “”
value1,  },
  “referrer”: {     // modelskeys theshould sourcebe application
an RDF predicate
  “label”: “”,    // text of the return button
key2: value2,        “returnTo”: “”, // returnvalues buttonare url
RDF resources or literals
 “version”: “”   // metadata for the nanopub provenance ...
  }
}

Data model 2

[
 {“uri”: “http://example.org/rel#treats”, “label”: “treats”},
 {“uri”: “http://example.org/rel#affects”, “label”: “affects”},
 ...
]