14:59:20 RRSAgent has joined #rdf-star 14:59:24 logging to https://www.w3.org/2024/11/22-rdf-star-irc 14:59:52 thms has joined #rdf-star 14:59:52 zakim, this is RDF-star 14:59:53 got it, AndyS 15:00:01 zakim, this is RDF-star SemanticTF 15:00:01 got it, AndyS 15:00:07 zakim, this is RDF-star SemanticsTF 15:00:07 got it, AndyS 15:00:24 rrsagent, make logs public 15:00:40 gkellogg has joined #rdf-star 15:00:50 present+ 15:01:34 RRSAgent, draft minutes 15:01:35 I have made the request to generate https://www.w3.org/2024/11/22-rdf-star-minutes.html TallTed 15:01:42 RRSAgent, make logs public 15:01:43 meeting: RDF-star Semantics TF 15:01:43 agenda: https://www.w3.org/events/meetings/6d0cd306-0be8-4267-865a-6272cc8d9da4/20241122T100000/ 15:01:43 clear agenda 15:01:43 agenda+ open agenda to discuss matters regarding semantics 15:01:43 RRSAgent, draft minutes 15:01:44 I have made the request to generate https://www.w3.org/2024/11/22-rdf-star-minutes.html TallTed 15:01:50 RRSAgent, make logs public 15:02:34 previous meeting: https://www.w3.org/2024/11/21-rdf-star-minutes.html 15:02:36 next meeting: https://www.w3.org/2024/12/05-rdf-star-minutes.html 15:03:04 enrico has joined #rdf-star 15:03:13 present+ 15:03:25 niklasl has joined #rdf-star 15:04:01 Souri has joined #rdf-star 15:04:16 chair: enrico 15:04:17 present+ 15:04:18 q+ 15:04:21 present+ 15:04:24 present+ 15:04:54 present+ 15:04:56 zakim, who is here? 15:04:56 Present: AndyS, enrico, thms, niklasl, TallTed, Souri 15:04:57 scribe: ad-hoc 15:04:58 On IRC I see Souri, niklasl, enrico, gkellogg, thms, RRSAgent, Zakim, TallTed, timbl_, AndyS, driib5, m2gbot, gb, ktk, csarven, gtw, agendabot, Tpt, rhiaro, pchampin 15:05:01 q? 15:05:09 william_vw has joined #rdf-star 15:05:15 I have made the request to generate https://www.w3.org/2024/11/22-rdf-star-minutes.html TallTed 15:05:21 present+ 15:05:29 q+ 15:06:07 present+ 15:06:12 niklasl1 has joined #rdf-star 15:07:06 q+ 15:07:28 ack thms 15:10:25 ack Souri 15:10:30 doerthe has joined #rdf-star 15:10:40 present+ 15:10:47 pfps has joined #rdf-star 15:10:58 present+ 15:11:01 q+ 15:11:04 q+ 15:11:06 https://github.com/w3c/rdf-star-wg/wiki/RDF-star-%22alternative-baseline%22/ 15:11:16 pfps has joined #rdf-star 15:11:20 niklasl has joined #rdf-star 15:11:22 q+ 15:11:27 present+ 15:11:30 q+ 15:11:31 ack pchampin 15:11:33 q+ on unstar 15:11:35 present+ 15:13:28 q+ on subj position and unstar 15:13:34 ack pfps 15:13:34 pfps, you wanted to comment on unstar 15:14:18 ack andys 15:14:41 It's unclear to me what role unstar now plays and what "two things" it relates together. 15:14:59 ack enrico 15:14:59 enrico, you wanted to comment on subj position and unstar 15:16:21 q+ on unstar information preserving 15:16:24 q+ to propose an alternative definition of information preservation 15:16:48 AndyS: IIRC we are having triple terms in the subject position in the semantics; in the RDF abstract data model (and hence syntaxes) it would be the more restrictive having triple terms only in the object position. 15:17:00 There are lots of properties that mappings that do not preserve semantics can have. One of them is some sort of encoding. One desirable property of an encoding is some sort of reversability. 15:17:53 ack niklasl 15:17:53 niklasl, you wanted to comment on unstar information preserving 15:19:05 https://github.com/w3c/rdf-semantics/issues/49 15:19:06 https://github.com/w3c/rdf-semantics/issues/49 -> Issue 49 Define an interpretation of Triple Terms (by niklasl) [needs discussion] 15:19:23 Just to be clear regarding triple-term position related decision: Has it been decided if N-Triple for RDF1.2 would allow having triple-term in the subject position? 15:19:41 q+ to ask about where we are re: graph vs dataset (or both) 15:20:36 ack pchampin 15:20:36 pchampin, you wanted to propose an alternative definition of information preservation 15:21:05 To Souri - "decided" is to strong (we have not "resolved") but otherwise, from my "IIRC", NT would not have triple-terms in the subject position. 15:21:36 s/to strong/too strong/ 15:21:50 q+ on strongly disagreeing unstar being only about syntax 15:22:12 ack andys 15:22:12 AndyS, you wanted to ask about where we are re: graph vs dataset (or both) 15:22:17 To Souri: IIRC the poll was about the semantics, but not about the possibility of triple terms in subject position (and neither about some syntaxes) 15:22:54 I was convince by niklasl's argument, as reported by gkellogg 15:23:00 q+ 15:24:22 We are looking at the "graph" flavor of unstar. (I will note that on the issue/PR for the wider audience) 15:25:37 rrsagent, please draft minutes 15:25:39 I have made the request to generate https://www.w3.org/2024/11/22-rdf-star-minutes.html AndyS 15:25:45 ack enrico 15:25:45 enrico, you wanted to comment on strongly disagreeing unstar being only about syntax 15:26:02 q+ 15:26:48 ack thms 15:27:15 q+ on not reusing the rdf old reification vocabulary 15:28:00 ack niklasl 15:28:04 q+ 15:28:17 I wonder wether the injectivity of our interpretation function could cause problems, but curious to see the bijection 15:28:49 q+ 15:29:20 ack enrico 15:29:20 enrico, you wanted to comment on not reusing the rdf old reification vocabulary 15:29:38 I lean towards enrico's point about using dedicated terms for unstarred triple terms 15:29:38 ack thms 15:29:44 ack niklasl 15:30:34 q+ 15:31:24 q+ 15:31:58 Explicit example of how I see it: https://github.com/w3c/rdf-star-wg/wiki/Converting-RDF-1.2-data-to-RDF-1.1 15:32:19 OK, maybe that was my point, so what is the bijection then? 15:32:20 ack enrico 15:32:24 ack pchampin 15:32:46 q+ 15:32:51 unicity = uniqueness? 15:32:54 q+ 15:34:06 Unless you name a graph with that name? 15:34:30 and for graph-style use of the unstar vocabulary? 15:36:11 ack niklasl 15:36:12 q+ 15:38:15 https://github.com/w3c/rdf-star-wg/issues/114#issuecomment-2389011520 15:38:15 https://github.com/w3c/rdf-star-wg/issues/114 -> Issue 114 Un-star operation to support RDF Dataset Canonicalization? (by niklasl) [needs discussion] 15:38:22 # a mixed environment 15:38:23 :r1 rdf:reifies 15:38:23 <<( :s :p :o1 )>> , 15:38:23 <<( :s :p :o2 )>> , 15:38:24 [ a rdf:Triple; rdf:subject :s ; rdf:predicate :p ; rdf:object :o3 ] , 15:38:24 [ a rdf:Triple; rdf:subject :s ; rdf:predicate :p ; rdf:object :o4 ] , 15:38:24 :g1 . 15:38:25 :g1 a rdf:Graph . 15:38:25 :g1 { 15:38:25 :s :p :o5 , 15:38:26 :o6 15:38:26 } 15:39:26 q+ 15:40:03 ack enrico 15:40:05 rdf:TripleTerm owl:hasKey (rdf:tripleTermSubject rdf:tripleTermPredicate rdf:tripleTermObject) . 15:40:13 That would fix it? 15:40:26 sameAs is defined on OWL; I think it should be possible to express the axioms on owl that allow us to infer that the two nodes of type TripleTerm are indeed sameAs, no? 15:40:45 using keys? 15:40:50 Yes, I just wrote that. :) 15:42:43 r1 rdf:reifies . r2 rdf:reifies . 15:42:51 thms: for me, the problem is that if you unstar, and then "restar" (inverse of unstar) your graph, it may not round-tripe 15:43:00 s/tripe/trip 15:43:00 r1 rdf:reifies _:b1. _:b1 :subject a. _:b1 :predicate b. _:b1 :object c. 15:43:06 r2 rdf:reifies _:b2. _:b2 :subject d. _:b2 :predicate e. _:b2 :object f. 15:43:30 r1 rdf:reifies <<(:a :b :c)>>. r2 rdf:reifies <<(:d :e :f )>>. 15:43:30 a owl:sameAs d. b owl:sameAs e. c owl:sameAs f. 15:43:45 SHOULD ENTAIL 15:43:51 _:b1 owl:sameAS _:b2. 15:44:18 q+ 15:44:21 I still dislike the injectivity (but can live with that after the discussion with pfps :) ) 15:46:03 q+ 15:46:05 s/:sameAS/:sameAs/ 15:46:07 ack thms 15:46:16 ack niklasl 15:47:19 ack doerthe 15:48:12 I have made the request to generate https://www.w3.org/2024/11/22-rdf-star-minutes.html TallTed 15:48:18 could we say that an rdf-star reifier that rdf:reifies only one triple term can be represented as RDF standard reification? 15:48:43 thms: I have en example of that (using OWL).... 15:49:20 niklasl do you happen to have a link? 15:49:42 It's not easy on the eyes, but: https://gist.github.com/niklasl/69428b043be6f1d33fd45f89cbe52632#file-statement-entailment-ttl 15:49:56 niklasl :) thanks! 15:50:12 Caveat: not updated to the correct unstarred forms 15:51:06 q? 15:51:09 q+ 15:52:40 q- 15:53:10 and for that I tried to make my argument short :( 15:53:25 q+ 15:54:48 q+ to ask about whether old-style reification to RDF-star is in fact a different algorithm 15:55:07 ack niklasl 15:55:50 ack andys 15:55:50 AndyS, you wanted to ask about whether old-style reification to RDF-star is in fact a different algorithm 15:56:27 q+ 15:56:34 q+ 15:56:53 ack thms 15:57:14 +1 to AndyS, because most old style reifications out there are probably more reifiers than triple terms 15:57:51 ack niklasl 15:58:56 _:r a rdf:Statement ; rdf:reifies <<( :s :p :o )>> 15:59:08 We also have more choice/control of the property names in unstar. 15:59:27 mmm, following your example enrico, I can see that it comes in hand that if I have 15:59:27 r1 rdf:reifies _:b1. _:b1 :subject a. _:b1 :predicate b. _:b1 :object c. 15:59:27 r2 rdf:reifies _:b2. _:b2 :subject d. _:b2 :predicate e. _:b2 :object f. 15:59:27 _:b1 owl:sameAs _:b2: 15:59:28 here, the injectivity comes in handy. We then have some kind of functional :subejct, :predicate, :object and we are out of our multiple object problem. 15:59:28 I know that this is a counterargument to my position :) 16:01:32 _:oldstyleReifier rdf:subject [ rdf:subjectOf <<( :s :p :o )>>; .. 16:03:59 I still dislike, yet, I see your point, but I think the triple term could be anything 16:04:09 i mean this 16:04:09 _:oldstyleReifier 16:04:09 a rdf:Statement ; 16:04:09 rdf:subject [ rdf:subjectOfTripleTerm <<( :s :p :o )>> ] ; 16:04:10 rdf:predicate [ rdf:predicateOfTripleTerm <<( :s :p :o )>> ] ; 16:04:10 rdf:object [ rdf:objectOfTripleTerm <<( :s :p :o )>> ] . 16:04:51 I have made the request to generate https://www.w3.org/2024/11/22-rdf-star-minutes.html TallTed 16:05:03 q+ on OWL... 16:05:33 ack niklasl 16:05:33 niklasl, you wanted to comment on OWL... 16:06:21 we have been kicked out! 16:06:37 re-join? 16:06:49 It's a sign! 16:07:20 AI 16:07:30 q? 16:07:47 q+ to wonder why OWL matters 16:08:08 q+ 16:08:14 q- 16:08:47 q+ 16:08:47 ack pfps 16:08:51 ack andy 16:08:53 OK, I think I dislike the whole injectivity because that already has old rdf reification in mind, we see a syntactical triple structure while we could also say that the triple term denotes some resource 16:10:09 ack niklasl 16:10:40 q+ 16:11:40 ack enrico 16:13:29 q+ 16:13:57 q- 16:14:58 q+ 16:16:54 ack thms 16:17:20 q+ 16:19:04 ack doerthe 16:22:36 q+ 16:22:51 ack thms 16:24:57 I have made the request to generate https://www.w3.org/2024/11/22-rdf-star-minutes.html TallTed