-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create / display chains of sequential or related documents #41
Comments
And add |
See also http://robustlinks.mementoweb.org/spec/ for whatever is applicable via @hvdsomp . I think we currently cover the use cases there using the PROV-O, schema.org, Web Annotation RDF vocabularies. Aside: I'm not particularly a fan of HTML data attributes as they require special processing, but good to keep this in our radar. |
Thanks for putting this comment in, Sarven. A few things:
|
Hello people from 2015, 2016.. I think the original cases that @rhiaro raised is implemented in dokieli for generally two 'create' operations with @hvdsomp 's suggestion on Memento:
If a resource (URI-R or URI-M) has a timemap relation, clicking on the "Memento" button from the dokieli menu will show a list of resources in the TimeMap resource in which the user can navigate to. Note: the Memento bits are intended to mimic the TimeMap bits of Memento protocol where the client handles the resources. Part of the idea here is to bring this feature to servers that don't support the Memento protocol, but something that would allow clients to still work with resource versioning. Whether a resource is actually immutable is not something that dokieli can ultimately control since the server makes the last call on that. A separate issue is needed for dokieli to work with servers implementing the Memento protocol or implementing the relevant parts of the Fedora spec. The solid-server didn't it implement at the time (pending nodeSolidServer/node-solid-server#478 nodeSolidServer/node-solid-server#612 ) and the Fedora spec was/is still in the works. Certainly a lot more can be fine tuned or extended here but I would consider the current state to be sufficient to close this issue. |
Examples:
These quite specific relations could be displayed differently from replies/annoations in the UI (from both ends of the relation, eg. derived-from and has-derivatives).
The text was updated successfully, but these errors were encountered: