- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 May 2020 19:40:48 +0000
- To: public-hydra-logs@w3.org
To wrap up things, we've got currently 3 areas where SHACL (and possible other vocabs) could be used alongside with hydra: - data structure definition - this should live with hydra side-by-side; hydra comes with `supportedClass` and `supportedProperty` which should point to classes and properties described by SHACL, OWL, RDFs, you name it; I believe slight modification of `supportedClass`'s range should enable those vocabs - expects/returns - I see two ways here: - no other vocab hints and client is opaque when sending/receiving resources - external vocabulary specifications with client doing the validation - I see no point in adding i.e. `sh:ShapeNode` here as the resource being sent will be yet another RDF graph, regardless of the source of it's description - IRI template mapping - I personally see no point in using something else here -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/214#issuecomment-633695947 using your GitHub account
Received on Monday, 25 May 2020 19:40:50 UTC