Sander Van Dooren
Sander Van Dooren
@bosd Let's see how it goes...
This looks like a [same origin policy](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy) issue? Perhaps a wildcard DNS entry on the domain serving the HTML could offer a solution? Then use the hierarchy in reverse order...
As an alternative to the current implementation I would suggest to drop the range of tree:shape, and instead define tree:shape as a subproperty of sh:shapesGraph.
- A server should define a default Accept header (e.g. if no accept is defined, return content type Turtle)
This is something we need to look into more in depth. This issue looks at it from an individual node, but I would also like to introduce something on the...
Hmm, I was thinking more to include a hash on each member (version object), that would represent the state of the full represented graph after applying the change: For instance...
Yes, I would see it as metadata of an event, similar like its timestamp. The hash would indicate the state of the graph after applying the member (or members in...
Perhaps we could create a LDES/protobuf serialization?
It seems that ABB has created a JSON-LD context: https://ipdc.vlaanderen.be/ldes.jsonld
I would avoid splitting up streams and the need for distributed transaction as much as possible. If the information is needed together, why not store it together? If we maintain...