- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 May 2020 19:59:27 +0000
- To: public-hydra-logs@w3.org
> I'm actually not afraid of SHACL - it's still an RDF. It doesn't matter if it's RDF. The client needs to understand the profile to understand whatever semantics a given `expects` or anything else in order to create the request message. If it doesn't, then there is now way to fall back. > It should still work, though. Agreed? See above. Yes, some pf the API will work up to a point where the client cannot perform a request described in ways it does no understand 🤷. Surely, it does not mean that the entire API is unusable but YMMV -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/216#issuecomment-635564389 using your GitHub account
Received on Thursday, 28 May 2020 19:59:29 UTC