10:28:41 RRSAgent has joined #data-shapes 10:28:46 logging to https://www.w3.org/2026/01/14-data-shapes-irc 10:28:55 zakim, this is SHACL Rules TF 10:28:55 got it, AndyS 10:29:12 agenda: https://www.w3.org/events/meetings/a5aa03f6-bc98-4ae6-b6e5-67d91d99bece/20260113T103000/#agenda 10:29:13 AndyS, sorry, I did not recognize any agenda in https://www.w3.org/events/meetings/a5aa03f6-bc98-4ae6-b6e5-67d91d99bece/20260113T103000/#agenda 10:29:50 simonstey has joined #data-shapes 10:31:48 AndyS has joined #data-shapes 10:32:22 zakim, start meeting 10:32:22 RRSAgent, make logs Public 10:32:24 please title this meeting ("meeting: ..."), AndyS 10:32:36 meeting: SHACL Rules TF 10:32:39 DavidHabgood has joined #data-shapes 10:32:58 I have made the request to generate https://www.w3.org/2026/01/14-data-shapes-minutes.html AndyS 10:33:09 present+ 10:33:21 present+ 10:33:46 Oggy has joined #data-shapes 10:33:59 scribe+ 10:34:00 Livio has joined #data-shapes 10:34:02 present+ 10:34:18 present+ Livio 10:34:23 present+ Oggy 10:34:39 present? 10:34:44 Robert has joined #data-shapes 10:35:07 present+ Robert 10:35:56 Agenda: scheduling for future meetings; whether to still talk to Derta re. n3; work items for document esp. syntax variants 10:35:56 DavidHabgood, sorry, could not get scheduling for future meetings; whether to still talk to Derta re. n3; work items for document esp. syntax variants (code 400). 10:36:36 Andy: agenda for today is: scheduling for future meetings; whether to still talk to Derta re. n3; work items for document esp. syntax variants 10:36:36 s/Derta/Doethe/ 10:38:01 timeslot: Wednesday is best for everyone, at current time 10:30 UTC 10:39:25 AndyS: do we still want meeting with Doethe, scheduling across timezones can be difficult. Worth coming up with wording around differences, e.g. logic system w/ rules vs. datalog 10:39:56 https://w3c.github.io/N3/spec/ 10:40:08 and https://w3c.github.io/N3/spec/semantics.html 10:41:30 Andy: will try to schedule a slot on Wednesday, if not Tuesday 10:43:36 Livio: some items still unclear, e.g. aggregates 10:44:51 ... would be good to clarify difference w/ n3 10:45:22 AndyS: need to be careful on difference in writing for standard vs academic paper; standard to be normative 10:46:09 ... also have options e.g. w3c notes, or adding to github discussions as means to include other information, comparisons 10:46:38 q+ 10:46:48 ... suggest focus on defining SHACL rules, and see whether a comparison is required, can review comments for input 10:47:40 q- 10:47:59 simonstey: will be comments on comparisons to n3, RIF; could go into primer, else expecting comments around reinventing existing 10:48:25 Robert: is it worth justifying decisions in the spec a bit 10:48:48 AndyS: could mention SHACL AF to show the demand for such a spec 10:49:45 simonstey: might be better to focus on justifying decisions rather than comparisons with others 10:50:00 Livio: can't compare against all others 10:50:13 Robert: consider complexity of comparing with other things 10:50:57 AndyS: the other techs show a need/demand; SHACL rules is an attempt to bring it closer to SHACL/SPARQL 10:52:02 s/Doethe/Dörthe/ 10:52:34 https://www.w3.org/DesignIssues/OldNotation3Grammar.html 2001 10:52:43 Oggy: good to understand intent/motivation for spec in addition to the specs as well 10:55:19 Topic: syntax 10:56:05 AndyS: RULE .. WHERE .. , IF .. THEN .., Datalog one with curly brackets. Has to be something to terminate a rule body, otherwise blurs into next rule 10:56:37 ... EBNF strictly, rules must be on one line, char at end of line is a terminator, this is how not run into head of next production 10:57:07 ... would need to do arbitrary lookaheads as can be many rules 10:58:44 Livio: do we also allow backtracking, as in prolog, "goal seek" behaviour 10:59:13 AndyS: not same as backtracking in prolog; no backtracking symbols or notion of "cut" 11:00:12 ... can be an implementation detail. Can do brute force forward chain, query outcome 11:01:13 ... can allow property functions as part of a SPARQL engine doing inference with rules 11:02:57 simonstey: how would the integration work, rules and sparql 11:03:32 AndyS: would work separately, call each other 11:04:07 Robert: graphwise has a current rule language, has some limitations, looking to implement SHACL 1.2 incl. rules 11:04:41 ... use cases where owl reasoning is overkill; completion of KG use cases 11:04:56 ... negation as failure is a useful feature for these cases 11:05:53 AndyS: would the implementation cover/be in RDF4J 11:06:29 Robert: potentially as they're tightly related 11:07:34 [8] Rule ::= Rule1 | Rule2 | Rule3 | Declaration 11:07:34 [9] Rule1 ::= 'RULE' HeadTemplate 'WHERE' BodyPattern 11:07:34 [10] Rule2 ::= 'IF' BodyPattern 'THEN' HeadTemplate 11:07:34 [11] Rule3 ::= HeadTemplate ':-' BodyPattern 11:09:49 Andy: RULE/WHERE and IF/THEN can accommodate people's different conceptual models 11:10:05 ... third datalog syntax :- if any could be the one to remove 11:11:08 Livio: people will likely converge on one format; if to pick one, would pick Rule2 11:12:20 Oggy: is there any impact with having the RDF format for rules 11:14:32 simonstey: doesn't necessarily need to support arbitrary SHACL constructs 11:15:18 AndyS: non single valued functions do not fit in with the current abstract syntax 11:18:13 simonstey: Rule3 syntax it is datalog like but not quite so can be confusing anyway 11:18:43 Robert: Rule3 similar to other syntaxes as well 11:21:05 AndyS: actions on the end of rules, go through one pass of actions, IF THEN could be a good fit for the actions 11:22:31 consensus is 1&2 support different mental models 11:25:09 AndyS: actions are open, like CONSTRUCT, less restrictions, could allow more arbitrary creation of terms in an action 11:28:54 Oggy: old problem of combining constraint language + open world language e.g. OWL; papers on compiling rules into SHACL itself 11:29:45 https://www.w3.org/TR/rif-owl-rl/ 11:30:20 Robert: OWL fragments, has requirements around explicit typing, could use SHACL to check syntax first, then rules on top of this 11:31:06 Oggy: e.g. could complete type hierarchy using rules before doing other operations w/ OWL 11:32:27 https://www.w3.org/TR/shacl12-core/#dfn-shacl-subclass 11:33:06 simonstey: part of historical reason for inclusion of RDFS in SHACL was to accommodate interests from different people 11:34:36 Robert: RDFS subclassing built in can be problematic, is odd that there isn't an equivalent sub property of 11:36:04 eiter 11:36:18 Thomas Eiter 11:36:26 https://informatics.tuwien.ac.at/people/thomas-eiter 11:37:46 Oggy: have a proof of completeness 11:39:06 Livio: entailment discussion, how did it end 11:39:28 AndyS: out of scope for rules, can refer to an entailment regime 11:43:27 I have made the request to generate https://www.w3.org/2026/01/14-data-shapes-minutes.html AndyS 11:44:34 s/Derta/Dörthe/ 11:44:39 I have made the request to generate https://www.w3.org/2026/01/14-data-shapes-minutes.html AndyS 11:45:14 zakim, end meeing 11:45:14 I don't understand 'end meeing', AndyS 11:45:20 zakim, end meeting 11:45:20 As of this point the attendees have been DavidHabgood, AndyS, simonstey, Livio, Oggy, Robert 11:45:22 RRSAgent, please draft minutes 11:45:23 I have made the request to generate https://www.w3.org/2026/01/14-data-shapes-minutes.html Zakim 11:45:28 I am happy to have been of service, AndyS; please remember to excuse RRSAgent. Goodbye 11:45:29 Zakim has left #data-shapes 11:45:40 rrsagent, please leave 11:45:40 I see no action items