generated from netwerk-digitaal-erfgoed/requirements-template
-
Notifications
You must be signed in to change notification settings - Fork 1
/
implementation.bs
73 lines (55 loc) · 2.43 KB
/
implementation.bs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
<pre class='metadata'>
Title: Artefact Lifecycle Event Log LDES implementation
Shortname: eventlog
Level: 1
Status: LS
URL: https://mellonscholarlycommunication.github.io/spec-eventlog
Editor: Miel Vander Sande, [meemoo - Flemish Institute for Archives](https://meemoo.be), [email protected]
Editor: Patrick Hochstenbach, [IDLab - Ghent University](https://knows.idlab.ugent.be), [email protected]
Editor: Ruben Dedecker, [IDLab - Ghent University](https://knows.idlab.ugent.be), [email protected]
Editor: Jeroen Werbrouck, [IDLab - Ghent University](https://knows.idlab.ugent.be), [email protected]
Abstract: This document specifies an implementation of the Artefact Lifecycle Event Log using a Linked Data Event Stream.
Markup Shorthands: markdown yes
</pre>
Introduction {#implementation}
========================
In this document, we provide implementation examples
Linked Data Event Streams and the Solid Platform {#implementation-solid}
========================
An Event Log is defined as a [Linked Data Event Stream (LDES)](https://semiceu.github.io/LinkedDataEventStreams/eventstreams.html), a collection of immutable objects, each object being described using a set of RDF triples.
<div class="example">
<u><b>/EventLog</b></u>
```
<> a ldes:EventStream ;
tree:shape <EventShape.shacl> ;
tree:member </Events/1>, </Events/2>, ... ;
tree:view <?page=1> .
<#node> a tree:Node ;
tree:relation [
a tree:GreaterThanOrEqualToRelation ;
tree:path dct:issued ;
tree:node </pages/1#node> ;
tree:value "2020-10-10T10:00:00Z"^^xsd:dateTime
] .
```
<hr>
<u><b>/pages/1</b></u>
```
</EventLog> a ldes:EventStream ;
tree:shape <EventShape.shacl> ;
tree:member </Events/3>, </Events/4>, ... ;
<#node> a tree:Node ;
void:subset </EventLog>;
```
</div>
Note: This example shows the [=Artefact Lifecycle Event Log=] as a Linked Data Event Stream, ordered according to the `dct:issued` value of the Events.
<img alt="…" src="images/peer_review_sequence.svg" style="width: 100%">
<img alt="…" src="images/review_aftermath.svg" style="width: 100%">
Spec roadmap {#roadmap}
====================================
## September ## {#september}
1. Work out full implementation details
- target the Solid ecosystem
- using the Event Streams Spec
- update images of control flows (outdated)
2. Better definitions for minimal-requirements (do you need a full Solid implementation?) - low priority