15:13:18 RRSAgent has joined #rdf-star 15:13:22 logging to https://www.w3.org/2024/12/06-rdf-star-irc 15:14:32 Note that until RRSAgent's arrival, there has been no log ... so present+, meeting:, agenda:, etc., may have to be repeated. (I can't see IRC earlier than 10 past the hour, when I joined.) 15:14:48 present+ 15:15:03 fine with that 15:15:10 meeting: RDF-Star Semantics TF 15:15:22 agenda: https://www.w3.org/events/meetings/6d0cd306-0be8-4267-865a-6272cc8d9da4/20241206T100000/ 15:15:22 clear agenda 15:15:22 agenda+ the Semantics TF will focus on the pull request "New triple term semantics in the rdf-semantics spec #55" -> https://github.com/w3c/rdf-semantics/pull/55 https://github.com/w3c/rdf-semantics/pull/55 15:15:24 so, to me, only the rdf:type is open :) 15:15:36 and the subject position of course... 15:15:39 ack niklasl 15:15:39 q+ to apologize for misreading the PR 15:15:45 ack enrico 15:16:23 ack william_vw 15:16:52 I have made the request to generate https://www.w3.org/2024/12/06-rdf-star-minutes.html TallTed 15:17:27 previous meeting: https://www.w3.org/2024/12/05-rdf-star-minutes.html 15:17:27 next meeting: https://www.w3.org/2024/12/11-rdf-star-minutes.html 15:18:34 ack doerthe 15:18:40 Occurrences (tokens are a kind of occurrences). 15:19:11 q+ 15:19:48 present+ doerthe, enrico, william_vw, pchampin, thomas, niklasl, gkellogg, Souri, AndyS 15:20:16 q? 15:20:28 ack thomas 15:20:28 thomas, you wanted to say that I don't oppose triple terms in subject position anymore 15:21:44 I'd say conflations are a general problem. And not only in RDF. :) 15:23:12 The notion of distinct identity is the cause of those problems. (But without that, we only have fuzzy logic.) 15:23:26 I have made the request to generate https://www.w3.org/2024/12/06-rdf-star-minutes.html TallTed 15:23:32 ack pchampin 15:23:32 pchampin, you wanted to apologize for misreading the PR 15:23:59 chair: enrico 15:24:11 scribe- 15:26:00 Question of definition: The classes are the sets of properties that (at times / may) point to or from the *edges* in the graph (and not the nodes)? 15:26:05 q? 15:26:40 q+ 15:27:20 that it looks ugly in the spec ;) 15:28:20 it might not stop there 15:30:37 ack enrico 15:30:42 ack niklasl 15:32:18 present+ 15:32:38 q+ 15:32:57 q+ 15:35:13 ack enrico 15:36:02 Souri has joined #rdf-star 15:36:07 present+ 15:39:53 rdf:StarificationProperty 15:40:19 rdf:TripleTermProperty 15:41:42 ack thomas 15:41:59 q+ 15:43:36 q+ 15:43:41 thomas, you might be interested in https://www.w3.org/TR/2013/REC-prov-dm-20130430/#term-specialization 15:43:43 thomas do you have a link to the Berlin example :-) 15:45:29 q+ 15:46:10 We have not been able to make it immediately clear, but we know that it is problematic? 15:46:16 q+ 15:47:31 ack doerthe 15:47:53 ack niklasl 15:48:07 @william_vw :Berlin :likedBy :John ; :in :Summer ; :likedBy :Alice ; :in :Winter . 15:48:29 The other possibility is to exclude everything except rdf:reifies. 15:49:07 @thomas thanks 15:49:45 @Souri ... but then what about rdfs:states ;-) IMO we need more properties than just rd:reifies 15:51:08 or rdf:associates, just to be neutral -- :r rdf:associates <<( :s :p :o )>> . It is just association and nothing else. 15:51:31 s/just association/just an association/ 15:52:00 ack pchampin 15:52:55 @thomas rdfs:states probably carries too much meaning 15:54:04 @pachampin but if it has no meaning then it just states the obvious 15:54:29 q+ 15:55:46 An assembly language (like RDF) can provide just the minimal core support => :r rdf:associates <<( :s :p :o )>> . :r a :Saying . This is as opposed to (in a higher level language): :r :says <<( :s :p :o )>> . 16:00:57 I would be satisfied with that. 16:01:15 I like the minimality. 16:01:16 +1 16:01:16 ack enrico 16:01:55 ack thomas 16:01:58 q+ 16:02:58 ack pchampin 16:03:01 q+ 16:03:14 (I did include no use as subject outside of generalized RDF in what I would be satisfied with.) 16:04:38 q+ 16:04:57 q+ to propose "rdf:indicates" (which Enrico proposed months ago) 16:06:07 ack enrico 16:06:17 ack gkellogg 16:06:51 and that was where we started, right? 16:07:21 doerthe: ofc 16:07:27 ack thomas 16:07:27 thomas, you wanted to propose "rdf:indicates" (which Enrico proposed months ago) 16:08:30 q+ 16:08:35 Etymology. The term "reification" originates from the combination of the Latin terms res ("thing") and -fication, a suffix related to facere ("to make"). 16:08:59 ack nikasls 16:09:01 ack nikasl 16:09:09 ack niklasl 16:10:37 Reification is when we make a "thing" (a resource) out from something abstract (a triple term) 16:11:37 Souri has joined #rdf-star 16:11:41 present+ 16:12:22 Yes, but in my intuition that somehow seems to imply that the thing exists (or is brought into existance by the reification) but that is not what is happening (at least not with rdf:reifies) 16:13:06 s/rdf:reifies)/rdf:reifies as opposed to rdfs:states) 16:15:13 but in my opinion it is not that clear, what the triple term denotes 16:15:41 (and it is not even important in my opinion ) 16:19:20 q? 16:19:24 q+ 16:19:43 "john has four letters" vs. "john loves paul", even without triple term 16:20:40 ack thomas 16:22:16 :r1 rdf:reifies <<(:john :marries :paula)>> ; a :Photo . :r2 rdf:reifies <<(:john :marries :paula)>> ; a :Event . 16:22:36 yes, Souri 16:23:39 I think we should keep things open even if we reify, we do not need to know what the triple term denotes and therefore, I would leave things that open that I would not even add injectivity 16:24:20 No. 16:24:27 I think we should discuss this injectivity stuff once and for all doerthe 16:24:49 sorry for always bringing it up, the cicero in me ;) 16:24:50 🤺🤺\ 16:26:55 we shouldn't kill rdf:TripleTerm 16:27:03 q+ 16:28:58 https://github.com/w3c/rdf-ucr/issues/27 -> Issue 27 Integrating different ontology designs through entailment upon triple terms (by niklasl) [use case] 16:30:47 ack doerthr 16:30:53 ack doerthe 16:34:51 doerthe has joined #rdf-star 16:36:01 @niklasl no pun intended, I'm sure 16:36:36 Not sure I understand this discussion about appropriateness of injectivity. Can we take this example to explain this? => :r1 rdf:reifies <<(:john :marries :paula)>> ; a :Photo . :r2 rdf:reifies <<(:john :marries :paula)>> ; a :Event . 16:45:22 This, by the way, is why I'm not really comfortable with the type rdf:Triple*Term*. It's not the type of that resource, but of the syntactic structure? 16:46:22 Is this what you are saying? Two entities: [SR: Set of Reifiers], [ST: Set of Triple-Terms]. One possibly many-to-many relationship: rdf:reifies that is a subset of SR x ST? 16:50:43 is this the problem - without injectivity, we can have: 16:50:43 r1 --reifies--> RE1 16:50:43 where RE1 = <<:john :loves :paul>>, <<:mary :loves :paula>> 16:50:43 so, no longer know what r1 is an occurrence of? ... 16:51:03 Yes. 16:51:11 (AFAICS) 16:51:32 r1 is then an occurrence of those two triples 16:52:28 Yes. I think ReflexiveProperty came up before as a counter, but the directional aspect is still true (only one implies the other). 16:52:39 SymmetricProperty, sorry. 16:53:14 So, with injectivity: <<( :s1 :p1 :o1 )>> owl:sameAs <<( :s2 :p2 :o2 )>> . <= => :s1 owl:sameAs :s2 . :p1 owl:sameAs :p2 . :o1 owl:sameAs :o2 . 16:53:29 Yes. 16:54:52 (the above is also known as a "fan trap" in databases, I believe :-) ) 16:55:36 Souri has joined #rdf-star 16:55:38 to avoid it, we only need a many-to-one here, no? 16:55:41 present+ 16:56:02 gkellogg has joined #rdf-star 16:57:11 gkellogg has joined #rdf-star 16:59:09 So, can s1-s2, p1-p2, o1-o2 "sameAs" be inferred from the following triples? (I hope not because there will be issues if rdf:reifies was used in one-to-many manner here.) => :r1 owl:sameAs :r2 . :r1 rdf:reifies <<( :s1 :p1 :o1 )>> . :r2 rdf:reifies << :s2 :p2 :o2 )>> . 17:00:28 @Souri I don't think so, since rdf:reifies is not injective 17:02:04 the more that gets written in IRC, the more I'll know about what is said from here on... 17:03:57 I have made the request to generate https://www.w3.org/2024/12/06-rdf-star-minutes.html TallTed 17:06:10 From my end, I think I understand enrico's point. Have to drop off. 17:06:13 niklasl has joined #rdf-star 17:18:20 "it" doesn't refer to a sentence but to what the sentence describes 17:18:51 in our semantics the reifier doesn't refer to what the sentence describes, but to the sentence itself 17:20:14 https://en.wikipedia.org/wiki/Tl%C3%B6n,_Uqbar,_Orbis_Tertius 17:21:35 we scared everyone away :D 17:25:59 proposition = statement . it can be true or false 17:26:10 +1000 for rdf:Proposition 17:26:14 so we're not saying about it's truth value 17:26:39 but then we should clarify the distinction to a fact, which we consider a true statement 17:26:39 ... And then.... rdf:PropositionProperty ? 17:31:03 F-Logic is cool 17:37:50 Enrico: "a triple term denotes a proposition" 17:37:55 +1 to that 17:39:43 Works for me. Noting that "An IRI denotes a[ny] resource.", and "A literal denotes .[... a value in the value space of the datatype of the literal]" 17:39:43 s/F-Logic is cool/"F-Logic is cool, Common Logic not so much" 17:40:36 gkellogg has joined #rdf-star 17:42:35 rrsagent, draft minutes 17:42:36 I have made the request to generate https://www.w3.org/2024/12/06-rdf-star-minutes.html niklasl 17:58:30 gkellogg has joined #rdf-star 18:28:14 Zakim, bye 18:28:14 leaving. As of this point the attendees have been pchampin, thomas, Souri, enrico, gkellogg, niklasl, doerthe, william_vw, TallTed, AndyS 18:28:14 Zakim has left #rdf-star 18:28:19 RRSAgent, bye 18:28:19 I see no action items