16:01:33 RRSAgent has joined #rdf-star 16:01:37 logging to https://www.w3.org/2023/09/28-rdf-star-irc 16:01:47 TallTed has joined #rdf-star 16:02:03 Agenda: https://www.w3.org/events/meetings/931e4e54-81ad-4aa3-a39f-84efe4b788c7/20230928T120000/ 16:02:03 clear agenda 16:02:03 agenda+ Scribe: Gschwend, Adrian (alternate: Pellissier Tanon, Thomas) 16:02:03 agenda+ Approval of last week's & TPAC minutes: -> 1 https://www.w3.org/2023/09/12-rdf-star-minutes.html 16:02:03 agenda+ Review of open actions, available at [2] 16:02:05 agenda+ Review of pull requests, available at [3] 16:02:07 agenda+ Semantics feedback 16:02:09 agenda+ Issue Triage, available at [4] 16:02:12 agenda+ Any Other Business (AOB), time permitting 16:02:35 scribe+ 16:02:38 present+ 16:02:39 present+ 16:02:42 present+ 16:02:44 zakim, next agendum 16:02:44 agendum 1 -- Scribe: Gschwend, Adrian (alternate: Pellissier Tanon, Thomas) -- taken up [from agendabot] 16:02:50 zakim, close item 1 16:02:50 I see a speaker queue remaining and respectfully decline to close this agendum, gkellogg 16:02:56 q? 16:02:58 Zakim, draft minutes 16:02:58 I don't understand 'draft minutes', ktk 16:03:02 present+ 16:03:05 RRSAgent, draft minutes 16:03:06 I have made the request to generate https://www.w3.org/2023/09/28-rdf-star-minutes.html ktk 16:03:14 RRSAgent, make minutes public 16:03:14 I'm logging. I don't understand 'make minutes public', ktk. Try /msg RRSAgent help 16:03:14 zakim, close 1 16:03:14 I don't understand 'close 1', gkellogg 16:03:22 zakim, close item 1 16:03:22 I see a speaker queue remaining and respectfully decline to close this agendum, gkellogg 16:03:25 q- 16:03:27 present+ 16:03:31 ack AndyS 16:03:38 zakim, close item 1 16:03:38 agendum 1, Scribe: Gschwend, Adrian (alternate: Pellissier Tanon, Thomas), closed 16:03:39 ack AndyS 16:03:40 present+ 16:03:40 I see 6 items remaining on the agenda; the next one is 16:03:40 2. Approval of last week's & TPAC minutes: -> 1 https://www.w3.org/2023/09/12-rdf-star-minutes.html [from agendabot] 16:03:44 zakim, open item 2 16:03:44 agendum 2 -- Approval of last week's & TPAC minutes: -> 1 https://www.w3.org/2023/09/12-rdf-star-minutes.html -- taken up [from agendabot] 16:04:01 present+ 16:04:04 present+ 16:04:04 Chair: ktk 16:04:07 enrico has joined #rdf-star 16:04:09 present+ 16:04:10 Present+ 16:04:26 present+ 16:04:27 regrets+ niklasl 16:04:39 Souri has joined #rdf-star 16:04:47 present+ 16:04:54 RRSAgent, draft minutes 16:04:56 I have made the request to generate https://www.w3.org/2023/09/28-rdf-star-minutes.html TallTed 16:04:57 RRSAgent, make logs public 16:04:58 TallTed has changed the topic to: RDF-star TPAC 2023-09-28 Agenda: https://www.w3.org/events/meetings/931e4e54-81ad-4aa3-a39f-84efe4b788c7/20230928T120000/ 16:05:00 present+ 16:05:02 RRSAgent, draft minutes 16:05:03 I have made the request to generate https://www.w3.org/2023/09/28-rdf-star-minutes.html TallTed 16:05:25 Last time: https://www.w3.org/2023/09/21-rdf-star-minutes.html 16:05:25 ktk: Minutes from last week https://www.w3.org/2023/09/28-rdf-star-minutes.html 16:05:33 https://www.w3.org/2023/09/21-rdf-star-minutes.html 16:05:52 PROPOSAL: Approve last week's minutes 16:05:56 +1 16:05:56 +1 16:05:58 +1 16:05:58 1+ 16:06:06 +1 16:06:06 +1 16:06:06 +1 16:06:06 +0 (was not present) 16:06:06 +1 16:06:09 +1 16:06:20 RESOLUTION: Approve last week's minutes 16:06:30 ktk: Minutes from TPAC https://www.w3.org/2023/09/12-rdf-star-minutes.html 16:07:04 ... pchampin applied the fixes. 16:07:52 PROPOSAL: Approve minutes 2023-09-12 16:07:54 +1 16:07:55 +1 16:07:57 +1 16:07:58 +1 16:07:59 +1 16:08:02 +1 16:08:15 +1 16:08:15 +1 16:08:17 +1 16:08:19 +1 16:08:21 +1 16:08:29 RESOLUTION: Approve minutes 2023-09-12 16:08:33 RRSAgent, draft minutes 16:08:34 I have made the request to generate https://www.w3.org/2023/09/28-rdf-star-minutes.html TallTed 16:08:41 zakim, next agendum 16:08:41 agendum 3 -- Review of open actions, available at -- taken up [from 2] 16:08:57 https://github.com/orgs/w3c/projects/20/views/3 16:09:33 s|available at|available at https://github.com/orgs/w3c/projects/20/views/3| 16:09:42 close #85 16:09:44 Closed -> action #85 https://github.com/w3c/rdf-star-wg/issues/85 16:10:03 subtopic #86 16:10:03 https://github.com/w3c/rdf-star-wg/issues/86 -> Action 86 Follow up to persons concerned regarding SPARQL EXISTS (on afs, pfps) due 2023-09-19 16:10:15 s/subtopic/subtopic:/ 16:10:21 pfps has joined #rdf-star 16:10:41 ktk: pfps seems to have completed this item. I also sent to Pavel. 16:11:43 close #86 16:11:44 Closed -> action #86 https://github.com/w3c/rdf-star-wg/issues/86 16:12:17 pfps: pchampin completed work for #92 16:12:18 https://github.com/w3c/rdf-star-wg/issues/92 -> Action 92 email where section headings should go (on pfps) due 2023-09-28 16:12:22 close #92 16:12:23 Closed -> action #92 https://github.com/w3c/rdf-star-wg/issues/92 16:12:36 pfps: Last week's meeting's scribe should have been me. 16:13:04 ... (it is correct, sorry) 16:13:45 close #93 16:13:45 Closed -> action #93 https://github.com/w3c/rdf-star-wg/issues/93 16:14:14 subtopic #19 16:14:15 https://github.com/w3c/rdf-star-wg/issues/19 -> Action 19 work with antoine and others to come up with a proposal for weak and strong compliance (on Antoine-Zimmermann, rdfguy) 16:14:23 az: I'm not sure how to move forward with this. 16:14:33 s/subtopic #19/subtopic: #19/ 16:14:58 ora: I'm not sure what we should do next, We need some statement about compliance. 16:15:13 ... I suggest everyone review this issue and review for next week. 16:15:49 ... az and I will go and clean up the comments. 16:16:01 az: Reading the whole thread would not be productive. 16:16:42 az: I'll work on cleaning this up. 16:17:00 ktk: Please send out an email when it's ready for review. 16:17:34 zakim, next agendum 16:17:34 agendum 4 -- Review of pull requests, available at -- taken up [from 3] 16:17:59 https://github.com/orgs/w3c/projects/20/views/4 16:18:15 s|available at|available at https://github.com/orgs/w3c/projects/20/views/4| 16:18:41 RRSAgent, draft minutes 16:18:43 I have made the request to generate https://www.w3.org/2023/09/28-rdf-star-minutes.html TallTed 16:18:49 subtopic: w3c/rdf-concepts#48 16:18:49 https://github.com/w3c/rdf-concepts/issues/48 -> Pull Request 48 Add base direction as a fourth element of literals. (by gkellogg) [i18n-tracker] [needs discussion] 16:18:54 q+ 16:18:54 q? 16:19:33 TallTed: I have a process comment. I think there should be a better way to present 2, 3, or four elements and the structure isn't quite clean enough. 16:20:27 Related is w3c/rdf-n-triples#34. 16:20:27 https://github.com/w3c/rdf-n-triples/issues/34 -> Pull Request 34 Adds BNF and text to extend LANGTAG to support base direction (by gkellogg) [spec:substantive] 16:20:53 q+ 16:20:59 ack TallTed 16:21:03 ack pfps 16:21:14 pfps: Is the datatype required of all RDF implementations. 16:21:15 s/process comment/comment-in-process on rdf-concepts#48/ 16:21:15 https://github.com/w3c/rdf-concepts/issues/48 -> Pull Request 48 Add base direction as a fourth element of literals. (by gkellogg) [i18n-tracker] [needs discussion] 16:21:28 gkellogg: I think so. 16:23:06 ... Eventually, should go in what's new in RDF 1.2 but now is in changes since 1.1. 16:23:21 pfps: Someone at some point should make sure this is correct. 16:23:59 ktk: Proposal is to is to accept the two PRs baring last minute editorial changes. 16:24:33 RRSAgent, draft minutes 16:24:34 I have made the request to generate https://www.w3.org/2023/09/28-rdf-star-minutes.html TallTed 16:25:10 s/is to is to/is to/ 16:25:10 PROPOSAL: Add base direction as a forth element of Literals, relating to w3c/rdf-concepts#48 and w3c/rdf-n-triples#34. 16:25:10 https://github.com/w3c/rdf-concepts/issues/48 -> Pull Request 48 Add base direction as a fourth element of literals. (by gkellogg) [i18n-tracker] [needs discussion] 16:25:10 gkellogg> +1 16:25:10 +1 16:25:11 0 - I still worry that this is neither necessary nor sufficient but it is "mostly harmless" 16:25:14 +1 16:25:17 +1 16:25:19 +1 16:25:19 +1 16:25:20 +1 16:25:24 +1 16:25:42 s/forth/fourth/ 16:26:14 +1 16:26:31 TallTed: Please, let's give w3c/rdf-concepts#48 until next week for editorial time. 16:26:39 +1 16:26:40 +1 16:26:44 +0 - I have to study it more carefully 16:26:46 RESOLUTION: Add base direction as a forth element of Literals, relating to w3c/rdf-concepts#48 and w3c/rdf-n-triples#34. 16:26:47 https://github.com/w3c/rdf-n-triples/issues/34 -> Pull Request 34 Adds BNF and text to extend LANGTAG to support base direction (by gkellogg) [spec:substantive] 16:26:47 https://github.com/w3c/rdf-concepts/issues/48 -> Pull Request 48 Add base direction as a fourth element of literals. (by gkellogg) [i18n-tracker] [needs discussion] 16:27:10 ktk: You can always open something new on this. 16:27:20 q+ 16:27:48 ktk: Some of the editorial PRs have been there for two weeks, and should probably just be merged. 16:28:16 ... w3c/rdf-turtle#39 16:28:17 https://github.com/w3c/rdf-turtle/issues/39 -> Pull Request 39 Unicode terminology and representation updates. (by gkellogg) [spec:editorial] 16:29:18 q? 16:30:09 gkellogg: I think we might want to come back on this in a subsequent PR 16:30:20 TallTed: I want to make it as clear as possible for new people. 16:30:28 q+ to suggest using both, if possible 16:30:31 q- 16:30:39 gkellogg: Maybe use character with a tool-tip and link to a definition. 16:31:01 TallTed: Multiple characters that roughly look the same can be a problem for non-english natives. 16:31:48 gkellogg: suggest we merged. 16:31:57 Similar characters can also be a problem for English natives - they don't even need to be all that similar. 16:32:19 subtopic: w3c/rdf-schema#27 16:32:20 https://github.com/w3c/rdf-schema/issues/27 -> CLOSED Pull Request 27 added rdf:JSON datatype (by domel) [spec:editorial] 16:32:24 ktk: This can be merged. 16:32:46 subtopic: w3c/sparql-query#123 16:32:46 https://github.com/w3c/sparql-query/issues/123 -> Pull Request 123 Fixes the definition of the Flatten function (by hartig) [spec:editorial] 16:33:02 olaf: I wanted to bring this one up for attention. 16:33:15 subtopic: w3c/sparql-query#124 16:33:16 https://github.com/w3c/sparql-query/issues/124 -> Pull Request 124 Improves the section about the Sum set function (by hartig) [spec:editorial] 16:33:23 q? 16:33:26 ack olaf 16:33:30 olaf: This is an in-progress proposal that I'd like feedback on. 16:33:51 niklasl has joined #rdf-star 16:33:55 ... If other co-editors can have a look, I'll make changes to similar functions (MIN, MAX, ...) 16:34:22 subtopic: w3c/sparql-query#110 16:34:22 https://github.com/w3c/sparql-query/issues/110 -> Pull Request 110 WIP: introduces a function called multiplicity to replace card[Ω](μ) (by hartig) 16:34:54 olaf: Please, if editors can also look at this proposal, I'll need to do more edits, but want to be sure it's generally acceptable. 16:35:03 q? 16:35:29 subtopic: w3c/rdf-concepts#66 16:35:30 https://github.com/w3c/rdf-concepts/issues/66 -> Pull Request 66 Updates rdf:JSON value space. (by gkellogg) [spec:substantive] 16:36:22 q+ 16:36:31 ack AndyS 16:36:53 AndyS: It might be helpful if we could see what the differences are in effect. 16:37:05 ... Particularly comparing how canonicalization works. 16:37:28 niklasl: can you present plus? 16:37:39 ... I don't think we've seen what the effect would actually be and what the tradeoffs are. 16:37:54 present+ 16:38:06 I-JSON https://www.rfc-editor.org/rfc/rfc7493.html 16:38:29 AndyS: I-JSON focuses on the JSON that processors agree on, rather than a flawed original representation. 16:38:55 q+ to commment on the lexical space 16:39:09 gkellogg: I'm not aware of any thing currently depending on the details of the value space. 16:39:15 ack pfps 16:39:15 pfps, you wanted to commment on the lexical space 16:39:32 pfps: My worry is that the value space will change, which is significant. It will change in a restrictive way. 16:39:32 draggett has joined #rdf-star 16:40:03 ... I also worry that the value space of I-JSON is not properly defined. 16:40:48 zakim, next agendum 16:40:48 agendum 5 -- Semantics feedback -- taken up [from agendabot] 16:41:21 ktk: I was at Semantics in Leipzig, which was interesting due to the interest in RDF-star. 16:41:44 ... There was some interest from Thomas Loertch who looked me up. 16:42:03 ... Dydra is becoming a W3C member and he plans to join the WG. 16:42:15 ... I assume he'll join via Dydra. 16:42:37 ... I also talked with another company that does a lot of work on exporting RDF to Neo4J. 16:42:49 ... The read some papers and have a lot of ideas. 16:43:25 ... I encouraged them to read the use cases and contact me or others as we're really interested in real-world applications 16:43:47 ... It was great to see people come up, it demonstrates interest in the community. 16:43:52 s/The read/They read/ 16:44:02 q? 16:44:13 zakim, next item 16:44:13 agendum 6 -- Issue Triage, available at -- taken up [from 4] 16:44:22 q+ 16:44:27 https://github.com/orgs/w3c/projects/20/views/5 16:44:36 s/baring/barring/ 16:45:02 AndyS: If we're doing a two week cycle on technical vs process, can we be sure what the topic is going to be for next week? 16:45:25 ... I'm happy for the chairs to choose the topic, but I want to be able to read the background material. 16:45:32 ktk: Noted. 16:46:27 close #54 16:46:29 Closed -> issue #54 https://github.com/w3c/rdf-star-wg/issues/54 16:47:49 ktk: we should remove the "duscuss-f2f" from those issues. 16:48:07 AndyS: The Echidna issue was paused due to random errors. 16:48:28 w3c/rdf-concepts#55 16:48:28 https://github.com/w3c/rdf-concepts/issues/55 -> Issue 55 Compare language tags after normalizing to lower case. (by gkellogg) [discuss-f2f] [needs discussion] [spec:enhancement] 16:50:38 at some time all issues need to be resolved so it is useful to have them all in a list somewherhe 16:51:02 s/somewherhe/somewhere/ 16:51:53 subtopic: w3c/rdf-concepts#55 16:52:08 AndyS: It's also a normalization case. 16:52:23 ... I emailed the Jena users list for feedback. 16:52:39 ... There are people for whom it's important. 16:52:53 ... Important is how to normalize 16:52:56 q+ 16:52:59 ack AndyS 16:54:00 ack gkellogg 16:54:50 enrico has joined #rdf-star 16:55:32 gkellogg: There's a question on how many triples get added to a graph. 16:55:47 AndyS: If we're going to do it, we should choose a normalization form. 16:56:23 ... A processor would place the literal into normalized form. 16:56:34 ktk: Let's follow up on the issue. 16:56:54 zakim, next item 16:56:54 agendum 7 -- Any Other Business (AOB), time permitting -- taken up [from agendabot] 16:57:02 ktk: is there a semantics TF tomorrow? 16:57:09 Thanks Adrian for chairing and Gregg for scribing. 16:57:10 enrico: Yes, I'll send out the update. 16:57:15 bye 16:57:25 RRSAgent, draft minutes 16:57:27 I have made the request to generate https://www.w3.org/2023/09/28-rdf-star-minutes.html ktk 16:57:33 olaf has left #rdf-star 16:57:58 regrets- niklasl 16:58:15 zakim, end meeting 16:58:15 As of this point the attendees have been rubensworks, ora, gkellogg, pchampin, gtw, olaf, AndyS, Dominik_T, pfps, Tpt, TallTed, draggett, niklasl, Souri_, ktk, AZ, enrico, Souri 16:58:18 RRSAgent, please draft minutes 16:58:20 I have made the request to generate https://www.w3.org/2023/09/28-rdf-star-minutes.html Zakim 16:58:26 I am happy to have been of service, gkellogg; please remember to excuse RRSAgent. Goodbye 16:58:26 Zakim has left #rdf-star 16:58:29 timbl has joined #rdf-star 16:58:51 rrsagent, bye 16:58:51 I see no action items previous meeting: https://www.w3.org/2023/09/21-rdf-star-minutes.html next meeting: https://www.w3.org/2023/10/05-rdf-star-minutes.html meeting: RDF-star Working Group Weekly Meeting