- From: Thomas Francart <thomas.francart@sparna.fr>
- Date: Tue, 19 Nov 2024 15:09:59 +0100
- To: Jerven Tjalling Bolleman <jerven.bolleman@sib.swiss>
- Cc: public-shacl@w3.org
- Message-ID: <CAPugn7VhdhdWp9S20Cp1F1X=q-EOjs84y9fQUDw=h-1TFUUpcA@mail.gmail.com>
Le mar. 19 nov. 2024 à 15:23, Jerven Tjalling Bolleman <jerven.bolleman@sib.swiss> a écrit : > Hi All, > > I don't know if Nick's work builds profiles from instance data. > > However, we have been developing void-generator[1] to inspect real data > and generate very detailed void files for SPARQL service descriptions. > One, of many, use cases is that we can generate SHACL from that using > SPARQL construct [2] to translate the VoID description into SHACL shapes > descriptions. Our idea does not work for all datasets (e.g. needs > rdf:type triples). > (we are probably now a bit off-topic) This is close to what we have in SHACL Play with SHACL generation : https://shacl-play.sparna.fr/play/generate#documentation. It generates SHACL by analyzing the structure of the dataset, and complements this by a VOID statistics file (see example at the end). In our case we analyze the statistics *from / after* the SHACL generation, we don't derive the SHACL from the statistics. What I would find useful in this context would be to relate the VOID statistics file not to classes and properties, but to actual shapes (i.e. void:shapePartition instead of void:classPartition). Because the statistics could be computed from shapes with e.g. SPARQL targets. Thomas > > Regards, > Jerven > > > 1: https://github.com/JervenBolleman/void-generator > 2: > > https://github.com/shex-consolidator/void2shapes/blob/main/sparql/uniprot-void-shacl.sparql > > On 11/19/24 15:08, Steve Ray wrote: > > Nick, > > Does your work include the possibly simpler task of building profiles of > > instance data? We are considering that very thing for the QUDT ontology > > vocabularies. > > > > Steve > > > > > > > > > > On Mon, Nov 18, 2024 at 9:03 PM Nicholas Car <nick@kurrawong.ai > > <mailto:nick@kurrawong.ai>> wrote: > > > > Dear SHACL CG, > > > > One of the deliverables of the proposed "Data Shapes WG" [1] is a > > "SHACL 1.2 Profiling" specification. The intention is to "define > > methods for using SHACL to create formal profiles of (RDF) > > standards" and, by extension, define how bundles of SHACL Shapes can > > import / depend on / reuse other SHACL Shapes. > > > > Even before this WG starts, if it does, I need to create SHACL Shape > > collections that pick and choose Shapes from other collections. I > > would like community input here to both get my job done and to start > > working up towards an implementation of this deliverable. > > > > You can see wholescale importation in the ABIS specification [2] but > > not selective importation. > > > > What methods / modelling patterns have you used to import Shapes 1, > > 2 and 4, but not 3 from Shapes Collection A into Collection B? > > > > If this area is of really great interest to you, please consider > > joining the WG too. > > > > Thanks, Nick > > > > > > [1] https://w3c.github.io/shacl/charter-1.2/shacl- > > wg.html#deliverables <https://w3c.github.io/shacl/charter-1.2/shacl- > > wg.html#deliverables> > > [2] https://github.com/AusBIGG/abis/blob/master/validators/ > > abis.ttl#L26-L55 <https://github.com/AusBIGG/abis/blob/master/ > > validators/abis.ttl#L26-L55> > > > > > -- *Thomas Francart* -* SPARN**A* linked *data* | domain *ontologies* | *knowledge* graphs blog : blog.sparna.fr, site : sparna.fr, linkedin : fr.linkedin.com/in/thomasfrancart tel : +33 (0)6.71.11.25.97
Received on Tuesday, 19 November 2024 15:10:15 UTC