- From: Holger Knublauch <holger@topquadrant.com>
- Date: Mon, 13 Aug 2018 08:52:22 +1000
- To: public-rdf-shapes@w3.org
- Message-ID: <edcc627f-7291-173a-e88e-076418b973ab@topquadrant.com>
Hi Dominik, on your SHACL question, TopBraid includes the ability to load SHACLC files (including in the TBC Free Edition). This is read-only support, which means that you can import any .shaclc file into other RDF files and they will be turned into SHACL on the fly. As Jose already said, SHACL Compact Syntax did not get published by the WG and I don't know whether it will be continued in the future. I can provide the implementation for anyone interested as we have no plans to continue on this format at this stage. For a notation that most mainstream developers would understand quite easily, I would recommend JSON-LD (see the example in https://www.w3.org/TR/shacl/#shacl-example) - there is a JSON-LD context available at http://shacl.org/context.json. Another option that we are increasingly using is to use GraphQL schema as a compact syntax for SHACL, see https://www.topquadrant.com/graphql/graphql-shacl.html. An example would look like # A user account type User { name: String! age: Int @shape(minInclusive: 18) gender: Gender purchases: [Purchase] } type Purchase { # The internal ID productId: String! @shape(minLength: 8, pattern: "[0-9]+") } enum Gender { FEMALE MALE } It would help us understand your requirements for the background of your question. Regards, Holger On 10/08/2018 10:39 PM, Dominik Tomaszuk wrote: > Dear Colleagues, > > Do you know any tools for transforming: > 1. from SHACL [1] into SHACLC [2] and/or from SHACLC into SHACL]? > 2. from ShExJ [3] (or other RDF syntax e.g. Turtle) into ShExC [3]? > > [1] https://www.w3.org/TR/shacl/ > [2] https://w3c.github.io/shacl/shacl-compact-syntax/ > [3] http://shex.io/shex-semantics/ > > Best regards, >
Received on Sunday, 12 August 2018 23:01:05 UTC