Meeting minutes
<TallTed> 07:44:10 <TallTed> agenda: https://
Improved meeting agenda template
nick: slimmed down and better meeting agenda
… explicit agenda points (topics), please put into agenda before meeting
Phase 1 deliverables finalisation timeline
Discussion
nick: Summary on SHACL Core, SHACL SPARQL and Node Expressions
Discussion
<AndyS> https://
HolgerK: added reification and list support
… poll is open for list options
… ready to start the next phase
ajnelson-nist: how difficult to change core?
nicholascar: not until they are published. We can still incrementally update core docs as needed
<Zakim> AndyS, you wanted to ask about CR
mgberg: w3c/
HolgerK: can merge now with 3 approvals
AndyS: checking if we are ready to proceed to CR
HolgerK: let's give us 3 months more, approx 1st of October before freezing
nicholascar: informal notice to wider community for feedback
Phase 2 status update
It is #408 sorry, I will need to fix that up later
nicholascar: SHACL profiling thoughts
… there are some conceptual challenges for this deliverable
… we're going to need some discussion around this to scope it
edmond: SHACL UI processor - work-in-progress
<nicholascar> edmond: I'm getting back into SHACL UI work - a second processor after a year
edmond: principles from DASH
… this is a second system and will address a areas not in the first system
<nicholascar> edmond: going back to first principles of SHACL -> UI components for better coverage
HolgerK: SHACL UI still mostly what's published on data shapes set of docs
bergos: know most of the existing implementors but not sure if they will join or if there are any recent activities around SHACL UI
… SHACL + DASH is currently serving the community's needs
Namespace, and namespace document, for SHACL Rules -- srl:
<AndyS> https://
AndyS: there's a second document with the grammar and the formal model
… RDF syntax round trip (also with SHACLC)
… defining the algorithms
… happy to schedule a session outside this call to discuss in more detail
<TallTed> sr: has at least one known conflict -- https://
<TallTed> srl: has no known conflicts -- https://
<ajnelson-nist> shr: also has no known conflicts, per same resource -- https://
TallTed: namespace preferred prefix
AndyS: might not be realistic to have different namespaces for every facet of SHACL
… conflicts/clashes very likely
… thought it'd be good to partition Rules as a separate namespace, but not sure if other features should follow the same pattern
bergos: concerned with namespace proliferation
… example: rdf vs rdfs
nicholascar: same issue with sosa, ssn, and ssn-ext
nicholascar: please see the poll on whether we should allow list syntax or not
… about a week left
Node Expressions
DHabgood: would be good to schedule in some meetings with the other editors to start on a draft
… see if we can build off of existing docs
Robert: will organise a meeting for this
HolgerK: I would like to join
… can build off existing sections in the docs around Node Expressions
<AndyS> URIs for list node expressions / SPARQL -- https://
AndyS: reference sparql-ns.ttl, will be an output of SPARQL 1.2
ajnelson-nist: are we carrying forward SHACL AF?
… what is still AF and what is core in 1.2?
HolgerK: we are not dropping AF but almost all will be moved over to the 1.2 specs
nicholascar: editors, please meet
… please see the poll
… if you have at least one approval on a PR, please just merge
<TallTed> poll is found via https://