From Shapes to Shapes: Inferring SHACL Shapes for Results of SPARQL CONSTRUCT Queries (Extended Version)
<|reference_start|>From Shapes to Shapes: Inferring SHACL Shapes for Results of SPARQL CONSTRUCT Queries (Extended Version): SPARQL CONSTRUCT queries allow for the specification of data processing pipelines that transform given input graphs into new output graphs. It is now common to constrain graphs through SHACL shapes allowing users to understand which data they can expect and which not. However, it becomes challenging to understand what graph data can be expected at the end of a data processing pipeline without knowing the particular input data: Shape constraints on the input graph may affect the output graph, but may no longer apply literally, and new shapes may be imposed by the query template. In this paper, we study the derivation of shape constraints that hold on all possible output graphs of a given SPARQL CONSTRUCT query. We assume that the SPARQL CONSTRUCT query is fixed, e.g., being part of a program, whereas the input graphs adhere to input shape constraints but may otherwise vary over time and, thus, are mostly unknown. We study a fragment of SPARQL CONSTRUCT queries (SCCQ) and a fragment of SHACL (Simple SHACL). We formally define the problem of deriving the most restrictive set of Simple SHACL shapes that constrain the results from evaluating a SCCQ over any input graph restricted by a given set of Simple SHACL shapes. We propose and implement an algorithm that statically analyses input SHACL shapes and CONSTRUCT queries and prove its soundness and complexity.<|reference_end|>
@article{seifer2024from,
    title={From Shapes to Shapes: Inferring SHACL Shapes for Results of SPARQL
  CONSTRUCT Queries (Extended Version)},
    author={Philipp Seifer, Daniel Hern'andez, Ralf L"ammel, Steffen Staab},
    journal={WWW '24: Proceedings of the ACM Web Conference 2024. ACM, 2024,
  pp. 2064-2074},
    year={2024},
    doi={10.1145/3589334.3645550},
    archivePrefix={arXiv},
    eprint={2402.08509},
    primaryClass={cs.DB cs.AI cs.LO}
}