Meeting minutes
Data Shapes telecon 2025-05-26
New readme
Nick: please look at the new readme, it has been updated to better reflect our work
Meeting times
Nick: 2PM CEST proposed instead of 9PM
(no objections)
Decision: Trial 2PM CEST
PR 335 Profiles doc & auto-publishing??
SimonStey: may be an issue without consensus, depending on the contents
Nick: Will approve the shell document. We can vote for the FPWD and then move it to auto-publishing. Applies for profiles and UI documents.
Usage of SHACL in the TREE CG
<bergos> Tree spec: https://
<bergos> proposal to switch to shapes in tree cg: TREEcg/
<simonstey> GeoSHACL: https://
bergos: no specific action point for TreeCG, just informing the group
GeoSHACL
<bergos> Shape Topologies specification: https://
bergos: if more people are interested, we might consider getting involved
… This is about constraints you can add to your shape
Nick: GeoSPARQL already contains shapes
… might serve as a starting point for this. These 43 shapes are generic.
<nicholascar> Here is the GeoSPARQL 1.1 validator in SHACL: https://
Nick: SHACL shapes using GeoSPARQL should work fine as long as the latter is enabled at the specific endpoint.
<simonstey> maybe relevant as well opengeospatial/
bergos: Does any SHACL engine provide this kind of capability out of the box? Would this be able to run without a SPARQL endpoint?
Nick: For the shapes likely to be written by people, a spatial index (therefore geoSPARQL) would be necessary.
<bergos> JS library for geo functions: https://
bergos: is anyone in touch with the people working on these projects?
<simonstey> https://