Skip to content
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

Extend license restriction with branch #4

Open
nicholascar opened this issue Apr 17, 2018 · 3 comments
Open

Extend license restriction with branch #4

nicholascar opened this issue Apr 17, 2018 · 3 comments
Assignees

Comments

@nicholascar
Copy link
Collaborator

nicholascar commented Apr 17, 2018

Is it possible to implement in SHACL such an instance-specific restriction branch condition test:

IF Dataset stored in EUDM system
THEN license must be as per current restriction (in .../license/ register, with 1+ permissions)
ELSE //Dataset in EUDM catalogue but stored elsewhere
THEN no license allowed to be present

This is due to Adam stating this is the logic of the licenses he's been asked to adhere to as CSIRO legal want to make no license claims for data stored elsewhere in case we characterise the license information incorrectly.

@nicholascar nicholascar changed the title Extend the license restriction Extend license restriction with branch Apr 17, 2018
@dr-shorthair
Copy link

That is related to the SPIN CONSTRUCT ops that I was able to successfully implement in https://w3c.github.io/sdw/proposals/ssn-extensions/ but haven't managed to get working in SHACL

@nicholascar
Copy link
Collaborator Author

This raises the issue of how a Implementation Resource Description could be mixed, rather than having a single resource with a conformsTo to SHACL or SPIN.

I think this is modeled by having, in this case, two ImplResDescs, conformsTo SHACL and the other SPIN, each with the resourceRole "Partial Set of Constraints for a Profile" from the Roles vocab.

That way, push SHACL as far as you can but use SPIN if you can't!

@dr-shorthair
Copy link

Of course, licenses are associated primarily with Distributions ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants