15:56:28 RRSAgent has joined #rdf-star 15:56:32 logging to https://www.w3.org/2024/07/18-rdf-star-irc 15:56:33 meeting: RDF-Star WG biweekly meeting 15:56:57 Agenda: https://www.w3.org/events/meetings/348e384e-2c0d-4c88-bb5c-5ddddf93ef4d/20240718T120000/ 15:56:57 clear agenda 15:56:57 agenda+ Approval of minutes from the last two meetings: -> 1 https://www.w3.org/2024/06/27-rdf-star-minutes.html , -> 2 https://www.w3.org/2024/07/11-rdf-star-minutes.html 15:56:57 agenda+ Proposed resultion by Semantics TF -> 3 https://www.w3.org/2024/07/12-rdf-star-minutes.html 15:56:58 agenda+ Proposal for next week's discussion 15:56:59 agenda+ Review of pull requests, available at -> 4 https://github.com/orgs/w3c/projects/20/views/4 15:57:02 agenda+ Issue Triage, available at -> 5 https://github.com/orgs/w3c/projects/20/views/5 15:57:05 agenda+ Any Other Business (AOB), time permitting 15:59:52 scribe+ 15:59:56 present+ 16:00:06 tl has joined #rdf-star 16:00:24 present+ 16:00:25 present+ 16:00:30 present+ 16:00:32 gkellogg has joined #rdf-star 16:00:36 RRSAgent, draft minutes 16:00:37 I have made the request to generate https://www.w3.org/2024/07/18-rdf-star-minutes.html TallTed 16:00:41 RRSAgent, make logs public 16:00:51 present+ 16:00:53 present+ 16:01:06 present+ 16:01:06 enrico has joined #rdf-star 16:01:09 present+ 16:01:46 previous meeting: https://www.w3.org/2024/07/12-rdf-star-minutes.html 16:01:46 next meeting: https://www.w3.org/2024/07/19-rdf-star-minutes.html 16:02:19 ora has joined #rdf-star 16:03:06 Dominik_T7 has joined #rdf-star 16:03:22 doerthe has joined #rdf-star 16:03:28 ah ok 16:03:35 present+ 16:03:55 present+ 16:04:02 AZ has joined #rdf-star 16:04:03 present+ 16:04:12 present+ 16:04:18 regrets+ pchampin 16:04:24 present+ 16:04:36 zakim, next agendum 16:04:36 agendum 1 -- Approval of minutes from the last two meetings: -> 1 https://www.w3.org/2024/06/27-rdf-star-minutes.html , -> 2 https://www.w3.org/2024/07/11-rdf-star-minutes.html -- 16:04:39 ... taken up [from agendabot] 16:05:29 minutes look fine to me 16:05:39 Souri has joined #rdf-star 16:05:45 present+ 16:06:05 PROPOSAL: Approve minutes of 2024-06-27 and 2024-07-11 16:06:05 +1 16:06:08 +1 16:06:08 +1 16:06:09 +0 (I was not there) 16:06:15 +1 16:06:16 +1 16:06:16 +1 16:06:16 eBremer has joined #rdf-star 16:06:17 +1 16:06:20 +1 16:06:21 +1 16:06:25 regrets+ fsasaki 16:06:27 present+ 16:06:30 +0 (was not present last week) 16:06:56 +1 16:06:56 +1 16:07:11 +0 (haven't reviewed) 16:07:19 RESOLVED: Approve minutes of 2024-06-27 and 2024-07-11 16:07:28 zakim, next agendum 16:07:28 agendum 2 -- Proposed resultion by Semantics TF -> 3 https://www.w3.org/2024/07/12-rdf-star-minutes.html -- taken up [from agendabot] 16:07:39 gkellogg has joined #rdf-star 16:07:45 the proposal is at https://github.com/w3c/rdf-star-wg/wiki/RDF-star-%22minimal-baseline%22 16:08:03 ora: I was not at the meeting, can anyone give a summary 16:08:17 present+ 16:08:45 nicklasl: the proposal adds triple triple terms and defines well-formed triple terms 16:09:09 nicklasl: the triple terms are fully transparent 16:09:33 nicklasl: this was discussed last Thursday and there were no objections 16:10:07 nicklasl: rdf:reifies with concept reifier 16:10:11 Dominik_T has joined #rdf-star 16:10:31 https://github.com/w3c/rdf-star-wg/wiki/RDF-star-and-LPGs 16:10:42 nicklasl: this is compatible with the use cases we've seen except for the one about recording deltas to RDF graphs 16:11:09 rrsagent, generate minutes 16:11:11 I have made the request to generate https://www.w3.org/2024/07/18-rdf-star-minutes.html gkellogg 16:11:20 nicklasl: this also caters to provenance of unasserted triples and other advanced usages 16:11:29 chair: ora 16:11:46 nicklasl: this also permits many-to-many reifiers 16:12:02 q? 16:12:02 q? 16:12:24 q+ 16:12:51 enrico: there was some discussion on syntax and whether triple terms have to be restricted to object position 16:13:24 mmm, but I doubt that we simply should not have the injectivity 16:13:31 enrico: each unique triple term has a unique resource 16:13:34 ack AndyS 16:13:45 enrico: doerte mentioned that this might be a problem in extensions 16:14:21 q+ to ask about relying entirely on transparent triple terms 16:14:35 Kurt has joined #rdf-star 16:14:37 andys: there are two levels of syntax - general syntax and well-formed syntax 16:14:43 @enrico you have a funny way of talking me into the well-formed fragment: You introduce a problem I don’t think we have and then create a solution. ;) 16:14:43 I agree that the well-formed semantics solves the injectivity problem, I just doubt that we need to create the problem. 16:14:43 q+ 16:14:49 ack gtw 16:14:49 gtw, you wanted to ask about relying entirely on transparent triple terms 16:15:34 gtw: several months ago dorthe had some examples where entailment produced many-to-many results 16:16:07 s/dorthe/doerhe/ 16:16:21 s/doerhe/doerthe/ 16:16:55 I think Enciro's page https://github.com/w3c/rdf-star-wg/wiki/RDF-star-and-LPGs addresses this? 16:17:09 To understand why the many-to-many is not prblematic for LPGs, see: https://github.com/w3c/rdf-star-wg/wiki/RDF-star-and-LPGs 16:17:16 gtw: there are some places where many-to-one is preferred 16:18:06 enrico: see the link above showing that the minimal baseline works for LPGs 16:18:14 q+ 16:18:28 q+ 16:19:06 doerthe: my point was that a previous proposal had problems 16:19:09 ack Kurt 16:19:37 Kurt: my proposal is relevant to this issue 16:20:04 Kurt: LPG style semantics has local predicates 16:20:39 ack AndyS 16:21:25 AndyS: part of the transparency issue is that IRIs are transparent in embedded triples 16:21:57 AndyS: there are conventions on use of IRIs on the web 16:22:06 ack gkellogg 16:22:23 s/ah ok// 16:22:23 s/minutes look fine to me/pfps: minutes look fine to me/ 16:22:23 rrsagent, draft minutes 16:22:25 I have made the request to generate https://www.w3.org/2024/07/18-rdf-star-minutes.html TallTed 16:23:03 gkellogg: the many-to-many issue looks similar to the situation with lists 16:23:13 Previous discussion about use of URIs -- https://www.w3.org/2024/07/11-rdf-star-minutes.html#t01 16:23:53 s/Enciro's/Enrico's/ 16:24:34 https://githua.com/w3c/rdf-star-wg/wiki/Proposal:-Named-Node-Expressions 16:24:45 https://github.com/w3c/rdf-star-wg/wiki/Proposal:-Named-Node-Expressions 16:25:17 Kurt: [presents information from the slide above] 16:25:20 s|https://githua.com/w3c/rdf-star-wg/wiki/Proposal:-Named-Node-Expressions|| 16:26:52 Kurt: a blank node is a local variable 16:27:45 Kurt: sometimes a local identifier is provided, but sometimes it is not, e.g., in [] syntax 16:28:38 q+ 16:28:57 Kurt: the blank node in a [] cannot be referenced elsewhere 16:29:09 ora: how does this relate to the minimum baseline 16:29:22 q- 16:30:15 Kurt: if a local name could be added to a [] node then this would allow references to it elsewhere in the same document 16:30:26 q+ 16:30:56 Kurt: expanding the [] syntax to triples necessarily adds a local name for the blank node 16:31:58 ora: but if this name is an IRI there is a difference 16:32:19 Confusion may arise because `[]` are brackets, sometimes called square brackets. `{}` are braces, sometimes called curly brackets. 16:32:29 +1 to TallTed 16:32:55 I've tried not to use "brace" or "bracket" in scribing 16:34:06 https://lists.w3.org/Archives/Public/public-rdf-star-wg/2024May/0067.html 16:34:34 enrico: I read the document and replied that this looks like singleton properties 16:35:28 ora: how would I know that this is like a singleton property? 16:36:06 I'm not geting the gist of this discussion so the scribing may not be accurate - see the document for more information 16:38:12 I normally try to avoid brining the complexity of blank nodes in discussions to avoid missing out on the elephant in the room. :-) 16:38:34 s/brining/bringing/ 16:38:58 This is where you can find the document by Kurt: https://lists.w3.org/Archives/Public/public-rdf-star-wg/2024May/0064.html 16:40:17 Kurt: in LPG there is an internal identifier for each edge, different from the label of the edge 16:40:27 Sounds like for this to work as intended, the abstract syntax would need to allow blank node predicates. 16:40:40 ora: singleton properties have not gone anywhere in RDF 16:41:34 Kurt: my contention is that you do not have the concept of a singleton property then you cannot have the many-to-one case 16:41:59 q+ 16:42:21 ack enrico 16:42:55 enrico: there was a long discussion of singleton properties and it was turned down 16:43:16 ack TallTed 16:43:17 +1 to enrico 16:43:43 we will have to have the discussion what the rdf:reifies relation actually means. we will then have to re-visit instantiation, e.g. singleton prperties 16:44:10 TallTed: as I'm reading this is appears to me that the author of the data needs to know that there are these two marries edges when the data is created and that is not viable 16:44:14 +t to TallTed 16:45:30 q? 16:45:51 Kurt: without named node expressions you cannot create a singleton property 16:46:12 q+ 16:46:27 q+ 16:46:40 Kurt: Neo4J has an internal hidden identifier for the statement that acts as a singleton property 16:47:04 I do get that if someone wants exactly the design that LPGs have, that's singleton properties (as I wrote a while back). But that does not handle lots of what we're enabling with rdf:reifies and references to triples. If there is opposition to enabling that, please speak up now. 16:47:18 ack gkellogg 16:47:22 ora: let's go back to the queue 16:47:31 q+ to note that masked identifiers are implementation details; they are not part of the abstract data model; they do not really exist. seeAlso Oracle's invisible ROWID. 16:47:52 gkellogg: what this boils down to in the abstract syntax is to allow blank node predicates 16:48:09 ack TallTed 16:48:09 TallTed, you wanted to note that masked identifiers are implementation details; they are not part of the abstract data model; they do not really exist. seeAlso Oracle's invisible 16:48:12 ... ROWID. 16:48:14 @niklasl i'm opposed to that 16:48:49 TallTed: invisible ids are not part of RDF and thus not portable 16:49:20 Kurt: the idea is to promote these to IRIs 16:49:54 ora: back to the agenda 16:49:57 nonymizing anonymous nodes makes them no longer anonymous ... in which case they should just be nonymized 16:49:59 q+ 16:50:07 ack tl 16:50:42 tl: I think that the minimal baseline is a good basis but leaves some things open 16:51:01 tl: what does the reifies thing mean, for example 16:51:20 tl: and unasserted assertions 16:51:23 q+ 16:51:28 ack ktk 16:51:45 tl: so I'm in favour of adopting the minimal baseline 16:52:01 q+ 16:52:06 ack doerthe 16:52:07 ktk: adopting is just creating something to compare against 16:52:42 doerthe: so proposals from now on are made against the baseline 16:52:53 ora: what is the proposal to vote on? 16:53:11 https://www.w3.org/2024/07/12-rdf-star-minutes.html 16:53:35 q+ 16:53:40 ack gkellogg 16:53:55 https://github.com/w3c/rdf-concepts/pull/96 16:53:55 https://github.com/w3c/rdf-concepts/pull/96 -> Pull Request 96 Change the section on Quoted Triples to Triple Terms. (by gkellogg) [spec:substantive] 16:53:58 ora: the Semantics group only resolved to bring forward the minimal baseline 16:54:45 gkellog: i created a draft PR for the purpose but all we need is a resolution to adopt the minimal baseline 16:54:53 https://github.com/w3c/rdf-star-wg/wiki/RDF-star-%22minimal-baseline%22 16:55:11 PROPOSAL: Adopt minimal baseline https://github.com/w3c/rdf-star-wg/wiki/RDF-star-%22minimal-baseline%22 16:55:14 +1 16:55:16 +1 16:55:17 +1 16:55:17 +1 16:55:17 +1 16:55:18 +1 16:55:22 +1 16:55:42 -0 ; I remain doubtful that this addresses LPG use-cases 16:55:43 +1 16:55:45 +0 16:55:45 +1 16:55:49 +1 16:55:54 +1 16:55:54 +1 16:56:02 +1 16:56:09 q+ 16:56:13 (Noting that I favor well-formed, or at least restriction on triple-terms as objects only.) 16:56:36 +1 to niklas regarding well-formed 16:56:43 RESOLVED: Adopt minimal baseline https://github.com/w3c/rdf-star-wg/wiki/RDF-star-%22minimal-baseline%22 16:56:50 enrico: doubters should start an email discussion 16:57:20 The baseline abstract syntax has triple terms only in the object position. 16:57:21 ktk: discuss use cases next week 16:57:51 got to go now 16:58:13 ... or perhaps categorize some of what we have as "anti"-use-cases. 16:58:24 RRSAgent, draft minutes 16:58:25 I have made the request to generate https://www.w3.org/2024/07/18-rdf-star-minutes.html TallTed 16:58:43 pfps has left #rdf-star 17:04:44 Zakim, end meeting 17:04:44 As of this point the attendees have been pfps, Tpt, TallTed, niklasl, gtw, tl, AndyS, enrico, doerthe, Dominik_T, ora, AZ, ktk, Souri, eBremer, gkellogg 17:04:47 RRSAgent, please draft minutes 17:04:48 I have made the request to generate https://www.w3.org/2024/07/18-rdf-star-minutes.html Zakim 17:04:54 I am happy to have been of service, TallTed; please remember to excuse RRSAgent. Goodbye 17:04:54 Zakim has left #rdf-star 17:04:57 RRSAgent, bye 17:04:57 I see no action items