15:33:39 RRSAgent has joined #vcwg 15:33:43 logging to https://www.w3.org/2024/12/04-vcwg-irc 15:33:43 RRSAgent, make logs Public 15:33:44 please title this meeting ("meeting: ..."), ivan 15:33:54 Meeting: Verifiable Credentials Working Group Telco 15:33:55 Date: 2024-12-04 15:33:55 Agenda: https://www.w3.org/events/meetings/d03d7ee5-c761-4c67-825e-b483138033c7/20241204T110000/ 15:33:55 chair: brent 15:33:56 ivan has changed the topic to: Meeting Agenda 2024-12-04: https://www.w3.org/events/meetings/d03d7ee5-c761-4c67-825e-b483138033c7/20241204T110000/ 15:58:27 brent has joined #vcwg 15:58:32 hsano has joined #vcwg 15:58:59 TallTed has joined #vcwg 15:59:08 present+ 15:59:40 mandyv has joined #vcwg 15:59:41 present+ 16:00:15 present+ TallTed 16:00:19 present+ joe 16:00:31 present+ mandyv 16:00:45 present+ hsano 16:01:02 present+ wesley 16:01:31 present+ davidc 16:01:36 DavidC has joined #vcwg 16:01:43 present+ 16:02:23 KevinDean has joined #vcwg 16:02:29 present+ 16:03:01 present+ manu 16:04:10 scribe+ 16:04:40 JoeAndrieu has joined #vcwg 16:05:22 brent: Welcome, this is the VCWG meeting. We have our agenda -- ask if anyone wants to talk about anything else, and then controller document rename. 16:05:32 brent: As we go into the topic, I'll layout what I'm looking for there. 16:05:43 ivan: short question on something. 16:05:52 brent: ok, that should be fine. 16:06:05 bigbluehat has joined #vcwg 16:06:17 present+ 16:06:22 Wip has joined #vcwg 16:06:34 ivan: Our Chinese colleagues have received a question/request from Chinese Expert who defines Multikeys for SM2, seems to be a Chinese alternative to elliptic curves, can it be added to the table for Multikeys? 16:06:35 q+ 16:06:57 ivan: To be precise, question is around DID spec, but by now, the place is in the controller document. I don't know what the official answer is. 16:07:05 scribe+ 16:07:07 ack manu 16:07:20 selfissued has joined #vcwg 16:07:28 manu: All hats off, yes, it's easy to add it and I was expecting the request to come in at some point. 16:07:44 JennieM has joined #vcwg 16:07:51 ...I can add it to the controller document. It's widely recognized in China, it's supported by their national standards body. 16:08:03 Ivan: Raise an issue in the controller document repository. 16:08:06 scribe- 16:08:10 present+ 16:08:17 Topic: Controller Document Rename 16:08:19 brent: ok, seeing no one else on the queue, let's go into our topic for today. 16:08:29 present+ selfissued, meier, will 16:09:01 brent: I'm seeing 14 people on the call today, currently. 16:09:16 brent: anyone is free to make a proposal, anyone is free to queue, anyone is free to talk about other proposals people have made. 16:09:17 q+ 16:09:38 q+ 16:10:06 Procedural question, so perhaps better to take me first. 16:10:15 brent: my plan is to run queue, when a proposal is made, count the plusses, with 14 people, I expect to see at least 8 pluses and no minuses. If I see minuses, I'll ask if they see it's a formal objection, and if not, if there is a single or just a couple, we can move forward. That's what I'm leaning toward as far as guidance on whether to determine we have consensus or not. 16:10:36 ack KevinDean 16:11:08 KevinDean: Quick procedural question, regarding pluses, 14 people in meeting, some companies represented by more than one person, how does that work? Since company is registered, not individual, how do pluses and minuses work in those circumstance. 16:11:16 q+ to say process is clear on this on 16:11:23 present+ smccown 16:12:01 brent: Previously in the group, we've allowed people to indicate preference, if this were to turn into a vote, I'll have to be clear that individual companies need to be represented, if that's what people want to do today, happy to try to do the math to figure out how to do that. 16:12:08 ack manu 16:12:10 scribe+ 16:12:28 manu: I had proposed something about how we go about this today that is aligned with your proposal. 16:12:38 smccown has joined #vcwg 16:12:57 ...The first being that I don't think you can formally object to the title of a spec. The last time we asked for formal objections, but that's not what we're looking for today. 16:13:16 PROPOSAL: Close issue #100 with no further action on the renaming topic. 16:13:21 ...Today, we're looking for the proposal that has the last number of -1s. Those who -1 will be asked to clarify their objection. 16:13:43 q+ 16:13:50 ...I feel like formal objections for the title of the spec are totally off the table. The -1s indicate that you really don't like it but there should be no formal objection. 16:14:01 ...I'm fine with multiple people providing input and one vote per org. 16:14:31 ...I think we pick the one with the least number of objections, but I don't know if that's aligned with Brent's position. 16:14:45 brent: All I'm trying to say is that if the group decides on a different name, that's fine, in my view, I haven't seen that yet. 16:14:49 Brent: If the group all agree on a different name, that's fine. So far, in my view, I haven't seen that. Others say they have. 16:14:53 ack JoeAndrieu 16:14:53 JoeAndrieu, you wanted to say process is clear on this on 16:14:58 q+ to indicate that any "decision" is subject to the Formal Objection process 16:15:17 JoeAndrieu: I would like to follow process, when it gets to a point where we hae a vote, we might do a poll first, ultimately, I think it meets process -- one vote per member, IE counts as one vote. 16:16:15 JoeAndrieu: Other thing to push back to, you can't formally object to something, you can formally object to anything under process -- spoke w/ Florian and PlH about it -- not aligned, but Florian says anyone can object to anything, PlH noted he doesn't necessarily agree. 16:16:28 brent: for my benefit, say who will indicate preferences. 16:16:33 q+ 16:16:39 ack selfissued 16:17:17 selfissued: I'll note that when we ran the polls, no poll for a name change garnered a majority of the recipients. Clear signal to not change name to anything in particular, I think we should be done. Proposal to that effect in the chat that I'd like to run. 16:17:28 brent: I'll run through queue and then run the proposal. 16:17:29 ack TallTed 16:17:29 TallTed, you wanted to indicate that any "decision" is subject to the Formal Objection process 16:18:04 ack ivan 16:18:07 TallTed: What Joe said, the process says that any decision is subject to FO, that includes a decision to title a spec. It does seem like a heavy lift for that decision, but it is a decision. If someone wants to make that heavy lift, they can make it happen. 16:18:41 ivan: something I noted, when we come out of the call, is the decision final or do we have an implicit CfC via email until next meeting. 16:19:06 ivan: we can decide that with this decision, we close no matter the outcome, but we have to agree on that first. 16:19:25 brent: As much as I'd like to proceed in that way, my recollection is that any decision made has a week of time where people can object. 16:19:41 brent: I am hesitant to act in a way that differs from our operating mode. 16:19:50 PROPOSAL: Close issue #100 with no further action on the renaming topic. 16:20:02 +1 16:20:03 -1 16:20:05 -1 16:20:08 +0 16:20:16 -1 16:20:19 0 16:20:28 0 16:20:28 0 16:20:34 0 16:20:40 +0 16:21:38 brent: I believe we have 11 organizations, we'd have to see six positive indications and no negative indications for a proposal to be clearly resolved. 16:21:43 ivan: I counted 11 as well. 16:21:43 q+ 16:21:49 brent: This proposal doesn't resolve, we have a single +1 16:21:49 ack selfissued 16:22:16 selfissued: What that result tells me, given that it was predominance of zeros, that a lot of people don't care about this. 16:24:07 brent: I did not mean to imply that only folks w/ proposals can run things... anyone can join conversation about title of the specification. 16:24:22 brent: We have three proposals to put forward, want to invite people to speak to proposal to add themselves to the queue. 16:24:23 q+ 16:24:29 ack manu 16:24:40 manu: I just want to highlight some of the thinking behind each proposal. 16:24:54 ...The first is just to establish if we want to keep the current title. 16:25:05 present+ dlehn 16:25:06 ...If we see a lot of +1s and few or no -1s or 0s, we should keep it. 16:25:29 q+ to ask a process question 16:25:31 present+ steele 16:25:33 ...We may find ourselves in a situation where we don't have a title and so we change the title to "Identifier document". 16:26:19 ...Third, we try to align with what Dave Longley and maybe Ted said, is to try to get alignment with the folks who want to keep identifier document, and add "controller" to the title. Keep both as a compromise. 16:26:20 ack brent 16:26:20 brent, you wanted to ask a process question 16:27:03 brent: First is to recap for those that have recently joined, today's proposals... preferences are being made as organizations. Please coordinate with your company for single indication of preference or not. We can't assume 11, we're up to 13 or 12? 16:27:50 q+ 16:27:58 ack selfissued 16:28:01 brent: A question to the group -- if none of the proposals receive positive indications, of more than half of those organizations present, in my view, that's an indication that none of the proposals have consensus. I would love to hear what people in the group feel the most appropriate action as chair should be in that event. Inclination as chair is to say there is no consensus and move on. 16:28:07 selfissued: If there is no consensus, we should move on. 16:28:07 q+ 16:28:14 selfissued: then move to CR. 16:28:15 q+ to speak to weakest objections 16:28:15 ack manu 16:28:38 q+ 16:28:53 manu: If there's no proposal that we agree on, we keep the existing title. That's one of the arguments being made. 16:29:11 ...If we can't change the title to any other title, then we don't have a title that we agree to. 16:29:29 ...This is about more than the title. We need to do an IANA registration and we need a title as part of the registration. 16:29:55 ...If we don't have agreement on current or new terminology, my position is that we have no decision and we will sit here until we have one. 16:29:58 q+ to ask if it would be sufficient to name as resolved the proposal with the highest number of positive indications 16:30:18 ...That's my current interpretation, I realize that's not everybody else's, but I don't think there's a clean argument for what the fallback position should be. 16:30:50 ...The other way that other working groups deal with this is to proceed with the ones that have the least number of objections. If that turns into a formal objection, we deal with that then. 16:31:01 ack JoeAndrieu 16:31:01 JoeAndrieu, you wanted to speak to weakest objections 16:31:06 ...If we go with the one with the least number of objections and the most support, we can move forward. 16:32:03 JoeAndrieu: There is good language about the fallback in the W3C Process document, I think those are good rules to do the proposal brent, thank you. If those rules don't meet rules, then whole process where there is dissent, and we should move on (agree to move on). Groups should favor proposals that receive weakest objections. 16:32:04 ack selfissued 16:32:59 selfissued: I strongly disagree with what Manu said about there being no decision. Controller document came from two documents that had WG approval, one was VC DI and one was VC JOSE COSE. Manu and I as editors consolidated it leaving the name in place, the name was already in WG approved documents. Unless there is consensus to change the name, we already have a consensus name. 16:33:07 ack brent 16:33:07 brent, you wanted to ask if it would be sufficient to name as resolved the proposal with the highest number of positive indications 16:33:10 q+ to note we do not :) -- that's why we're here. 16:33:49 brent: If there is not clear consensus on a proposal, I'll declare as resolved the proposal with higest number of indications, least number of negative indications. I think that's in line with what people have said and W3C Process. I'd like to move to the proposals. 16:33:50 q- 16:34:07 brent: If it was clear we had consensus on the name, we would not be having this discussion. 16:34:29 PROPOSAL: Keep the "Controller Documents" title 16:34:31 +0 16:34:31 -1 16:34:35 -1 16:34:36 0 16:34:49 0 16:34:49 -1 16:34:52 -1 16:34:59 selfissued has joined #vcwg 16:35:00 +0 16:35:03 0 16:35:04 +1 16:35:07 present+ 16:35:38 present+ 16:35:43 brent: This proposal doesn't have consensus 16:36:04 PROPOSAL: Change the title of the "Controller Documents" to "Identifier Documents" 16:36:07 -1 16:36:08 +0 16:36:09 +1 16:36:10 -1 16:36:13 +1 16:36:13 +1 16:36:13 +1 16:36:18 +1 16:36:23 0 16:36:26 -0 16:37:15 brent: five +1s, 3 0s, and 2 -1s -- my suggestion is we run the other proposal to see how it compares before talking w/ people w/ indication of -1s. 16:37:25 PROPOSAL: Change the title of the "Controller Documents" to "Controllable Identifier Documents" 16:37:29 +1 16:37:29 0 16:37:30 +1 16:37:33 0 16:37:33 0 16:37:35 +1 16:37:37 0 16:37:42 +0 16:37:45 +1 16:37:46 -1 16:38:42 q+ 16:38:53 brent: the first proposal has more support and more objection. The first proposal is meeting qualification at beginning of call wrt. abstentions... obstentions do matter as they are not in support. 16:39:00 ack ivan 16:39:16 ivan: I voted zero everywhere, customary for company-based vote, W3C abstains. That's the reason I voted 0. 16:39:39 manu: Yes, it's non-blocking. 16:40:06 ...I know that Dave feels very strongly about "Identifier Document" in that it's not very descriptive. 16:40:17 brent: MikeJ, can you speak to your -1s? 16:41:07 selfissued: Identifier Document as a name is pretty meaningless, it's not evocative as a name as what it does -- titles should indicate what it does. This does not, the second name "Controllable Identifier Documents" as english is also strange, it raises the mental question of if there are "uncontrollable identifier documents" 16:41:08 q+ 16:41:10 q+ to support controllable identifier 16:41:13 selfissued: In what sense are they controllable? 16:41:14 q- 16:41:35 selfissued: The english result is non-sensical, I would object to having my name on either of those. 16:41:47 brent: Is either of your objections weaker than the other? 16:41:52 "Identifier Controller Document" 16:42:01 selfissued: They're both non-sensicle names, neither of those help. 16:42:07 ack JoeAndrieu 16:42:07 JoeAndrieu, you wanted to support controllable identifier 16:42:20 JoeAndrieu: I'd look at those two -1s as more objections, and would support that. 16:42:21 s/sensicle/sensible/ 16:42:35 selfissued your arguements equally apply to the name Controller Documents 16:43:10 JoeAndrieu: Also want to push back on what you're saying MikeJ, it's one of the hardest problems -- that's what we've been doing with DIDs -- whole point is through proofs, you show control over an identifier. That is, in fact, quite semantically accurate that describes controllable identifiers and how you establish/prove control. 16:43:17 PROPOSAL: Change the title of the document to "Identifier Controller Document" 16:43:29 brent: I've drafted as a proposal, TallTed's comment. 16:43:30 0 16:43:31 -1 16:43:33 0 16:43:37 -1 16:43:40 -1 16:43:46 0 16:43:49 -1 16:43:52 -1 16:43:55 0 16:43:59 +0 ... it was mostly an attempt to address mike's objection to the other names 16:44:17 PROPOSED PROPOSAL: Change the title to Verifiably Controlled Identifiers 16:44:49 q+ 16:45:07 brent: I'm going to run proposal as just the title. 16:45:23 TallTed: When resolved, do the full string. 16:45:50 selfissued: The problem with Controllable, in terms of the English, it raises the question of "uncontrollable identifiers" 16:45:51 q+ 16:45:58 ack selfissued 16:46:06 rogue identifiers are identifiers you don't control 16:46:07 ack manu 16:46:13 q= 16:46:21 q+ 16:46:24 selfissued: It has same linguistic problem, hope we don't go with that, the "controllable" vs. "uncontrollable" distinction is real. 16:46:46 manu: Just to respond, Mike, an uncontrollable identifier example is a Social Security Number. 16:47:12 ...There are many uncontrollable identifiers that we use: URNs, SSNs, tax ID numbers, these are all uncontrollable because you can't prove that you control it. 16:47:21 ...If you assert it to someone, you can't prove that you control it. 16:47:40 q+ to suggest options like "manifest" or "descriptor" instead of "document 16:47:44 ...The name "controllable identifier" is the thing that makes these types identifiers provable of having control over it. 16:48:10 ...That is what this specification establishes. It isn't a decentralized version of that, because it doesn't have the characteristics of a DID. 16:48:28 brent: We are at the tail end of our call, can we run proposals before we're done. 16:48:29 ack DavidC 16:48:49 ack JoeAndrieu 16:48:49 JoeAndrieu, you wanted to suggest options like "manifest" or "descriptor" instead of "document 16:48:51 DavidC: Wanted to address Mike's point of "rogue identifier" -- equally controllable as non-controllable -- think rogue identifier is spurious. 16:49:18 JoeAndrieu: Maybe shifting term around document might open up some options -- could run Controllable Identifier Descriptor? How control is done there. 16:49:44 PROPOSAL: "Controllable Identifier" 16:49:46 brent: Can you draft proposals for that? I'm going to run one Dave proposed, one Mike proposed, then we can try to get others in. 16:49:48 -1 16:49:49 +1 16:49:52 -1 16:49:54 0 16:49:58 0 16:50:03 -1 16:50:07 0 16:50:15 0 16:50:15 -0 16:50:17 0 16:50:40 PROPSAL: Verifiably Controlled Identifiers 16:50:47 +1 16:50:48 0 16:50:49 -1 16:50:52 0 16:50:58 -1 16:51:00 +1 16:51:00 -1 16:51:05 0 16:51:05 +0 16:51:06 0 16:51:37 PROPOSAL: Controllable Identifier Descriptor 16:51:42 0 16:51:45 0 16:51:46 0 16:51:51 +1 16:51:52 0 16:51:56 0 16:51:59 -1 we don't use descriptor anywhere else :( 16:52:08 0 16:52:08 -0 16:52:08 lol 16:52:14 +0 16:52:34 brent: I'm not seeing consensus on any of the last 3 proposals. 16:52:44 PROPOSAL: Controlled Identifier Documents 16:52:50 +1 16:52:50 0 16:52:50 +1 16:52:55 0 16:52:56 0 16:52:59 0 16:53:06 +0 16:53:08 0 16:53:13 0 16:53:35 brent: least objections, but active support for it is poor. Not seeing everyone's vote either. 16:54:28 -1 because it should be "Document" 16:54:31 brent: MikeJ? Comments? 16:54:55 q+ 16:55:05 -1 "Controlled Identifiers Document" 16:55:07 I would support Controlled Identifiers Document 16:55:07 selfissued: Should it be controlled "Identifiers"? 16:55:10 ack JoeAndrieu 16:55:27 JoeAndrieu: There is only one identifier in the document that is what the document is about. 16:55:38 selfissued: What about the keys? 16:55:47 I would support Controlled Identifier Document 16:55:54 PROPOSAL: Controlled Identifier Document 16:55:55 brent: Othere documents would hav etheir own documents that proved control. 16:55:55 0 16:55:57 +1 16:55:57 +1 16:56:02 0 16:56:03 +1 16:56:03 0 16:56:05 +1 16:56:06 0 16:56:07 +1 16:56:25 +1 16:57:15 brent: I'm not seeing anyone on the queue, not seeing anyone else making other proposals, this has 6 +1s, no indications against, clearly indicates consensus, we are resolved. 16:57:18 clap clap clap 16:57:34 RESOLVED: Change the title of the"Controller Document" to "Controlled Identifier Document" 16:58:07 brent: We have consensus. 16:58:27 brent: I hope to participate next week, but might not work out, next weeks call might be an issue. Please look for calendar invite update. 16:58:46 rrsagent, draft minutes 16:58:48 I have made the request to generate https://www.w3.org/2024/12/04-vcwg-minutes.html ivan