Introduction of the hydra:extension predicate that should resolve issue #221
Summary
This PR should resolve issue #221 by introducing a new term by which server could announce extensions in use. Additionally, client can express it's preferences regarding those extensions.
More details
While in the issue there was a suggestion of using a hydra:profile term, I decided to use hydra:extension. The word profile introduced was meant to reflect how descriptive logic of OWL changes with different OWL profiles, thus it didn't feel like a correct word to use. Finally, extension feels more generic and does not imply any specific behavior other than something additional to the base Hydra description that client may or may not understand.
Introduction of the
hydra:extension
predicate that should resolve issue #221Summary
This PR should resolve issue #221 by introducing a new term by which server could announce extensions in use. Additionally, client can express it's preferences regarding those extensions.
More details
While in the issue there was a suggestion of using a
hydra:profile
term, I decided to usehydra:extension
. The wordprofile
introduced was meant to reflect how descriptive logic of OWL changes with different OWL profiles, thus it didn't feel like a correct word to use. Finally, extension feels more generic and does not imply any specific behavior other than something additional to the base Hydra description that client may or may not understand.