- From: Thomas Hoppe <thomas.hoppe@n-fuse.de>
- Date: Fri, 11 Oct 2013 12:19:42 +0200
- To: public-hydra@w3.org
- Message-ID: <5257D0BE.3050209@n-fuse.de>
Hello,
here is some more feedback and questions:
1.) I have been working with the spec now for a while and I first I
could not
really use the figure "The Hydra core vocabulary" in a sensible manner
but after having understood the concepts it is very useful as a shore
reference.
2.) In the SPEC the "supportedClasses" property defines a range
"hydra:Class".
I wounder whether it is sensible to set a classes resource like this:
"supportedProperties": "https://api.ex.com/classes/"
which would dereference to a collection like this:
{
"@context": "http://purl.org/hydra/core/context.jsonld",
"@id": "https://api.ex.com/classes/",
"@type": "Collection",
"members": [
{
"@id": "person"
},
{
"@id": "user"
},
...
]
}
A hydra collection is also a hydra:Class according to the spec (although
not explicitly stated in the figure),
so syntactically this should be correct but what about the semantics?
The reason for doing this is that I would like to have the supported
classes being proper API resources as well.
3.) I really don't get the point about the "entrypoint" property.
What is the semantics behind it?
So far I consider it useless as it does not contribute to the URI
resolution (which was the only thing I could think of) --
everything required for this is already specified here [1] I think.
[1] http://json-ld.org/spec/latest/json-ld/#base-iri
Greets, Thomas
Received on Friday, 11 October 2013 10:20:08 UTC