- From: Asbjørn Ulsberg via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 May 2020 19:56:24 +0000
- To: public-hydra-logs@w3.org
> I never aimed to control that. I just have to put all the ideas to extreme situations in order to find out (or at least to get a hint of) how the spec behaves before we modify the spec. Ok, fair enough. > > The profiles just extend Hydra Core > > It is still an idea - let's not be hasty in assuming profiles does exist in hydra as it is now. No, profiles exist regardless of what Hydra decides to do in this space. Officially embraced profiles may not exist without the Hydra CG's seal of approval, but profiles (just like XML namespaces, RDF terms or anything else based on a URI) can be created by anyone. > > so a client can always fall back to Hydra Core > > This is my aim - it is still possible to commit an unrecoverable mistake on the design stage which could render that very fallback impossible. I want to avoid situation when there are several hydra dialects so no client can talk to more than one with same base. That is only possible to a certain degree, though. We are shooting for much more than the moon if we think we can make everything fallback gracefully. > > so a client can always fall back to Hydra Core > > This will often be not an option? If the client finds and operation which `expects` some SHACL Shape and it does not understand SHACL, how would you "fall back to Hydra Core"? Excellent point. This goes a bit back to the content negotiation bit again. There will be situations where a server and client can't find an agreeable format in which to communicate here, just as it exists on the web at large. Some clients don't understand PDF and some servers have no way to translate it into something a client actually understands. That's as applicable to Hydra (although not the PDF bit, perhaps) as it is to a text terminal browsing a website of legal documents. > If the client does not understand a profile, it will not be able to perform operations described using that profile. There is not much more to it, is there? I was thinking that a lot of the vocabulary in Hydra Core will allow a client to interoperate with the API without understanding every part about the API. Like a browser that only understands CSS level 1 may be able to render color, fonts, borders, but very little layout and everything will most likely look pretty horrible. It should still work, though. Agreed? -- GitHub Notification of comment by asbjornu Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/216#issuecomment-635562834 using your GitHub account
Received on Thursday, 28 May 2020 19:56:26 UTC