15:58:46 RRSAgent has joined #rdf-star 15:58:51 logging to https://www.w3.org/2024/09/05-rdf-star-irc 15:59:19 Agenda: https://www.w3.org/events/meetings/23bcb331-af6e-40af-98f1-11c029455d12/20240905T120000/ 15:59:19 clear agenda 15:59:19 agenda+ TPAC goals & topics -> 1 https://www.w3.org/2024/08/29-rdf-star-minutes.html#t03 15:59:19 agenda+ Continuation of last week's discussions. -> 2 https://www.w3.org/2024/08/29-rdf-star-minutes.html#t02 15:59:19 agenda+ rdf:states/rdf:asserts 15:59:28 present+ 15:59:32 fsasaki has joined #rdf-star 15:59:59 present+ 16:00:04 regrets+ 16:00:20 present+ 16:00:26 present+ 16:00:55 enrico has joined #rdf-star 16:01:01 present+ 16:01:14 ora has joined #rdf-star 16:01:23 present+ 16:01:27 present+ 16:01:29 william_vw has joined #rdf-star 16:01:33 present+ 16:01:35 present+ 16:01:35 chair+ 16:01:38 present+ 16:01:48 present+ 16:02:03 present+ 16:02:11 scribe+ 16:02:14 Meeting: RDF-star WG biweekly focused meeting 16:02:19 AZ has joined #rdf-star 16:02:22 RRSAgent, draft minutes 16:02:24 I have made the request to generate https://www.w3.org/2024/09/05-rdf-star-minutes.html ktk 16:02:26 agenda? 16:02:34 present+ 16:02:39 RRSAgent, make log public 16:02:51 ora: TPAC planning 16:03:13 Zakim, open item 1 16:03:13 agendum 1 -- TPAC goals & topics -> 1 https://www.w3.org/2024/08/29-rdf-star-minutes.html#t03 -- taken up [from agendabot] 16:03:13 ... earlier idea was refining details 16:03:30 q? 16:03:34 ... reserve some time for semantics and model 16:03:37 q+ 16:03:39 olaf has joined #rdf-star 16:03:42 ack AndyS 16:03:42 scribe+ 16:03:46 present+ 16:04:04 AndyS: another thing to be aware of is that we may have a visitor, of note. 16:04:16 previous meeting: https://www.w3.org/2024/08/30-rdf-star-minutes.html 16:04:16 next meeting: https://www.w3.org/2024/09/06-rdf-star-minutes.html 16:04:21 ... We might want to prep him about the current state of the WG. This would make things easier. 16:04:38 ... We have to to a general briefing anyway, for other's sake. 16:04:51 ora: may prepare a few slides 16:04:51 scribe- 16:04:52 ... 1 - where are we? 16:05:13 ... 2 - points of contention - areas of debate 16:05:28 RRSAgent, draft minutes 16:05:29 I have made the request to generate https://www.w3.org/2024/09/05-rdf-star-minutes.html TallTed 16:05:35 present+ 16:06:04 ... there will be questions about syntax but I'd like to the focus abstract syntax and semantics 16:06:21 ... concrete syntax can be done afterwards 16:07:04 q+ 16:07:05 ... I had discussion with LPG person. Hard to explain reifiers and named graphs 16:07:09 ack tl 16:07:25 doerthe has joined #rdf-star 16:07:29 tl: I made a proposal about named graphs 16:07:39 present+ 16:07:47 ... noted at the time - they were in use for other things 16:07:49 Are we debating this, or mentioning it? 16:08:24 ora: This is not reopening the discussion. The concern is explaining to the wider audience. 16:08:30 q+ 16:08:37 ack enrico 16:08:40 tl: Don't want to reopen the discussion 16:09:06 enrico: We could defer until the basics are stable. 16:09:16 We need to present the differences clearly and concisely. And anchor this in the group? 16:09:22 q+ 16:10:02 ... what we are doing is many-many naming which can capture the ideas of named graphs / quads. 16:10:31 ora3 has joined #rdf-star 16:10:36 It's not the same as the named graph notion. There are some crucial differences. 16:10:41 ... reifier id is the 4th element of a quad. This is my observation. 16:10:44 chair+ 16:10:47 present+ 16:10:53 q? 16:10:57 ack niklasl 16:11:44 niklasl: we need to clearly explain the differences. Maybe if not done in time for TPAC we should defer. 16:11:54 q+ 16:11:57 Souri has joined #rdf-star 16:12:03 ack AndyS 16:12:03 I can have a go. 16:12:11 scribe+ 16:12:26 AndyS: one of the things that can be relevant for TPAC is the fact that N3 graphs are opaque. 16:12:42 That's one important difference. 16:12:50 if you want some connection to N3, I can also help with the slides ora 16:12:53 ... This was part of last year's discussion. We can bring that up and explain about transparency. 16:13:29 ... The other thing is: we found it too hard. It is too big to reinvent RDF with graph literals, whatever graph literals are in this case. 16:13:32 The other main difference is that there is a named relationship between the reifier and each triple (term). This can also be "SHACL:d" and/or OWL-constrained. 16:13:33 scribe- 16:13:41 ora: Will draft some slides. 16:14:11 ... when slides done., will send out to interested parties. 16:14:16 q+ 16:14:21 ack ktk 16:14:21 ... what else at TPAC 16:14:37 ktk: Process backlog? 16:15:05 ora: I gave a talk at tech user community of LDBC 16:15:20 ... interesting points raised 16:15:58 ... support for multiple reifiers of a triple 16:16:14 ... may relate to some ongoing LPG thinking 16:16:20 (And just as I'm not friends with a set of people, but with each of my friends, a refiier reifies one or more triples (not the set of them)?) 16:16:57 ... trying to schedule time with Alistair Green 16:17:30 ... I had not expected LPG to be a dynamic target 16:18:04 q? 16:18:23 ... some discussion at TPAC to bring people up-to-date. 16:19:02 ktk: how do we align the areas e.g. schema 16:19:25 ... whatever that means. Better to be proactive. 16:19:25 q+ 16:20:11 ack enrico 16:20:14 Dominik_T has joined #Rdf-star 16:20:16 enrico: I have been invited to contribute to LPG schema graph. 16:20:33 Present+ 16:20:44 ... "Relational AI" - strong on data modelling 16:21:07 q+ 16:21:10 Regarding undirected edges, couldn't we actually extend s-p-o in RDF to include a 3-valued direction value: forward, reverse, and none? 16:21:23 ... bringing traditions of LDBC starting from relational databases - ER c.f. RDFS. 16:21:36 q+ to ask if the two TPAC meetings (Tuesday and Thursday) have different purposes 16:21:38 ack ora 16:21:42 ... will be weekly meetings from mid-September 16:21:59 ora: there has some activity already 16:22:24 ... interesting to see joint work starting 16:22:51 enrico: subset of PG-schema + PG keys 16:22:55 ack tl 16:22:55 tl, you wanted to ask if the two TPAC meetings (Tuesday and Thursday) have different purposes 16:23:18 q? 16:23:19 tl: Two meetings at TPAC - different purposes? 16:23:20 q+ 16:23:26 ack pchampin 16:23:53 Dominik_T has joined #RDF-star 16:23:57 pchampin: some missing stuff on the calendar 16:24:03 ... may not be accurate 16:24:20 ... I think we have 4 slots overall 16:24:20 https://www.w3.org/2024/09/TPAC/#schedule 16:24:38 ... 2 full half days = 4 slots 16:24:46 ... one is shared with JSON-LD 16:25:09 .. about triple terms and all that in JSON-LD 16:25:27 ora: the chairs will sketch out the TPAC time. 16:26:11 ktk: 18:00 CET start , Tuesday and Thursday 16:27:00 gkellogg: I see 2 AM entries Tuesday and Thursday 9am Pacfic time 16:27:06 Zakim, next item 16:27:06 agendum 2 -- Continuation of last week's discussions. -> 2 https://www.w3.org/2024/08/29-rdf-star-minutes.html#t02 -- taken up [from agendabot] 16:27:41 Dominik_T has joined #Rdf-star 16:28:08 ktk: we did not finish the discussion from Semantics TF. 16:28:21 ora: we were not ready to vote. 16:28:49 s/PG-keys/PG keys + PG-types/ 16:28:50 q+ 16:28:56 ack enrico 16:29:02 enrico: Summary -- 16:29:08 sorry, what does LDBC stand for? 16:29:33 ... issue is whether well-formed fragment with rdf:reifies + triple term. 16:29:38 RRSAgent, draft minutes 16:29:39 I have made the request to generate https://www.w3.org/2024/09/05-rdf-star-minutes.html TallTed 16:29:45 LDBC = Linked Data Benchmark Council 16:29:59 https://ldbcouncil.org/ 16:30:07 thanks olaf 16:30:15 ... want other properties allowed and it becomes a rdf:ReificationProperty 16:30:22 q? 16:31:00 ... we can get remove the well-formed condition / syntax restriction. 16:31:23 s/well-formed condition/s/well-formed RDF condition/ 16:31:51 q+ 16:31:56 s/Continuation of last week's discussions./Proposed resultion by Semantics TF (cont.) 16:31:58 ack ora 16:32:05 ... if you do something bizarre , bizarre things happen. i.e. no hard restriction 16:32:31 ora: if we say don't mix with old reification then what? 16:32:32 q+ 16:32:35 q+ 16:32:39 ... we have to answer that. 16:33:00 q- 16:33:09 q+ 16:33:31 enrico: old style continues to work., It is a mix of old+new (triple terms) - RDF 1.1 data does not have triple terms so not affected. 16:33:38 ack gkellogg 16:34:11 gkellogg: we need to consider RDF 1.1 reification for mapping to classical RDF 16:34:25 q+ 16:35:00 ... I think an intuition is that rdf:reifies + triple terms gives a translation to RDF 1.1 16:35:07 william_vw has joined #rdf-star 16:35:07 ack gtw 16:35:09 ... RDF/XML ... unclear. 16:35:40 gtw: no probs only true for data - not tooling. 16:35:53 ... e.g. unexpected triple term. 16:36:06 ... such tooling will break 16:36:18 ... Not restricted to reification 16:36:49 ... new data will break existing modelling 16:36:52 ack pchampin 16:36:53 q+ 16:36:58 q+ 16:37:31 pchampin: This is like RDF Collection vs RDF Seq (RDF 1.1 and RDF 1.0) 16:38:14 .. RDF 1.1 WG decision was not to deprecate rdf:Seq - marked "archaic" to suggest using new forms. 16:38:23 ack enrico 16:38:27 s/.. RDF/... RDF/ 16:38:43 q+ 16:38:55 q+ 16:39:23 enrico: Two elements - I'm unclear what to do. Anything with new forms will break RDF 1.1 tools. 16:40:07 Dominik_T6 has joined #rdf-star 16:40:16 ... triple terms only have a meaning if used in a certain way. 16:41:02 ack niklasl 16:41:04 ... not clear the problem will appear. 16:41:18 niklasl: SPIN example interesting. 16:41:34 ... RDF 1.1 reification is a pattern. 16:43:01 ... any property that might reference a triple term is a rdf:ReifierProperty 16:44:05 I currently don't see how we can align with N3 because of the opacity, but maybe it is possible 16:44:08 ... SPIN is (was) doing something meta. 16:44:50 enrico: misunderstanding about statements and triple terms 16:45:42 ... the reifier denotes the triple term. 16:45:56 ... the triple term is the triple term. 16:47:11 ack ktk 16:47:14 ... tomorrow ... 16:47:28 RRSAgent, make minutes 16:47:29 I have made the request to generate https://www.w3.org/2024/09/05-rdf-star-minutes.html pchampin 16:47:35 that is btw. why I want to emphasize that much that there is a difference between triples and triple terms 16:47:37 ktk: similar problems at RDF 1.1 e.g. PREFIX 16:47:39 even in the semantics 16:47:46 ... some tools got left behind 16:48:01 ... some tools update 16:48:07 ack doerthe 16:48:51 niklasl has joined #rdf-star 16:48:55 present+ 16:49:15 doerthe: to Gregory: whether the class of reification property makes sense in the examples. 16:49:58 ... can use the property with things other than triple terms. 16:50:09 q+ 16:50:16 ack tl 16:50:16 q+ 16:50:24 +1 to what doerthe said 16:50:36 tl: not seeing a problem 16:51:00 ... in general, "tools may break" is inevitable 16:51:14 q+ 16:51:17 ack william_vw 16:51:45 william_vw: I disagree that it is not a problem. 16:52:02 s|SPIN example|SPIN (https://spinrdf.org/) example 16:52:25 ... as I understood it, a triple term is used and has a reifier 16:52:45 ... what gtx points out there are other contexts 16:52:59 q+ 16:53:02 ... a statement which is not to assign a reifier 16:53:20 ... but the inferences mix in 16:53:40 q- 16:53:55 q- 16:54:08 is this a condition for the unstar work? 16:54:46 ora: a continuing discussion 16:55:31 enrico: Semantics meeting tomorrow 16:55:40 RRSAgent, draft minutes 16:55:41 I have made the request to generate https://www.w3.org/2024/09/05-rdf-star-minutes.html ktk 16:56:50 present+ 16:59:18 s/to to/to/ 16:59:34 s/reslution/resolution/ 16:59:40 s/refiier/reifier/ 16:59:46 s/Pacfic/Pacific/ 17:00:06 s/gtx/gtw/ 17:00:12 RRSAgent, draft minutes 17:00:13 I have made the request to generate https://www.w3.org/2024/09/05-rdf-star-minutes.html ktk 17:00:41 s/have to a/have to do a/ 17:00:44 RRSAgent, draft minutes 17:00:46 I have made the request to generate https://www.w3.org/2024/09/05-rdf-star-minutes.html ktk 17:02:46 RRSAgent, leave 17:02:46 I see no action items