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

hydra:Link should be an ObjectProperty #193

Closed
tpluscode opened this issue May 12, 2019 · 3 comments
Closed

hydra:Link should be an ObjectProperty #193

tpluscode opened this issue May 12, 2019 · 3 comments

Comments

@tpluscode
Copy link
Contributor

I notice that hydra:Link is defined as a Property.

I does not make sense that a link triple has a literal object. I think that hydra:Link should be changed so that it's an ObjectProperty.

@alien-mcl
Copy link
Member

There are no terms in hydra's RDF representation that are using OWL (excluding the ontology itself).
I don't see any benefits from using owl:ObjectProperty. Still, we could add a @type: "@id" to the hydra's context that can be referenced by other - it should work fine for JSON-LD

@angelo-v
Copy link

I am with @alien-mcl Let's not introduce OWL if it's not there yet. I do not see us gaining much using this here.

I do not understand where you would put @type: "@id"?

@tpluscode
Copy link
Contributor Author

Ok, thanks guys. I forgot that those terms are not RDFS.

About "@type": "@id", it will help simplify JSON structure but if the server is using other serialisation format then it does not shield them from pushing literal accidentally where a URI is expected.

FYI, I created hypermedia-app/hydra-validator#8 to add this to the analyser.

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

3 participants