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

Negative statement constraints #88

Open
tombaker opened this issue Dec 6, 2022 · 1 comment
Open

Negative statement constraints #88

tombaker opened this issue Dec 6, 2022 · 1 comment
Labels

Comments

@tombaker
Copy link
Collaborator

tombaker commented Dec 6, 2022

The combination of "mandatory" and "repeatable" does not capture the notion of a statement template that MUST NOT match the data.

For example one might want to specify, in a shape, that there be no statements with predicate ex:star_rating.

This could be done by using min and max for the cardinality of the statement constraint, then setting both as "0".

This seems like an edge case possibly worthy of mention in the Cookbook.

@kcoyle
Copy link
Collaborator

kcoyle commented Dec 7, 2022

I feel like this is getting into validation territory, and can imagine other patterns like "if THIS then not THAT". In the sense of defining your own AP I think it would be unusual to say what it is NOT, but NOT comes up in ingesting data from others or in validating existing metadata. To me this brings up a fundamental question about DCTAP and whether it is intended also as an ingest pattern definition. I think if we go there we get into the weeds, even though we can imagine situations where it might be used that way.

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

No branches or pull requests

2 participants