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

Use "signposting" principles to make resources machine-friendly #860

Open
bryjbrown opened this Issue Jun 25, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@bryjbrown
Member

bryjbrown commented Jun 25, 2018

Title (Goal) Use "signposting" principles to make resources machine-friendly
Primary Actor Web crawlers & citation/annotation management tools
Scope Drupal Module
Level Low
Story As a web crawler or citation/annotation management tool, I want to be able to accurately and consistently discern the PURL and license for a given resource, as well as discern the URLs of any associated objects or files via typed HTTP links, also known as signposting.

This would satisfy the following behaviours from the COAR NGR report:

@dannylamb

This comment has been minimized.

Show comment
Hide comment
@dannylamb

dannylamb Jun 26, 2018

Hey @bryjbrown, I'm assuming PURL is a Permanent URL?

Currently, we have all this except for pointing to the license, but CLAW currently provides signposts for all entity references, so if you modeling things a certain way you could probably get it without any programming.

dannylamb commented Jun 26, 2018

Hey @bryjbrown, I'm assuming PURL is a Permanent URL?

Currently, we have all this except for pointing to the license, but CLAW currently provides signposts for all entity references, so if you modeling things a certain way you could probably get it without any programming.

@bryjbrown

This comment has been minimized.

Show comment
Hide comment
@bryjbrown

bryjbrown Jun 26, 2018

Member

@dannylamb Yep, technically "persistant" URL, but you get the gist. Basically any URL that gets passed to a resolver, so ARKs, DOIs, Handles, etc are all examples of PURLs we'd want to expose via HTTP links.

I figured CLAW already did some of this stuff, I just wanted to make the use cases to show where we overlap with the COAR NGR report. Exposing the license shouldn't be too much work, right?

Member

bryjbrown commented Jun 26, 2018

@dannylamb Yep, technically "persistant" URL, but you get the gist. Basically any URL that gets passed to a resolver, so ARKs, DOIs, Handles, etc are all examples of PURLs we'd want to expose via HTTP links.

I figured CLAW already did some of this stuff, I just wanted to make the use cases to show where we overlap with the COAR NGR report. Exposing the license shouldn't be too much work, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment