- From: Hammond, Tony <tony.hammond@springernature.com>
- Date: Tue, 11 Apr 2017 10:28:19 +0100
- To: public-rdf-shapes@w3.org
Of interest to this list, yesterday we published the SHACL shapes we used for publishing the Springer Nature SciGraph datasets: https://github.com/springernature/scigraph/tree/master/shapes Some notes from the README below. The SciGraph Team == We use the Shapes Constraint Language (SHACL) for publishing our RDF datasets. These shapes make use of a fairly simplistic interpretation of the SHACL spec. Basically we maintain one shapes graph per export dataset. We define closed shapes for target classes only, with each shape being namespaced under our domain. These shapes are used primarily for data extraction rather than validation, where SPARQL queries range over the SHACL shapes to build RDF datasets via a CONSTRUCT query type. See the wiki section Classes and Properties for model descriptions. (Note that we use a corresponding – but wider – set of shapes for data validation and restriction on our ETL import workflows.) Some points of note: * These shapes conform to an earlier version of the SHACL spec, ca. September 2016, when we forked the TopBraid SHACL API project. In particular, we make use use of the sh:predicate property, rather than sh:path. * We have not yet defined any modularization techniques so some shapes are repeated more or less verbatim across different shapes graphs (see e.g.shapes:Contribution in articles.ttl and grants.ttl) * We also use shape definitions for our OWL ontology (see ontologies.ttl) and SKOS concept schemes (see subjects.ttl) . ==
Received on Tuesday, 11 April 2017 09:28:54 UTC