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

Add support for dcam:domainIncludes and dcam:rangeIncludes #15

Open
white-gecko opened this issue Mar 29, 2022 · 1 comment
Open

Add support for dcam:domainIncludes and dcam:rangeIncludes #15

white-gecko opened this issue Mar 29, 2022 · 1 comment

Comments

@white-gecko
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The usage of owl:domain and owl:range is involved with sometimes (maybe most of the time) unintended inference. The usage of a more soft property, that suggest the usage of a property in combination with a class might be a better solution.

Describe the solution you'd like
Add support for dcam:domainIncludes (http://purl.org/dc/dcam/domainIncludes) and dcam:rangeIncludes (http://purl.org/dc/dcam/rangeIncludes)

Describe alternatives you've considered
Additionally we could also add support for the following terms:
dcid:domainIncludes (https://datacommons.org/browser/domainIncludes)
dcid:rangeIncludes (https://datacommons.org/browser/rangeIncludes)
schema:domainIncludes (https://schema.org/domainIncludes)
schema:rangeIncludes (https://schema.org/rangeIncludes)

Additional context

See also: https://www.dublincore.org/resources/glossary/domain_and_range_includes/

@VladimirAlexiev
Copy link

VladimirAlexiev commented Sep 13, 2022

@white-gecko 👍 great request!

I've posted this previously to other doc generators:

And related issues to use more metadata props:

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

No branches or pull requests

2 participants