- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Sat, 23 May 2020 18:44:29 +0000
- To: public-hydra-logs@w3.org
I like the idea of having SHACL on board - I was among those suggesting it in last years. We just need to move carefully - removing the `rdfs:range` is a breaking change and we need to make it as least _breaking_ as possible. I also find it a bit surprising to modify `hydra:expects` - I though we've already made a modification allowing to have a `hydra:resource` so everything can be _expected_ (including raw resources). I'd look rather at `hydra:property` or `hydra:supportedClass` so these can accept SHACL constructs. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/214#issuecomment-633115251 using your GitHub account
Received on Saturday, 23 May 2020 18:44:30 UTC