- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 May 2020 15:04:55 +0000
- To: public-hydra-logs@w3.org
> I'm not even sure Hydra should provide its own MVP schema language out of the box, or simply define that as out of scope for the Core specification and delegate it to one of possibly many extension specifications. I was just thinking that indeed right now. I did hint above that anything we reference in the Core spec should be implemented by a generic client. But we also cannot have a client implement all possible schema options. > I'm not even sure Hydra should provide its own MVP schema language out of the box Right... It hardly makes sense to maintain a built-in model (`hydra:Class` et.al.) if we know that it is a wasted effort on a sub-par solution which is likely not enough for any serious application. > it would be great if Hydra Core allowed extension points that could be implemented by SHACL, OWL, JSON Schema, Relax NG, XSD or any other schema mechanism. The vocabulary is already open enough to allow anything to be used with `hydra:expects`. Might continue the discussion of template mappings (which I consider forms-lite) to also be not limited to `hydra` terms and we'd be almost at the finish line. -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/214#issuecomment-633613541 using your GitHub account
Received on Monday, 25 May 2020 15:04:57 UTC