Endorsements

Selected people and organizations who have publicly indicated their interest in using SHACL (since October 2016).

• Allotrope Foundation: Allotrope Foundation is an international association of pharmaceutical and biotech companies. SHACL has been selected as the standard by which Allotrope can ensure consistency in the captured data.

• Tim Smith (Procter & Gamble): we believe SHACL will allow us to create a much more robust data architecture, a more fluid and fault tolerant data transformation and integration environment as well as enhancing our user's experience with a more "intelligent" user interface.

• Terry Roach (Capsicum): We are very interested in the SHACL standard making it’s way through this process and becoming endorsed so that we can commit to it in our products.

• Bart van Leeuwen (Netage B.V.): in a recent W3C related conference at least half of the presentations mentioned SHACL / Shapes as a technology they use.

• Dean Allemang (Working Ontologist): In FIBO, we have been looking for a constraint language to help us make definitions that go beyond the capabilities of OWL.

• Jack Hodges (Siemens): In the past 8 months we have embraced the use of SHACL, and in particular SHACL SPARQL constraints, to develop inter-model constraints that the specification doesn't provide templates for. Without SPARQL support within SHACL, I am not convinced that SHACL would have much value for our work.

• Pano Maria (Taxonic): We see a growing need for SHACL at our clients, and are noticing a growing interest in SHACL in the Dutch Linked Data community.

• Stephane Fellah (Image Matters, TTL): I am keen to help building a SHACL shapes repository as open source project for OWL.

• Tim Armstrong: The most interesting part of the comparison to me, though, is that SHACL can be used mainly directly to validate object-oriented data.

• Tony Hammond (Spinger Nature): As an integral part of our data publishing architecture (at various layers – integration, validation and publishing) we are relying on the Shapes Constraint Language (SHACL) for validating RDF graphs

• Sarven Capadisli: there are some tooling e.g., https://github.com/solid/node-solid-server, https://github.com/linkeddata/dokieli that would be interested in using existing SHACL libraries. Linked Data Notifications mentions SHACL as a possibility in which LDN Senders and Receivers may want to incorporate into their tooling/workflow.

• Gregor Wobbe: in light of the anticipated FIBO adoption within the financial industry, I believe SHACL will play a crucial role in the cross-firm data integration by providing a common way to validate a constraint graph against a data graph.

• Paraskevi Zerva: I use shape graphs to declare SHACL property constraints in order to declare the set of mandatory/optional parameters and restrictions associated to the values of a particular property for certain conceptual elements. I use shape graphs as descriptions to enable code generation with regards to visualization/user interface utilities...

• Adam Kimball (Healthwise, Inc): With a technology like SHACL, I can now effectively write unit tests for these transformations. Even better, I can build the constraint as an interface before I even begin to write transformation code.

• Kurt Cagle (Semantical, LLC): I am learning to love SHACL. I had evolved something similar for my own projects, primarily because I’ve usually found the OWL is simply too heavy-weight for applications where your primary goal is to work with business data. It also contains enough of a structure to provide UI hints. SHACL is to XSD as OWL is to DTDs — DTDs are more expressive when dealing with narrative content, but SHACL is more appropriate for doing analytics.

• Ethan Gruber: eventually, would like to incorporate SHACL for expression and validation of models

• Martin Hepp: I think SHACL is very promising for data quality for linked open data & schema.org

• Thomas Francart (Sparna): SHACL will remedy this lack by allowing to express verification constraints on an RDF graph (translated from French).

• Semantic Arts: An exciting new standard is under development at the W3C to add some much needed functionality to OWL.

• Paul Appleby (Pearson): Although not perfect JSON-LD and SHACL makes this platform viable

• Nandana Mihindu: It will be great to have a nice set of open-source Java #SHACL libraries

• Angela Pitts SHACL - the piece of the puzzle we've been looking for - RDF validator. Yay!

• Acando: At the eInnsyn project, a collaborative project between Agency for Public Management and eGovernment (Difi) and the Oslo municipality (Oslo kommune), we have now successfully implemented a SHACL engine and are using SHACL for data validation.

• Mary Parmelee (MITRE): Thank you for introducing SHACL. We are currently testing it for data validation in an analytics service pipeline and we are finding it to be very useful!