- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Jun 2018 00:17:16 +0000
- To: public-dxwg-wg@w3.org
@azaroth42 "I think this issue is clear that the Profile and schema/validation language are separate resources, and thus profiles can only "link to" those machine processable constraint descriptions. That a profile could then link to many such descriptions, for different formats (JSON-schema, SHACL/ShEx, xml schema / schematron, etc.), thereby resolving Lars' definition that the profile is technology independent." @larsgsvensson " I think we do: even if we can't develop a technology-independent language for defining (implementing) profiles, we can develop one for composing profiles. OK, then let's do it!" this is exactly the motivation for the ProfileDesc vocabulary :-) Please identify where it succeeds or fails to meet these goals and also make sure the Use Cases and Requirements adequately drive this if there is any doubt. -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/162#issuecomment-399282131 using your GitHub account
Received on Friday, 22 June 2018 00:17:19 UTC