Comments (3)
To make this work efficiently, I think we would need a way to communicate to the client that the view uses a unidirectional linked list as pagination model between fragments.
If this is the case, the client can keep the last consumed fragment uri and the timestamp of the last processed member as state, and can continue from there on?
from linkeddataeventstreams.
Not convinced a unidirectional fragmentation is needed: the relations however do have to use the ldes:timestampPath as tree:path.
from linkeddataeventstreams.
If we go with this idea of 'profiles', that allow the client to discover how a view can be consumed, we could define the minimal relations that should be present in said profile?
e.g. tree:GreaterThanRelation is required in each fragment?
Having someting with even more simplistic semantics like nextOrderOfArrivalFragment would be nice to have, as in theory a fragment could contain multiple GreaterThanRelation relations?
If we want to keep the itterator logic as simple as possible, being able to have a explicit order beween fragments becomes important.
from linkeddataeventstreams.
Related Issues (20)
- Proposal: further constraining the EventSource view HOT 1
- Clarify MAY on ldes:timestampPath
- Latest state + time retention
- Add and specify support for named graphs HOT 6
- JSON-LD context/frame for the LDES members HOT 2
- Delayed flush strategy profile for views
- Hypermedia URIs should be relative URIs HOT 1
- Support streaming parsing of fragments (profile) HOT 2
- Add an ActivityStreams example in the spec
- New shape backward compatible. HOT 1
- Separating metadata from LDES members HOT 3
- Distributed transactions in LDES HOT 1
- LatestVersionSubset gives wrong impression HOT 1
- Default JSON-LD context HOT 1
- Add note on version objects
- ActivityStreams-based retention policies for removed entities HOT 2
- Consistent graph replication - RDF Dataset Canonicalization HOT 4
- https://tree.linkeddatafragments.org/linked-data-event-streams/ cannot be reached HOT 1
- Polling interval algorithm and extra property called ldes:timeToLive
- Status log of LDES consumers
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from linkeddataeventstreams.