- From: Thomas Francart <thomas.francart@sparna.fr>
- Date: Fri, 7 Jun 2024 12:31:12 +0200
- To: Public Shacl W3C <public-shacl@w3.org>
- Cc: public-json-ld-wg@w3.org
- Message-ID: <CAPugn7UYCCrgE34bypwPk6jBYdpHaJ7kJaAi+ojeZQ7aepsM7Q@mail.gmail.com>
Hello SHACL & JSON-LD lovers I have SHACL specs. I also have APIs that return JSON-LD. The JSON-LD is built from RDF using a manually maintained context + JSON-LD framing specs. My question is how I could bridge my SHACL with my JSON-LD context + framing, to have a completely model-driven architecture. In other words can I generate the context + framing from the SHACL (probably using some extra annotations). Generating a default context from the SHACL is relatively easy [1]. My question is on the framing part, specifically on the hierarchical structure of the JSON. How can I indicate in the SHACL model : 1. which shapes are the roots of the JSON-LD structure ? 2. which properties use embedding in the JSON-LD structure ? ("@embed": "@always") and which should be simply references to URIs ? The ability to specify the (or a) hierarchical view of my graph structure could be useful, even for an RDF/XML serialization, or an HTML rendering of a dataset. Any ideas or pointers on this ? Cheers Thomas [1] : https://shacl-play.sparna.fr/play/context#documentation - a simplistic JSON-LD context derivation from a SHACL spec. -- *Thomas Francart* -* SPARNA* Web de *données* | Architecture de l'*information* | Accès aux *connaissances* blog : blog.sparna.fr, site : sparna.fr, linkedin : fr.linkedin.com/in/thomasfrancart tel : +33 (0)6.71.11.25.97, skype : francartthomas
Received on Friday, 7 June 2024 10:31:28 UTC