We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I would like to propose an OWL vocabulary to augment Hydra Core.
First, it could provide OWL constructs describing the model (as an alternative to SHACL (#2))
Second, it could define additional terms to allow basic OWL-based inferencing. Off the top of my head, we could have inverse properties
howl:operationSupportedByClass owl:inverseOf hydra:supportedOperation ; rdfs:domain hydra:Operation ; rdfs:range hydra:Class . howl:operatonSupportedBy owl:inverseOf hydra:operation ; rdfs:domain hydra:Operation ; rdfs:range hydra:Resource . howl:propertySupportedByClass owl:inverseOf hydra:supportedProperty ; rdfs:domain hydra:Operation ; rdfs:range hydra:Class .
This way instances, and terms from external vocabularies could be extended with Hydra affordances without "polluting" their immediate graphs
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I would like to propose an OWL vocabulary to augment Hydra Core.
First, it could provide OWL constructs describing the model (as an alternative to SHACL (#2))
Second, it could define additional terms to allow basic OWL-based inferencing. Off the top of my head, we could have inverse properties
This way instances, and terms from external vocabularies could be extended with Hydra affordances without "polluting" their immediate graphs
The text was updated successfully, but these errors were encountered: