Re: The Linked Data Event Streams specification

Hi Pieter,

We've successfully been using a profile of the Activity Streams
specification for this, documented here:
   https://iiif.io/api/discovery/0.9/#status-of-this-document.

To your three points:
* The collection is the set of distinct entities that are the object of the
activities in the stream.
* They are digital entities, so you can download them
* And the activities are typed as Create, Update, Delete, Add, Remove so
you can process them.

The algorithm at [1] shows how a consumer would keep in sync, based on the
stream.

It's not exactly the same use case perhaps, but I think it's worth
reconsidering what extensions might be needed to AS to make it work rather
than starting from scratch.

Hope that helps,

Rob

1: https://iiif.io/api/discovery/0.9/#activity-streams-processing-algorithm


On Mon, Mar 15, 2021 at 3:40 PM Pieter Colpaert <pieter.colpaert@ugent.be>
wrote:

> Dearest public LOD mailing list,
>
> I was looking for a specification, a bit like RSS, that would allow me
> to tell potential data consumers that:
>
>   - I’m maintaining a collection of members adhering to a certain shape,
>
>   - that they they can find and download all of the members, and
>
>   - that I want them to stay in sync with the latest changes.
>
> As I did not find a solution in for example LDP, Hydra or Activity
> Streams 2, I made my own. You can find the Linked Data Event Streams
> (LDES) specification over here: https://w3id.org/ldes/specification. It
> does not do much: it just defined an event stream as a collection of an
> ever-growing collection of objects that never change (“version objects”).
>
> It is based on the TREE specification
> (https://w3id.org/tree/specification) which in its turn allows more than
> simple one-dimensional paging. It allows to make your collection
> searchable using qualified links to following pages (or tree:Nodes).
> This means you can for example geospatially tile your LDES [1] or expose
> a file-based substring index [2]. Of course, you can also just load the
> LDES in a triple store and make sure your copy always stays in sync with
> the authoritative data source. TREE also foresees compatibility with
> hypermedia specs and collection designs in LDP, Hydra, Activity Streams
> 2, Shape Trees and Triple Pattern Fragments. Over the coming months we
> are planing to publish some governmental base registries with this
> specification.
>
> Are there any other specs LDES should be compatible to?
>
> Kind regards,
>
> Pieter
>
> P.S. Tomorrow I’m speaking at this online event called ENDORSE about
> this specification and the ideas behind it. More info:
> https://op.europa.eu/en/web/endorse/programme
>
> [1] We last year published about a geospatial fragmentation in this
> paper: https://hdelva.be/articles/geospatial-linked-connections/
>
> [2] Check out an autocompletion demo on top of a TREE collection
> fragmented by substring here:
> https://treecg.github.io/treemunica_typeahead_demo/ - I can send a
> preprint of a paper we wrote about this if interested.
>
> --
> https://pietercolpaert.be/#me
>
>
>

-- 
Rob Sanderson
Director for Cultural Heritage Metadata
Yale University