Glossary #101
Description
As I said through the chat in the last meeting, I am preparing a glossary with some LDES spec terms. I finished a preliminary version of this glossary, but not all terms are defined, as I could not find their definitions in the spec. Also, I think we should probably polish up some of the current definitions for clarity and consistency. Following, I present the current terms of this glossary alphabetically ordered, with comments after the // characters.
Focus node
Once the node has been fully parsed, a client MUST make a list of all member IRIs matching <ES> tree:member ?m with ES being the IRI of the LDES. Each match of this pattern is called a focus node.
// comment: I think it would help to have this definition written as “A focus node is …”.
Immutable node
A node is considered immutable when re-fetching it will not result in new members.
LDES client
A piece of software used by a consumer that accepts the URL to an entry point and returns a stream of members of the corresponding LDES. A client MUST take an IRI as the only required argument.
// comment: I replaced ldes:EventStream by LDES because we are referring to an instance of ldes:EventStream, not the class.
Linked Data Event Stream (LDES) // comment: or just event stream?
A collection of members that cannot be updated or removed once they are published. An append-only collection.
Instance of ldes:EventStream , with ldes:EventStream rdfs:subClassOf tree:Collection .
// comment: is an event stream the same as a data stream? If yes, for consistency and ease of understanding, should we just use “event stream”?
Member
A set of RDF quads.
// comment: what’s the relationship between members and nodes/pages?
Node
Instance of tree:Node . A page in the search tree. The same as Page.
// comment: what is the composition of a page / node? What is its relation to a member?
Page
Instance of tree:Node .
// comment: what is the composition of a page / node? What is its relation to a member?
Retention policy
Indicates in what way a specific view will not be able to provide a complete history of the LDES to the consumer.
Root node
The first page of the structure.
// comment: which structure is this? Is it the search tree? Do we call it a view?
Search tree
One complete invocation of the client’s traversal logic, visiting all nodes that are relevant given the current state. During this synchronization run it emits the newly found members.
// comment: who emits? The client? Is emitting a synonym of publishing?
Subsequent node
One complete invocation of the client’s traversal logic, visiting all nodes that are relevant given the current state. During this synchronization run it emits the newly found members.
// comment: “it” refers to the client, right? Also, should “this” (synchronization) be replaced by “a” (synchronization)?
Terms left to be defined: Consumer, Entity, LDES server, Version.