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

Remove rdfs:range from components-pipeline #100

Open
Robsteranium opened this issue Jan 15, 2019 · 0 comments
Open

Remove rdfs:range from components-pipeline #100

Robsteranium opened this issue Jan 15, 2019 · 0 comments

Comments

@Robsteranium
Copy link
Contributor

The use of rdfs:range and the classize transformation for describing components was taken from the sns-graft pipeline where we all apply a class to the codes as part of a single loading pipeline.

I had originally hoped this would support validation, but I have since learned that rdfs:range is actually used to make inferences, not to validate constraints. In other words:

given the tbox:
dim:age rdfs:range class:Age
and abox with (invalid data):
obs1 dim:age code:Male
inference will give you (false, but consistent data):
code:Male a class:Age

I now think we should validate integrity constraints by another means (see #97 for more).

We should, therefore, remove the rdfs:range statements and classize function etc.

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

1 participant