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

Open
rhiaro opened this Issue Dec 15, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@rhiaro
Collaborator

rhiaro commented Dec 15, 2015

Examples:

  • Paper v2 is derived from paper v1 + rebuttal + reviewer feedback
  • Sequential chapters
  • Paper is a follow-up from a proposal

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).

@csarven csarven added the UI label Dec 15, 2015

@rhiaro

This comment has been minimized.

Show comment
Hide comment
@rhiaro

rhiaro Apr 27, 2016

Collaborator

And add derivedFrom provenance to all articles generated via Save As

Collaborator

rhiaro commented Apr 27, 2016

And add derivedFrom provenance to all articles generated via Save As

@csarven

This comment has been minimized.

Show comment
Hide comment
@csarven

csarven May 10, 2016

Member

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.

Member

csarven commented May 10, 2016

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.

@hvdsomp

This comment has been minimized.

Show comment
Hide comment
@hvdsomp

hvdsomp May 10, 2016

Thanks for putting this comment in, Sarven. A few things:

  • I am not sure that what you are trying to achieve with PROV-O etc is what Robust Links wants to achieve. Robust Links is about papers linking to "web-at-large" resources. And about the fact that these resources evolve in two ways: they disappear (link rot) and their content changes when compared to when they were linked to (content drift). Robust Links is about providing a mechanisms to revisit the state of the referenced/linked resource as it was when it was referenced. It works, indeed, by means of HTML5 data- attributes and leverages the Memento protocol and associated infrastructure to find a temporally appropriate resource version in web archives, resource versioning systems, etc.
  • I think what you want to achieve using PROV-O is more along the lines of what is described at Resource Versioning and Memento. That is a very lightweight, REST/HATEOS approach to expose and access temporal versions of resources.
  • The data- attributes we use for Robust Links are processed using utterly simple RobustLinks JavaScript embedded in the page that includes the data- link decorations. I don't consider this any more special processing than would be required to deal with eg PROV-O, schema.org, ...

hvdsomp commented May 10, 2016

Thanks for putting this comment in, Sarven. A few things:

  • I am not sure that what you are trying to achieve with PROV-O etc is what Robust Links wants to achieve. Robust Links is about papers linking to "web-at-large" resources. And about the fact that these resources evolve in two ways: they disappear (link rot) and their content changes when compared to when they were linked to (content drift). Robust Links is about providing a mechanisms to revisit the state of the referenced/linked resource as it was when it was referenced. It works, indeed, by means of HTML5 data- attributes and leverages the Memento protocol and associated infrastructure to find a temporally appropriate resource version in web archives, resource versioning systems, etc.
  • I think what you want to achieve using PROV-O is more along the lines of what is described at Resource Versioning and Memento. That is a very lightweight, REST/HATEOS approach to expose and access temporal versions of resources.
  • The data- attributes we use for Robust Links are processed using utterly simple RobustLinks JavaScript embedded in the page that includes the data- link decorations. I don't consider this any more special processing than would be required to deal with eg PROV-O, schema.org, ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment