11:51:01 RRSAgent has joined #data-shapes 11:51:06 logging to https://www.w3.org/2025/06/02-data-shapes-irc 11:51:06 Zakim has joined #data-shapes 11:51:41 I have made the request to generate https://www.w3.org/2025/06/02-data-shapes-minutes.html TallTed 11:52:24 meeting: Data Shapes Working Group teleconference 11:52:24 agenda: https://github.com/w3c/data-shapes/raw/refs/heads/agenda/admin/agenda-2025-06-02.md 11:53:16 previous meeting: https://www.w3.org/2025/05/26-data-shapes-minutes.html 11:53:16 next meeting: https://www.w3.org/2025/06/09-data-shapes-minutes.html 11:53:37 I have made the request to generate https://www.w3.org/2025/06/02-data-shapes-minutes.html TallTed 11:55:00 scribe: __TBD__ 11:55:02 gkellogg has joined #data-shapes 11:57:19 agendabot has joined #data-shapes 11:57:24 simonstey has joined #data-shapes 11:57:32 clear agenda 11:57:32 agenda+ ... 11:57:32 agenda+ ... 11:57:32 agenda+ [Support for RDF 1.2 triple terms (without asserted triple)](https://github.com/w3c/data-shapes/issues/379): What should be part of core? 11:57:33 agenda+ The minutes can be found [(link to be added)](https://www.w3.org/2025/06/02-data-shapes-minutes.html) 11:57:40 AndyS has joined #data-shapes 11:58:09 I have made the request to generate https://www.w3.org/2025/06/02-data-shapes-minutes.html TallTed 11:58:15 HolgerK has joined #data-shapes 11:58:48 elianaP has joined #data-shapes 12:01:19 David has joined #data-shapes 12:01:29 scribe+ 12:02:09 bergos has joined #data-shapes 12:02:21 present+ 12:02:33 ajnelson-nist has joined #data-shapes 12:02:38 elianaP: Some attendance in this slot 12:02:42 present+ 12:02:49 present+ 12:02:50 .. two points in the agenda 12:02:55 present+ 12:03:05 bergos: RDF 1.2 12:03:31 ... with and without associated asserted triple for a triple term 12:03:40 ... wantign to make people aware of this 12:04:10 s/wantign/wanting/ 12:04:22 ... I need some input 12:04:29 present+ 12:04:32 present+ 12:05:02 https://github.com/w3c/data-shapes/issues/379 12:05:12 q+ 12:05:53 tallted: RDF 1.2. introduces triple term <<(:s :p :o )>> 12:06:17 ... It is not a triple in the graph (i.e. it is not a member of the set of triples) 12:06:27 q+ 12:06:29 nicholascar has joined #data-shapes 12:06:38 ... e.g. "joe said <<( :s :p :o )>>" 12:06:53 ack TallTed 12:07:24 ajnelson-nist Is there a property for an asserted triple? 12:07:26 q+ 12:08:04 q+ 12:08:10 ... I can see a UC for is for either in the base graph or inferred? 12:08:29 ack me 12:08:32 ack ajnelson-nist 12:09:49 A "fact", being a triple in the graph, is asserted. A "triple term", not being a triple in the graph, is not asserted. 12:11:02 simonstey: we need to clarify how SHACL deals with triple term where the triple is not asserted 12:11:12 q+ 12:11:26 ack simonstey 12:11:45 ... how to validate the triple term 12:11:48 q- 12:12:04 labra1 has joined #data-shapes 12:12:47 labra2 has joined #data-shapes 12:13:10 bergos: a triple term in the object position as an RDF term. 12:13:21 gkellogg has joined #data-shapes 12:13:31 present+ 12:13:44 ... we can have a description of a triple in a another graph e.g. "I disagree with" 12:14:00 ... or a change log for deletion of a triple. 12:14:15 ack bergos 12:14:36 ... should we deal with triples not asserted 12:15:21 ... we have reifiers _:r rdf:reifies <<(:s :p :o)>> . 12:15:41 .. do we need target for triple terms? with or without further restrictions? 12:16:01 s/.. d/... do/ 12:16:08 note that reifiers (identifiers of reified triples) are not necessarily blank nodes; they can be URI/IRI/URL (whatever is the current catchall) 12:16:58 ... ignoring everything not asserted will not work. 12:16:58 labra2 has left #data-shapes 12:17:28 elianaP: uses case for looking inside triple term 12:17:43 bergos: question is how to do this. 12:17:56 ... use a node expression? 12:18:04 ... new target? 12:19:15 q? 12:19:28 q+ 12:20:09 scribe: simonstey 12:20:13 scribe+ 12:20:26 s/scribe: simonstey// 12:21:33 AndyS: Need to address Alex's point about inference - that's separate from triple terms 12:21:48 ... How you treat inferences isn't particular to triple terms. Whether triples asserted by inference or other means is different mechanism 12:21:54 mgberg has joined #data-shapes 12:22:51 ... Triple terms mostly appear as objects of RDF reification statements 12:23:08 ... The subject gives you a resource to talk about this use of the triple term; Sometimes called an "occurrence" - you can make comments about it 12:23:18 ... Can reuse same triple term with different RDF reification IRIs for different comments 12:23:30 ... Allows talking about different times you've seen this triple term without mixing them up 12:23:40 ... For finding them, RDF reification provides navigation method 12:24:56 ... bergos touched on working backwards from triple term to access internal structure 12:25:14 ... Triple terms create nesting concept - triples as terms within graph; Non-asserted triple terms might need recursive target application 12:25:31 ... Need nesting operation like target that works within constraints; Example: find triple terms, then constrain paths to those with specific subjects 12:25:43 q+ 12:25:48 ack me 12:25:49 Note that "RDF*" and "RDF-star" are old names for preliminary drafts of what will ship as "RDF 1.2". Best not to use the old names, to avoid future confusion. 12:26:21 scribe+ 12:26:21 q+ 12:26:43 q- 12:27:06 nick: should support somethin in SHACL core as it is part of RDF 1.2 12:27:25 ajnelson-nist: is property shape adequate for the task? 12:27:42 ... what about a "triple term part"? 12:27:47 q+ 12:27:53 ack ajnelson-nist 12:27:58 ... Statement: SHACL should handle RDF triple terms in core without node expressions, Triple terms are part of RDF language now - we should cover basic handling, Need special convenience functions like Andy suggested, Core should handle: follow path -> hit triple pattern -> access subject/predicate/object, Should work whether triple terms are 12:27:58 asserted or not 12:28:08 scribe- 12:28:24 SUBJECT(<<(:s :p :o)>>) --> :s 12:29:53 ack me 12:30:01 nick: in triples, step "get subject" then keep pathing. 12:30:19 ... "in" and "out" operator 12:32:16 ... are there UC for this from RDF 1.2 WG? 12:33:09 ... how settled is the design from RDF 1.2? 12:33:33 TallTed: not set in stone but in (baked) clay 12:33:56 ... WG extended for 2 years 12:35:06 ... deal with errata, triple terms, focus (1) easier to talk about treiple not asserted and (2) syntax for talk about the triple and assert it 12:35:08 q+ 12:35:33 ... reduce the user burden in expected common pattern 12:35:58 ... classical reification seem as clunky and hard to use. 12:37:18 ack bergos 12:37:49 bergos: homwwork needed. Path in, and also how to validate. 12:38:03 q+ 12:38:51 s/treiple not asserted and (2) syntax for talk about the triple and assert/a triple without asserting it; and (2) syntax for talking about the triple and simultaneously asserting/ 12:40:50 ack me 12:41:23 q+ 12:41:25 ack ajnelson-nist 12:41:33 q+ 12:42:20 https://www.w3.org/TR/sparql12-query/#func-triple-terms 12:45:14 q+ 12:45:25 ack me 12:46:41 I think that's a reasonable example, simonstey. 12:46:51 ack bergos 12:47:03 begos: moving forward 12:47:19 ... I can make some proposals 12:47:37 ... need feedback and discussion 12:48:36 ... on #379 12:49:35 s/begos:/bergos: 12:49:37 q? 12:49:44 ack mgberg 12:50:30 https://www.w3.org/TR/rdf12-concepts/#dfn-classicize 12:50:31 mgberg: RDF 1.2 transformation to non-triple term form ("classicise", "unstar") 12:50:48 q+ 12:51:08 q+ 12:51:18 ... RDF 1.2 triple terms in an RDF 1.1 graph 12:51:48 ajnelson-nist: sounds like a SHACL profile 12:51:53 ack ajnelson-nist 12:51:58 ack me 12:54:43 q+ 12:54:48 ackme 12:54:51 ack me 12:55:48 ajnelson-nist: RDF 1.2 data with a RDF 1.1 triple store 12:58:15 ack me 13:01:04 I have made the request to generate https://www.w3.org/2025/06/02-data-shapes-minutes.html TallTed 13:01:54 chair: elianaP 13:02:17 s/scribe: __TBD__// 13:02:22 I have made the request to generate https://www.w3.org/2025/06/02-data-shapes-minutes.html TallTed 13:02:39 present+ 13:02:50 I have made the request to generate https://www.w3.org/2025/06/02-data-shapes-minutes.html TallTed 13:04:17 s/ackme// 13:05:23 s/ajnelson-nist Is/ajnelson-nist: Is/ 13:07:00 s/asserted or not/... asserted or not/ 13:07:44 s|SUBJECT(<<(: s :p :o)>>) --> :s|`SUBJECT(<<(: s :p :o)>>) --> :s`| 13:07:55 I have made the request to generate https://www.w3.org/2025/06/02-data-shapes-minutes.html TallTed 13:09:40 s/SUBJECT(<<(: s :p :o)>>) --> :s/... SUBJECT(<<(: s :p :o)>>) --> :s/ 13:09:57 I have made the request to generate https://www.w3.org/2025/06/02-data-shapes-minutes.html TallTed 13:10:49 Zakim, bye 13:10:49 leaving. As of this point the attendees have been bergos, ajnelson-nist, elianaP, caribou, David, AndyS, HolgerK, TallTed 13:10:49 Zakim has left #data-shapes 13:10:54 RRSAgent, bye 13:10:54 I see no action items