15:00:03 <RRSAgent> RRSAgent has joined #rch
15:00:03 <RRSAgent> logging to https://www.w3.org/2022/11/23-rch-irc
15:00:05 <Zakim> RRSAgent, make logs Public
15:00:06 <Zakim> please title this meeting ("meeting: ..."), phila
15:00:18 <phila> Meeting: RCH WG bi-weekly
15:00:22 <gkellogg> gkellogg has joined #rch
15:00:27 <gkellogg_> gkellogg_ has joined #rch
15:01:21 <AndyS> AndyS has joined #rch
15:01:43 <yamdan> yamdan has joined #rch
15:01:56 <AndyS> present+
15:02:11 <gkellogg_> present+
15:02:25 <ivan> present+
15:02:25 <yamdan> present+
15:02:42 <phila> present+
15:02:53 <aalobaid> aalobaid has joined #rch
15:05:10 <pchampin> present+
15:05:23 <AndyS> zakim, who is here
15:05:24 <Zakim> AndyS, you need to end that query with '?'
15:05:25 <TallTed> present+
15:05:37 <phila> -> https://www.w3.org/TR/2022/WD-rdf-canon-20221124/ FPWD
15:05:37 <AndyS> zakim, who is here?
15:05:37 <Zakim> Present: AndyS, gkellogg_, ivan, yamdan, phila, pchampin, TallTed
15:05:39 <Zakim> On IRC I see aalobaid, yamdan, AndyS, gkellogg_, RRSAgent, markus_sabadello, phila, Zakim, ivan, TallTed, Tpt, dlehn1, manu, dlongley, pchampin
15:05:51 <manu> Thank you Gregg and PA!
15:06:03 <manu> (for publication of FPWD)
15:06:05 <ivan> q?
15:06:12 <pchampin> q+
15:06:15 <aalobaid> Phil: the draft has been published
15:06:29 <aalobaid> Ivan: It is not yet published
15:06:31 <manu> s/(for publication of FPWD)//
15:06:38 <manu> s/Thank you Gregg and PA!//
15:06:47 <aalobaid> Phil: it is about to be published
15:06:49 <pchampin> q-
15:06:51 <gkellogg_> https://www.w3.org/TR/2022/WD-rdf-canon-20221124/
15:07:09 <aalobaid> Phil: it will be published tomorrow
15:07:22 <AndyS> scribe: aalobaid
15:07:27 <aalobaid> present+
15:07:27 <markus_sabadello> present+
15:08:41 <phila> Topic: IIW
15:08:49 <ivan> q+
15:09:01 <ivan> q-
15:09:26 <manu> q+ to report out on Data Integrity usage (and RDF Dataset Canonicalization) in JFF Plugfest #2 interop
15:09:43 <aalobaid> Phil: Mark, you can explain to everybody about the recent event.
15:10:06 <aalobaid> Mark: There were many sessions about harmonisation and different creditional formats.
15:10:06 <phila> -> https://internetidentityworkshop.com IIW website
15:10:24 <aalobaid> Mark: another big topic about Web5.
15:11:03 <aalobaid> Mark: Another topic is about identify, signatures, and much more. But nothing specific to this working group.
15:11:42 <TallTed> we've skipped web4, and web3 is still being defined as well
15:13:43 <aalobaid> Dan: I had to 2 sessions. One is about SPARQL endpoint and signatures.
15:14:05 <aalobaid> Dan: and anonymisation about SPARQL results.
15:15:03 <aalobaid> Dan: The second is about the canonicalization (but only as a black box). Mainly from the user perspective.
15:17:02 <manu> Plugfest related to RCH work item output -- https://docs.google.com/presentation/d/19GmJ3bLMrbVadesnkmsWaaUr-U71Y9Kr775tZvgs-xI/edit
15:17:03 <aalobaid> Manu: Companies participating and using verified signatures.
15:18:11 <manu> Verifiable Credential Data Integrity 1.0 FPWD: https://w3c.github.io/vc-data-integrity/
15:18:18 <manu> https://www.w3.org/TR/vc-data-integrity/
15:18:25 <aalobaid> Manu: 17 credentials issuers.
15:18:45 <manu> Transition EdDSA to VCWG in next few weeks: https://w3c-ccg.github.io/di-eddsa-2020/
15:19:12 <manu> Finally, there is a active test suite with multiple implementers: https://w3c-ccg.github.io/di-ed25519-test-suite/#Ed25519Signature2020%20(issuer)
15:19:50 <aalobaid> Manu: We will have more test suites from the participants.
15:22:11 <phila> Topic: Issue
15:22:31 <aalobaid> phila: Let us talk about the issues that are recently updated.
15:22:56 <aalobaid> phila: Greg. Are there any issues that you would like the group to discuss?
15:23:36 <phila> -> https://github.com/w3c/rdf-canon/pull/40 PR 40
15:25:19 <aalobaid> phila: Any comments on this issue?
15:25:49 <aalobaid> ivan: There is a loop in the algorithm that is unecessary.
15:25:50 <manu> q+ to ask if Longley has weighed in on this?
15:26:02 <manu> q-
15:26:17 <aalobaid> ivan: We had a discussion about that in issue 23.
15:26:42 <aalobaid> ivan: Dave and I agreed that this is unnecessary.
15:27:20 <aalobaid> gkellogg_: I took the opportunity to add labels to everystep in the algorithm.
15:27:57 <aalobaid> ivan: we need to relabel the steps if the algorithms is changed.
15:28:07 <phila> Proposed Resolution: Accept PR40 that removes the 'simple' processing loop, and close issue 23
15:28:12 <manu> +1
15:28:16 <ivan> +1
15:28:17 <gkellogg_> +1
15:28:32 <pchampin> +1
15:28:35 <phila> Proposed Resolution: Accept PR40 that removes the 'simple' processing loop, and prepare to close issue 23
15:28:45 <manu> +1
15:28:50 <aalobaid> gkellogg_: there is some referencing issues that need to be resolved.
15:29:31 <aalobaid> ivan: It is a good practice to keep a list of changes to the issue regardless whether the issue is opened or not.
15:29:48 <aalobaid> gkellogg_: I will take care of this.
15:29:49 <yamdan> +1
15:30:04 <phila> +1
15:30:12 <phila> Resolution: Accept PR40 that removes the 'simple' processing loop, and prepare to close issue 23
15:30:18 <aalobaid> phila: any objections?
15:30:24 <aalobaid> phila: resolved
15:30:33 <gkellogg_> subtopic: https://github.com/w3c/rdf-canon/issues/37
15:31:28 <aalobaid> gkellogg_: There is some ambiguity about sorting quads
15:31:47 <aalobaid> gkellogg_: there is no formal definition about canonicalised quads
15:32:14 <AndyS> q+
15:33:24 <aalobaid> gkellogg_: nquads separaters should be a line terminator or a dot?
15:33:36 <phila> ack AndyS
15:35:07 <phila> gkellogg_: There's a section in the N triples spec that defines a canonical form. The basic spec allows any amount of white space between components
15:35:15 <phila> ... but you can't have new lines outside the grammar
15:35:33 <phila> ... the canonical form fixes that as a single space character and doesn't discuss newline separator
15:36:04 <phila> ... So erratum would be to include that newline character as part of the canonical form or to describe it only in the canonical form of a document
15:36:26 <AndyS> q+
15:36:38 <TallTed> we might be drilling too far into the details for the moment...
15:36:48 <phila> ... Where a certain no.of quads are used to create a hash - that will help clarify a specific form of these quads without the newline separaor and the terminator
15:37:15 <aalobaid> AndyS: I agree with Greg's suggestion.
15:38:15 <phila> ack AndyS
15:38:35 <aalobaid> TallTed: Should we dive into the details about this here.
15:39:30 <aalobaid> TallTed: Vocally discussing this here might not be enough.
15:39:39 <aalobaid> phila: Understood
15:39:56 <phila> Subtopic: https://github.com/w3c/rdf-canon/issues/10
15:40:30 <aalobaid> phila: What is the criteria about choosing?
15:41:22 <manu> q+ to note we're not at a fork in the road...
15:41:31 <aalobaid> gkellogg_: I don't think it is not up to me to choose the approach.
15:41:54 <aalobaid> manu: I agree. We don't have to choose one or the other.
15:41:58 <phila> ack manu
15:41:58 <Zakim> manu, you wanted to note we're not at a fork in the road...
15:43:15 <aalobaid> manu: If we decided to do something new, we can do it without disturbing the existing specs
15:43:16 <AndyS> q+
15:43:34 <pchampin> RRSAgent, draft minutes
15:43:34 <RRSAgent> I have made the request to generate https://www.w3.org/2022/11/23-rch-minutes.html pchampin
15:43:49 <manu> q+ to note that it's important to write down what we're optimising for in the current work.
15:44:31 <gkellogg_> q+ to discuss a new topic: granularity and approval of future PRs leading to WD publication.
15:44:31 <aalobaid> phila: If there is nothing pushing for a change, then we don't have to do it yet.
15:44:58 <phila> q?
15:45:01 <phila> ack AndyS
15:45:54 <phila> ack next
15:45:55 <Zakim> manu, you wanted to note that it's important to write down what we're optimising for in the current work.
15:45:56 <aalobaid> AndyS: Maybe we can add more details about the algorithms.
15:46:31 <phila> q+ to support Manu
15:46:51 <aalobaid> manu: It is valuable to write down what we optimise (e.g., time complexity, proofs, ...)
15:46:56 <phila> ack next
15:46:57 <Zakim> gkellogg_, you wanted to discuss a new topic: granularity and approval of future PRs leading to WD publication.
15:47:09 <phila> ack me
15:47:09 <Zakim> phila, you wanted to support Manu
15:48:02 <aalobaid> phila: It is good to include the reasoning for the decisions.
15:49:00 <aalobaid> phila: I would like to see a section in the document about the reasons behind the taken decisions.
15:49:58 <phila> Topic: Granularity of pull requests
15:50:34 <aalobaid> gkellogg_: frequency of pull requests and authority for merging pull requests. Maybe we need to discuss the dynamics of this.
15:51:42 <manu> Phil's explanation of the granularity has been my experience.
15:51:55 <aalobaid> phila: I think merging several pull requests in the same day will be considered a single change.
15:52:02 <manu> q+
15:52:08 <phila> ack manu
15:52:45 <aalobaid> manu: I have the same experience and I've never had problems with making several merge requests.
15:52:52 <pchampin> q+
15:53:47 <phila> ack pchampin
15:53:59 <aalobaid> phila: If it is an editorial think, we can go for it greg.
15:53:59 <TallTed> Editors are allowed to edit. :-)
15:54:34 <manu> +1 to depend on Editor's judgement on merging to main. Don't merge unless you're very confident that there won't be objections... make sure you have multiple reviews, etc. :) -- but the Editors already know how to do all of this and have demonstrated to do it well over the past several years. :)
15:54:58 <pchampin> +1
15:55:33 <aalobaid> pchampin: I agree that the editors can do changes that is not too large.
15:55:53 <aalobaid> phila: Editors should be allowed to edit.
15:56:11 <aalobaid> phila: Thanks everyone
15:56:25 <phila> RRSAgent, draft minutes
15:56:25 <RRSAgent> I have made the request to generate https://www.w3.org/2022/11/23-rch-minutes.html phila
15:56:55 <pchampin> RRSAgent, draft minutes
15:56:55 <RRSAgent> I have made the request to generate https://www.w3.org/2022/11/23-rch-minutes.html pchampin
15:56:59 <phila> regrets+ Kazue
15:57:06 <phila> RRSAgent, draft minutes
15:57:06 <RRSAgent> I have made the request to generate https://www.w3.org/2022/11/23-rch-minutes.html phila
15:57:48 <phila> zakim, end meeting
15:57:48 <Zakim> As of this point the attendees have been AndyS, gkellogg_, ivan, yamdan, phila, pchampin, TallTed, aalobaid, markus_sabadello
15:57:50 <Zakim> RRSAgent, please draft minutes
15:57:50 <RRSAgent> I have made the request to generate https://www.w3.org/2022/11/23-rch-minutes.html Zakim
15:57:54 <Zakim> I am happy to have been of service, phila; please remember to excuse RRSAgent.  Goodbye
15:57:58 <Zakim> Zakim has left #rch
15:58:10 <phila> RRSAgent, you are excused
15:58:10 <RRSAgent> I'm logging. I don't understand 'you are excused', phila.  Try /msg RRSAgent help
16:05:12 <pchampin> s|-> https://github.com/w3c/rdf-canon/pull/40 PR 40|https://github.com/w3c/rdf-canon/pull|
16:05:16 <pchampin> RRSAgent, draft minutes
16:05:16 <RRSAgent> I have made the request to generate https://www.w3.org/2022/11/23-rch-minutes.html pchampin
16:06:40 <pchampin> s|https://github.com/w3c/rdf-canon/pull|Subtopic: https://github.com/w3c/rdf-canon/pull/40|
16:07:27 <pchampin> RRSAgent, draft minutes
16:07:27 <RRSAgent> I have made the request to generate https://www.w3.org/2022/11/23-rch-minutes.html pchampin
16:07:41 <gkellogg> gkellogg has joined #rch
16:08:17 <pchampin> dlongley, you missed the change of time for the meeting
16:08:22 <pchampin> we just finished
16:08:41 <dlongley> pchampin: thanks ... yeah, my calendar is *still* wrong, trying to figure it out
16:08:55 <dlongley> i remember we discussed it now, but i foolishly relied on my calendar tooling :)
16:09:07 <pchampin> are you using the W3C calendar and its ICS stream?
16:09:38 <dlongley> yeah, i subscribed to: https://www.w3.org/groups/wg/rch/calendar/export
16:10:12 <dlongley> i've already deleted it and reimported it as well... going to do that again now
16:11:15 <dlongley> ok, second time is the charm, apparently.
16:11:25 <dlongley> pchampin: i have it working now ... not sure if there was a caching issue or what.
16:12:11 <dlongley> and it only shows in the main calendar app, not the gmail sidebar ... but, that's not a problem with the W3C calendar i'm sure.
16:12:16 <dlongley> tools are hard.
16:12:57 <pchampin> the W3C calendar is still relatively new, so I'm watching for toothing problems
16:25:10 <gkellogg> gkellogg has joined #rch
16:41:49 <gkellogg> gkellogg has joined #rch
16:48:10 <gkellogg> gkellogg has joined #rch
16:59:24 <gkellogg> gkellogg has joined #rch
17:19:10 <gkellogg> gkellogg has joined #rch
17:23:05 <gkellogg_> gkellogg_ has joined #rch