- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 May 2020 11:31:14 +0000
- To: public-hydra-logs@w3.org
>I'm curious about your other ideas. >While I don't think `supportedClass` fits SHACL, >I would like to know what you had in mind for `hydra:property` I was wondering on how to support various ways of how supported data structures could be hinted to the client. Currently `hydra:supportedClass` accepts `hydra:Class`, which is `rdfs:Class` which may raise SHACL shapes to that level. While I personaly see no harm with a SHACL shape being a hydra:Class simultanously, this may be unwanted behavior in some cases (what cases?). I was also thinking on how the client would tell a server on it's preferences regarding data structure description (I've mentioned various ways of describing those in my previous post). Maybe a Prefer header? I'd love to see hydra as a common framework driving API, but I hate seeing several hydra dialects applied here and there so no generic client can talk to all of them. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/214#issuecomment-633526875 using your GitHub account
Received on Monday, 25 May 2020 11:31:16 UTC