13:58:09 <RRSAgent> RRSAgent has joined #rch
13:58:14 <RRSAgent> logging to https://www.w3.org/2023/07/25-rch-irc
13:58:16 <Zakim> Zakim has joined #rch
13:58:34 <phila> meeting: RCH weekly meeting
13:58:45 <phila> Agenda: https://www.w3.org/events/meetings/493561b0-3a22-467f-8531-3c93ee3512f5/20230725T100000/
13:58:45 <agendabot> clear agenda
13:58:45 <agendabot> agenda+ Scribe (most recent first) Manu, DLongley, Seabass, kazue, PhilA, Gregg, markus_sabadello, pchampin, Ahmad, TallTed
13:58:45 <agendabot> agenda+ All minutes online available via https://www.w3.org/services/meeting-minutes?channel=rch&num=200
13:58:46 <agendabot> agenda+ Round the room updates
13:58:46 <agendabot> agenda+ Look at -> Open Issues https://github.com/w3c/rdf-canon/issues
13:58:49 <agendabot> agenda+ Review -> test suite https://w3c.github.io/rdf-canon/tests/
13:58:52 <agendabot> agenda+ Review implementation reports (link needed)!
13:58:54 <agendabot> agenda+ Timeline to CR (incl. 3 month period for TAG review)
13:58:57 <agendabot> agenda+ Meeting schedule back to every other Wednesday. DNM 2023-08-16
13:59:02 <phila> chair: phila
13:59:08 <phila> regrets+ Ivan
14:03:00 <seabass1> present+
14:03:01 <gkellogg> gkellogg has joined #rch
14:03:09 <phila> present+
14:03:12 <manu> present+
14:03:13 <dlongley> present+
14:03:13 <gkellogg> present+
14:03:24 <manu> q+ to note item on agenda
14:03:24 <seabass1> What do I come up as on IRC? seabass1?
14:03:29 <seabass1> I'll scribe
14:03:34 <yamdan> yamdan has joined #rch
14:03:43 <markus_sabadello> markus_sabadello has joined #rch
14:03:46 <markus_sabadello> present+
14:04:32 <seabass> present+
14:04:36 <seabass> scribe+
14:04:41 <yamdan> present+
14:04:52 <dlehn1> present+
14:05:04 <seabass> Obligatory https://xkcd.com/1782/
14:05:30 <manu> q+
14:06:05 <phila> ack manu
14:06:05 <Zakim> manu, you wanted to note item on agenda and to
14:06:05 <seabass> manu: There was an interesting email to the JSON-LD WG to the IoT group in W3C; they have requested a meeting at TPAC.
14:06:39 <seabass> manu: They're suggesting meeting on Monday, or another time which conflicts with the VCWG meeting
14:07:17 <seabass> s/IoT/WoT/
14:07:51 <TallTed> TallTed has joined #rch
14:08:51 <seabass> phila: Unless something goes wrong, we'll only have one agenda item: discussion of going to CR.
14:09:15 <manu> +1 to meet w/ WoT during RCH WG.
14:09:37 <seabass> phila: Let's combine with the WoT meeting then.
14:09:49 <TallTed> present+
14:10:15 <manu> q+
14:10:21 <phila> ack manu
14:10:50 <manu> Demonstration of Support for NIST-Compliant Selective Disclosure for Data Integrity Cryptosuites in VCWG: https://lists.w3.org/Archives/Public/public-vc-wg/2023Jul/0015.html
14:11:06 <seabass> manu: We've been gathering signatures for an open letter of support for NIST-compliant cryptosuites for Verifiable Credentials/Presentations
14:11:15 <manu> PRs to make the above concrete: https://lists.w3.org/Archives/Public/public-vc-wg/2023Jul/0016.html
14:11:40 <seabass> manu: As a result of this, two pull requests have been opened on the EDDSA test suite related to RDF Dataset Canonicalisation.
14:12:51 <seabass> manu: The other selective disclosure method is based on a mechanism called BBS.
14:14:49 <seabass> seabass: Is the letter a formal procedure?
14:15:17 <seabass> manu: No, it's an informal one. Some of the signatures include GS1 (thank you to Phil) and most recently GSMA.
14:16:06 <seabass> manu: The formal part is the PR review - if there are objects to the pull requests, then it might still be rejected.
14:16:16 <seabass> s/objects/objections/
14:16:57 <seabass> manu: It is marked as 'at-risk', so there is no guarantee that it will survive the CR phase.
14:18:03 <phila> Topic: Open Issues
14:18:06 <phila> https://github.com/w3c/rdf-canon/issues
14:19:02 <seabass> phila: If we don't get a response from the requested horizontal reviews, we can continue to go to CR without delay.
14:19:59 <seabass> phila: Manu, are you still able to write the history section given your workload?
14:20:15 <gkellogg> q+
14:20:20 <seabass> manu: Yes, eventually I will write it but unlikely in the next few weeks.
14:20:47 <gkellogg> https://github.com/w3c/rdf-canon/issues/98#issuecomment-1649889042
14:20:59 <phila> Subtopic: https://github.com/w3c/rdf-canon/issues/98
14:21:10 <pchampin> scribe+
14:21:29 <pchampin> seabass: I've not used respec in this depth before.
14:22:06 <manu> q+
14:22:16 <pchampin> ... the JS code is such that the image will be inserted several time -- can we improve that?
14:22:44 <pchampin> gkellogg: all SVGs are commited by hand, there is no automated pipeline that spits them out
14:23:00 <pchampin> ... you mentioned the list of contributors; this one uses a script that requires an API key
14:23:11 <pchampin> ... it has not been included in a pipeline
14:23:12 <manu> q+ to note that images checked in multiple times is ok -- also respec-mermaid exists, SVGs are text, etc.
14:23:50 <pchampin> ... we do have actions that run on any commit/PR (e.g. updating the tests)
14:24:18 <phila> ack manu
14:24:18 <Zakim> manu, you wanted to note that images checked in multiple times is ok -- also respec-mermaid exists, SVGs are text, etc.
14:24:22 <pchampin> ... this could lead to extra commits
14:24:49 <pchampin> manu: recommends against plantuml, it generates ugly diagrams compared to what Dan has produced
14:25:12 <pchampin> ... different WGs work differently
14:25:35 <pchampin> ... let's just check-in the image file, it won't change that much anyway
14:26:16 <pchampin> ... the other thing we could do: use the respec plugin for mermaid to generate the diagram (but again, will not look as good)
14:26:35 <pchampin> ... SVG is text; we can fine-tune them by hand
14:27:11 <pchampin> ... I suggest seabass to not spend time on this
14:27:38 <manu> +1 to do this in SVG format, easier to do accessible descriptions for that.
14:27:42 <phila> ack gkellogg
14:27:43 <seabass> https://github.com/svg/svgo
14:27:45 <pchampin> seabass: ok; I can suggest svgo which is an XML-formatter fine-tuned for SVG
14:27:53 <manu> oh! totally agree w/ gkellog.
14:28:02 <manu> I didn't know that's what we were discussing.
14:28:15 <manu> (we shouldn't reproduce this diagram for every example)
14:28:16 <pchampin> gkellogg: this diagram will only occur onces; from it you can interpret other examples
14:29:06 <gkellogg> #110
14:29:14 <seabass> scribe+
14:29:21 <phila> Subtopic: https://github.com/w3c/rdf-canon/issues/114
14:29:23 <gkellogg> s/110/114/
14:29:42 <manu> q+ to note how we usually do this.
14:29:56 <seabass> gkellogg: I wasn't able to find a coherent list of contributors from the CCG to acknowledge.
14:30:10 <phila> ack manu
14:30:10 <Zakim> manu, you wanted to note how we usually do this.
14:31:02 <seabass> manu: I have a script that will pick out the names automatically. I can share it if my workload permits.
14:32:30 <seabass> seabass: We could ask the entire current CCG if any members were involved in the past.
14:32:50 <seabass> TallTed: The W3C will have records of who was involved because of IPR.
14:33:11 <seabass> phila: That would include many more people than who were involved directly in our project.
14:34:58 <phila> Topic: Review Test Suite https://w3c.github.io/rdf-canon/tests/
14:35:02 <seabass> phila: I believe we have finished our review of the currently opened issues, and we have no issue to discuss here.
14:35:42 <gkellogg> q+
14:35:49 <phila> ack gkellogg
14:35:54 <seabass> phila: Is the test suite complete and is it still correct?
14:36:49 <seabass> gkellogg: Test suites are never truly complete, and we might still see requests for new tests to be added even after the end of our WG. However, the test suite has everything we wanted in it and there are two independent implementations.
14:37:07 <gkellogg> https://w3c.github.io/rdf-canon/reports/
14:38:18 <pchampin> scribe-
14:38:43 <pchampin> indeed, I did run the last test suite with my latest code, and got 100% passed
14:39:14 <pchampin> I'll submit my new test report as soon as I make a new release of Sophia
14:40:03 <yamdan> I'll submit a report of my implementation later
14:40:13 <manu> q+
14:40:19 <seabass> phila: Implementations written by those outside of this WG are worth ten times what an internal implementation is worth.
14:40:24 <phila> ack manu
14:40:35 <phila> Topic: Implementation Reports
14:41:16 <dlongley> the people who wrote these may update them: https://github.com/w3c/rdf-canon/wiki/List-of-available-implementations
14:41:37 <seabass> seabass: Has SpruceID committed to writing an implementation?
14:41:48 <seabass> manu: Charles Lehner of SpruceID has already written one.
14:42:09 <seabass> phila: yamdan, do you have an implementation?
14:42:20 <seabass> yamdan: Yes, and I will submit my test report later.
14:42:25 <manu> q+ to ask yamdan about impl language
14:42:44 <phila> ack manu
14:42:44 <Zakim> manu, you wanted to ask yamdan about impl language
14:42:56 <seabass> manu: What language is it in?
14:43:03 <dlongley> q+
14:43:05 <seabass> yamdan: It's written in Rust.
14:43:16 <phila> ack dlongley
14:43:16 <TallTed> gkellogg -- I've added the links you muttered about being missing. Now on both https://w3c.github.io/rdf-canon/ and https://github.com/w3c/rdf-canon#readme
14:43:40 <pchampin> +1 manu, I have a plan to publish a WASM version of my implementation
14:44:23 <seabass> dlongley: we have a list of implementations in the 'wiki' on our GitHub repository, too.
14:46:04 <phila> Topic: Timeline to CR (incl. 3 month period for TAG review)
14:46:52 <seabass> phila: We invited the TAG to review our specification on the 7th of June. They have three months to get back to use. If we don't hear from them, we are still clear to go to TPAC.
14:47:23 <seabass> s/use/us/
14:50:30 <seabass> phila: I'll stick with 16th and 30th, then at TPAC. The other ones will be cancelled as there is not enough to fill their agendas.
14:50:54 <phila> Topic: DNM 2023-08-16
14:51:47 <phila> RRSAgent, make logs public
14:51:59 <phila> RRSAgent, draft minutes
14:52:00 <RRSAgent> I have made the request to generate https://www.w3.org/2023/07/25-rch-minutes.html phila
15:02:25 <phila> zakim, end meeting
15:02:25 <Zakim> As of this point the attendees have been seabass, phila, manu, dlongley, gkellogg, markus_sabadello, yamdan, dlehn, TallTed
15:02:27 <Zakim> RRSAgent, please draft minutes
15:02:29 <RRSAgent> I have made the request to generate https://www.w3.org/2023/07/25-rch-minutes.html Zakim
15:02:35 <Zakim> I am happy to have been of service, phila; please remember to excuse RRSAgent.  Goodbye
15:02:36 <Zakim> Zakim has left #rch
15:02:44 <phila> RRSAgent, please excuse us
15:02:44 <RRSAgent> I see no action items