[MINUTES] VCWG Barcodes and Data Integrity 2026-08-25

The VCWG Barcodes and Data Integrity task force met on August 25, 2026, to
discuss various agenda items including time zone conflicts, publishing
threat models, VC forgery defense, PR reviews, data integrity updates, and
VC barcode updates. The meeting focused on making progress on
specifications and tooling, with discussions ranging from logistical
challenges like scheduling to technical details of various specifications.
A key theme was ensuring consistency and efficiency in tooling and
specification development across the group's work.

*Topics Covered:*

   - *Time Zone Conflict Discussion:* The group discussed potential
   scheduling conflicts, particularly concerning Greg's semi-retirement and
   Ivan Herman's evening availability, and decided to gather more information
   via a doodle poll to find a suitable meeting time.
   - *Publishing Threat Models:* The team reviewed the technical hurdles
   for publishing threat models as multi-chapter specifications, with a focus
   on adapting existing tooling to support this structure and ensuring a
   unified approach across all threat models.
   - *VC Forgery Defense:* The discussion centered on handling a spam issue
   in the repository, with the group agreeing to report the user to GitHub and
   investigate repository-level blocking mechanisms.
   - *PR Review and Merge:* The group discussed the criteria for merging a
   Pull Request that had been open for several weeks, with the editor given
   the discretion to merge if they felt the comments had been adequately
   addressed.
   - *Data Integrity Updates:* Greg Bernstein's updates were discussed,
   including outstanding PRs for common algorithms, selective disclosure, and
   quantum-resistant ECDSA. The group also addressed a whitespace issue in a
   PR and the timely merging of the data integrity specification, alongside
   the potential integration of a new contributor focused on post-quantum
   cryptography.
   - *VC Barcodes Updates:* The task force addressed the need to move the
   XI crypto suite and the bit string status list entry to more appropriate
   locations before horizontal reviews begin, and discussed the process for
   publishing new versions of specifications.
   - *External Deployments:* There was a brief mention of potential
   large-scale deployments of verifiable credential barcodes by organizations
   like the World Bank, with a commitment to gather more information.
   - *XML Signature Work:* Ivan Herman raised awareness of ongoing work at
   W3C/IETF on re-opening XML signature work with quantum-resistant keys, and
   the group decided to monitor this development rather than actively engage
   at this stage.

*Action Items:*

   - Send out a doodle poll to find a new meeting time that accommodates
   Greg and Ivan Herman.
   - Manu Sporny and Ivan Herman to work on technical details for adapting
   tooling to publish threat models as multi-chapter specifications.
   - Wesley Smith to report the spam issue on GitHub and investigate
   repository-level user blocking.
   - Wesley Smith to incorporate wording tweaks and merge the discussed PR
   after the call.
   - Wesley Smith to investigate and potentially fix the whitespace issue
   in the data integrity PR.
   - Ivan Herman and Manu Sporny to investigate the best location for the
   XI crypto suite and bit string status list entry within specifications.
   - Wesley Smith to initiate the process for a First Public Working Draft
   of Bitstream status lists 1.1.
   - Elaine Wooton to endeavor to get more information about the World
   Bank's verifiable credential barcode deployment.
   - Wesley Smith to investigate the status of Anthony, a new contributor
   focused on post-quantum cryptography, and ensure they are integrated into
   the meeting invites.

HTML:
https://meet.w3c-ccg.org/archives/w3c-vcwg-barcodes-and-data-integrity-2026-08-25.html

Video:
https://meet.w3c-ccg.org/archives/w3c-vcwg-barcodes-and-data-integrity-2026-08-25.mp4

[image: W3C] <https://www.w3.org/>
VCWG Barcodes and Data Integrity 25 August 2026 Attendees

Present

Dave Lehn, Dave Longley, Elaine Wooton, Ivan Herman, Manu Sporny, Ted
Thibodeau Jr, Wesley Smith

Regrets

-

Chair

-

Scribe

transcriber
Contents

   1. Time Zone Conflict Discussion <#15b6>
   2. Publishing Threat Models <#f400>
   3. VC Forgery Defense <#41dc>
   4. PR Review And Merge <#d76b>
   5. Data Integrity Updates <#ead2>
   6. VC Barcodes Updates <#b7a7>

Meeting minutes Time Zone Conflict Discussion

Ivan Herman: Thanks.

Wesley Smith: Hey folks, I'm g to give it a minute or two for people to
trickle

Wesley Smith: All right. Hi everybody. Welcome to the August 25th, 2026
meeting of the barcodes and data integrity task force. the agenda for today
is much the same as normal. We will go through announcement process and
introduction items. and then we will spend time on the barcodes for defense
and data integrity specs as time allows. does anybody have any process
introduction or announcement items for the group today? All right. does
anybody have any Mon, go ahead.

Manu Sporny: Yeah, sorry.

Wesley Smith: Yeah, sounds good.

Manu Sporny: I didn't know where to put this, but maybe under pro we've
lost Greg because he's semi-retired and he's like I don't want to wake up
this early and come to this call, which I can totally appreciate. I am
wondering I've asked him…

Ivan Herman: Okay.

Manu Sporny: if us moving the call would get him here. it would have to be,
9:00 a.m. to 12 p.m. Pacific, which then moves it a bit late for our
European friends. just I'm wondering if the group should talk about that
today. and that's it.

Wesley Smith: Any other announcement, process or introduction or similar
items? All right, let's go ahead and talk about that then.

Wesley Smith: Anybody have thoughts on the zone time conflict issue?

Wesley Smith: I will note that I'm happy to move this call personally. I
have a pretty flexible schedule on Tuesdays if the hope is for it to remain
on Tuesdays. M. Go ahead. Sorry, Ivon. Go ahead.

Ivan Herman: Yeah, I don't want to compete with Greg,…

Ivan Herman: but I'm also semi-retired and I am not really willing to have
a call after 6:00 my time in the evening. for all kinds of reasons. I try
to keep my evenings free. I know this sounds crazy because this means it
you guys have to choose between myself and Greg, but I think Greg is more
important.

Wesley Smith: Mon, go ahead.

Ivan Herman: But I'm just saying

Manu Sporny: I don't know about more important Avon, but yes, she having to
choose, which is not good. We're having to choose between two completely
reasonable requests from two semi-retired people. So, I think that's it. I
mean, the only reason I'm concerned about Greg not being on the calls is
because he is actively editing some of these documents. but he might
basically be like, I don't need to be on the calls to make progress and
that's what he's been doing and it hasn't really slowed him down. at the
same time Ivonne it's very useful to have you on these calls especially on
the first call because we end up talking about a variety of things like
threat model and how are we going to get the publication process done and
it's important for you to be there.

Manu Sporny: I think everyone else can move probably the calls around, but
So, I think we should just wait to hear back from Greg and see if he's
like, "Yeah, the time is just not working for me." But if you moved it, I
would show up. I'll note that Tuesdays are completely packed with standards
calls. I can't move it to any other time on Tuesday. I will not be able to
make it.

Manu Sporny: The only other days that are open for me are Mondays and
Fridays. sorry. If we move it to noon Eastern, I can make most of the days,
but it conflicts with the CCG call on Tuesdays. do Mondays, could do
Wednesdays, could do Thursdays. so …

Manu Sporny: I suggest let's hear back from Greg and then if he's like,
"Yes, I want to come to the calls. It's just a bad time for me." Then we
can send out a doodle poll and maybe we find a time, but almost certainly
we will not find a time that works for go ahead 10.

Ted Thibodeau Jr: I was going to suggest that the doodle poll be started
with the information that we know from Ivonne and…

Ted Thibodeau Jr: Greg. And that gives sort of a much smaller window of
things for the rest of us to be clicking from instead of some of us having
to click, 37 yes or 37 no. I know my calendar is relatively packed most
days.

Ted Thibodeau Jr: But there's always a window somewhere and knowing the
importance of some things I could shuffle things around. But it would be
based on the prime movers in this case,…

Ted Thibodeau Jr: which is Ivon and Greg. Thanks.

Wesley Smith: Yeah, I so plus one to…

Wesley Smith: what you folks said. I was just going to add to what Mono
said. Ivon Manu essentially said this, but it is worth noting that you are
an active part of basically all of the discussions this group has. First of
all, Greg's effort is much more focused on one of the specifications. I
also will note that I'm happy if we can't find a time that works for
everybody. potentially Greg might be open to coming to the calls once in a
while. and if we can ahead of time know that there are some data integrity
issues that need to be discussed on a certain day. we can try to, pack that
into a single call, have Greg show up to that call, get a lot of data
integrity work done, and the rest of the time I'd be happy to, kind of do
what I've been doing the last couple weeks, which is sort of giving brief
updates that he sends over via email in hisstead. So, a lot of decent
options here, I think.

Ivan Herman: Yes, I wouldn't count on that.

Wesley Smith: Want to go ahead

Manu Sporny: is Avon, I'm sorry, I'm forgetting where X is on the time
zones. is a 12:00 p.m. Eastern call 6 pm for you. Okay. Yeah, that's
unfortunate. And so maybe the US can change their daylight savings position
and that solves things neither unfortunately.

Wesley Smith: All right,…

Manu Sporny: I think this is good. we know what we need to do and so we'll
just try to get some data from Greg and then try to get some data from a
doodle poll.

Wesley Smith: sounds good. any other process announcement, introduction,
that sort of thing items for today? All right. So, last week we talked
quite a bit about publishing threat models and…
Publishing Threat Models

Wesley Smith: regularly on this call we kind of workshop that process. I
saw there's been quite a lot of back and forth with is it Denise Dennis?

Ivan Herman: Denny. I think while man and…

Wesley Smith: Thank you. with Denise on the topic and it seems like we are
in agreement on the direction which is to publish these things as quote
unquote multi-chapter specifications. now there remains some technical
hurdles which is how do we update our existing tooling to support that
concept? Ivon go ahead.

Ivan Herman: I have had our conversation, I think we also have a fair idea
of how this can be done from the akidna/W3C point of view. The question is
how to slightly reorganize the spec repository. I leave that to money where
we will have to separate the file which is in respect and the file which is
the static version of respect because Akidna can take care of the second
one by just copying onto whatever it has to copy it to.

Ivan Herman: but these two have to be separated in the spec which
repository which is not nice but I think we can live with The other issue
which was discussed for a while is that the threat model at the moment is
published as a note which is not good. I would try to leave with the base
format that respect gives that could work and it has some useful meta
information but I am afraid that what is usually referred to as history
might go wrong. So we might have to remove that section by

Ivan Herman: relatively simple JavaScript to be done in cooperation with
respect.

Ivan Herman: That's where we are.

Wesley Smith: Thanks Ivon.

Wesley Smith: Ma go ahead.

Manu Sporny: Yeah, plus one to what Avon said. I think we're very close to
a technical solution. Some minor modifications to what you said, and these
are I think just details that, we'll figure out Avon Deni and myself. Avon,
I don't One of the things where Denise was basically like, you have to
check in the static copy and you have to have two files. I definitely don't
want to do that. because we don't have to do that, that is I think he was
kind of trying to think out loud about how we could do it. Remember that
the way that the specs are created today we have a build process that runs
when a kidna runs and our index.html file during that build process is
completely overwritten by a static copy and then that is what akidna takes
and publishes. So that's how it works today.

Manu Sporny: We can apply that same in theory. I'm pretty sure this should
work especially based on what you found Ivon. we can run the exact same
process on the threat model is a respspec file. It's dynamically rendered
and all that kind of stuff. But during the build process what Akidna does
or the spec process does is it literally just uses the command line version
of respspec to render the specification into a static copy. It names it as
index.src.html and in that exact same GitHub action it then takes index.s
src.html copies it to html completely overwriting and destroying the
respspec file. But that is the static copy that akidna then picks up and
publishes to trspace. So I think we can just do the exact same thing that's
happening today to the index.html

Manu Sporny: html file for the spec to the threat model/index.html HTML and
then if we do that Avon we can run all of the other tooling like link
checking at least the format syntax checking and all that kind of stuff on
the file as well which I think von you mentioned you wanted to do as well I
think that's a good idea too and then we're done right I think we can do it
in a way… where all of those details are just completely hidden by the
tooling instead of editors having to now understand, how to do, this thing.
Manu Sporny:

Ivan Herman: I did not know about the details of Akidna.

Ivan Herman: If that works then that's fine. I don't know how you set up
the GitHub thing now for the DIP spec which is more complicated because I
know that you have used the GitHub possibility to separate the page feature
from the source and that's how you generate the vocabulary files for
example so the vocabulary files are generated and are never part of the
real GitHub repository

Ivan Herman: Is it the same mechanism that is used by Akidna and that's
what we want to use?

Manu Sporny: Unfortunately, that's a different process with other
complexities that don't allow us to use a kid.

Ivan Herman: That's what I was afraid of. Yeah, that's… Manu Sporny:

Manu Sporny: Yeah. Yeah.

Ivan Herman: what I was afraid of.

Manu Sporny: We have to run I think YAML to vocab on it and kidna is and
spec are completely unaware of YAL to we can figure this out I think we
have a direction and…

Ivan Herman: Okay.

Manu Sporny: what we want and…

Ivan Herman: We have Yes.

Manu Sporny: it's just a matter of writing some code to make it happen. I'm
not concerned about it at this

Ivan Herman: One more minor thing I think we have an agreement on that as
well manu is that this structure should be used for all our threat models.
We should not have separate tools or separate features for others.

Ivan Herman: I don't know whether you said I think last time when we
discussing you said that the confidence method people with Joe use a
slightly different process for the threat modeling and I am worried whether
this can be transferred without problems for that one as well.

Manu Sporny: Agree with we want it to work the same way across all these
repositories. Having different mechanisms is just going to make it really
hard on anyone that needs to work on any of this stuff. plus one to unified
tooling across all of our repositories. it was the VCOM specification of on
that they had an external threat model.

Manu Sporny: Since that happened, I think they've merged it into the way we
do all the other threat models. so I think that that issue is resolved.
yeah,…

Ivan Herman: Are you said that Joe is using a different tool,…

Ivan Herman: not Okay.

Manu Sporny: that is the respect-threats tool. That thing's being copied
all over the place. But that is a respspec plugin and is Yeah.

Ivan Herman: Besides the point. Yes. Okay. Okay.

Manu Sporny: Yeah. it's just respspec runs So whatever if we run respec on
the spec, it automatically runs all that other complicated code to do what
it needs to do. so yeah, luckily we don't have to worry about that. The
thing we need to worry about there is that tooling has been copied and
pasted in five different places and has evolved based on experiments we've
run on the threat model. So we have to reconsolidate that code.

Ivan Herman: Let's move to something more interesting.

Manu Sporny: Joe does have a respect threats repository. It is. a very very
low priority for me to reconcile everything right now. We're just trying to
get to horizontal review. Once we get past horizontal review, hopefully
we'll have some extra time to clean things up.
VC Forgery Defense

Wesley Smith: That's very interesting stuff. Thank you both for the time
and thinking through this process. I'll reiterate briefly that there seems
to be somewhat of a bus factor problem with this tooling stuff and I'm
happy to help where possible. I don't know how any of it really works, but
if anyone in the group feels like at any point it would be a good time for
somebody else to jump in and, pay the overhead to get up to speed, happy to
do that. All right. next let's talk about VC forgery defense.

Wesley Smith: Not a lot to talk about today. I do want to briefly bring up
I'm not going to link it directly for bot reasons, but there was a spam
issue raised. I'll link the closed issues in the chat. question is any
other action needed from me or others in the group? are there any W3C
process things that need to be done or…

Ivan Herman: Okay.

Wesley Smith: GitHub buttons that I should press other than just marking an
issue as appearing to be spam and Delete it from orbit. Manu, go ahead.

Manu Sporny: Yeah, I mean plus one to nuking it. I don't know if we can. I
can't do that.

Manu Sporny: I do have a spam marker. wow, this one's really good. Pictures
and everything.

Wesley Smith: Yeah. …

Wesley Smith: the reason I didn't immediately delete it was because that
seemed like editorial overstep or something. I don't know. I wanted to at
least this is pretty clearly spam, but it seemed like bad practice to
delete something immediately instead of commenting that it appears to be
spam and giving somebody a chance to say no, it isn't spam even though it
looked like it. Sorry, Manu. Go ahead.

Manu Sporny: I mean this thing is clearly spam right they're right so in
that case you can delete it I mean this is super spam and…

Wesley Smith: Hey, I'm with you.

Wesley Smith: You don't got to convince me, but

Manu Sporny: there's delete issue in the bottom right and if we do it by
accident, the person just comes back in and reres The danger with keeping
spam around is that it provides positive referrals, which boosts, search
scores and all that kind of stuff. we do not want to contribute to that,
bot ecosystem. So, we can do our part to combating these back links.

Manu Sporny: That's

Wesley Smith: All right,…

Wesley Smith: Ted. Go ahead.

Ted Thibodeau Jr: Yeah,…

Ted Thibodeau Jr: while I agree deleting it gets it out of our way, there
is a process for reporting content and…

Ivan Herman: How do you do Okay.

Ted Thibodeau Jr: and spam posts, etc. to GitHub. they're not the fastest
to deal with anything, but it's the only way for GitHub to get any better
at preventing it or closing spam accounts or that sort of thing. So, I
would say don't Do tag it as spam. Do report it to this to GitHub. you're
obviously the repo admin, so don't report it to yourselves. That's it. one
second.

Ted Thibodeau Jr: Upper right there's three dots and it says report content

Wesley Smith: The three dot money.

Wesley Smith: Go ahead.

Manu Sporny: Yeah, plus one. I think Ted's got the better idea here. we
should report this. So, this is basically you're reporting the user for
generating spam, which means that they'll go after the account. plus one
did that. I wish we could just delete it after or maybe they'll come back
in and delete it. I don't think we need to spend plus one. Let's report it
at spam as spam and then, close the issue, mark it as spam, and then maybe
at some point in six months, we go through all of our spam issues and bulk
delete them.

Ivan Herman: I would propose to report content and…

Ivan Herman: also block the user.

Wesley Smith: sounds good.

Wesley Smith: I just reported the issue. Block the user. Is that going to
be me personally blocking the user or is there a repository block?

Ivan Herman: I think the repository it blocks the user.

Wesley Smith: Okay, I'll look into that off the call. I think we are good.
Thank for the guidance. Mona, go ahead.

Manu Sporny: Yeah, The problem of with blocking the user is that if it is a
legitimate thing, they will be unable to reerraase the issue. Maybe, two or
three infractions and we block them. But my expectation is that GitHub will
act on the spam thing and then block them and hopefully delete their
content and…

Manu Sporny: all that kind of stuff. And if they don't, we'll go back and
delete the content in six months.

Wesley Smith: All right.
PR Review And Merge

Wesley Smith: Anybody else have anything on that topic? All right. Moving
on. next up, there's a PR. Please review this PR. Hang on. not properly
topic this in a second.

Wesley Smith: Please review this R if you are a contributor or you've been
part of that discussion at Manuspornney.

Ivan Herman: as a kind of a of method.

Wesley Smith: You requested some changes. Please when you have a second go
and look at the changes they're pretty brief. anyone else interested in the
specification take a look at this PR. it's not a big PR. It's a pretty
small PR. It just generalizes the format for a piece of randomness in the
specification and now adds an example for why the format is defined the way
that it is. Ivon, go ahead.

Ivan Herman: methodology so to This PR has been around for a while. It says
last months and we are at the end of August. So that means several weeks.
It has been approved by two people and it has been commented by one and was
acted upon. So I would consider that there is a third one that has approved
it.

Ivan Herman: I think you can just go ahead and then merge it. There is no
reason to keep it for open for so long. My personal opinion of that

Wesley Smith: …

Wesley Smith: I certainly hear what you're saying and agree with the
sentiment. my hesitation is that I would be making personally a judgment
call whether I had addressed the person's comments to their satisfaction.
And in this case, I think I have because the ask was pretty clear and I
acted upon it in a pretty clear way. But if the feedback was a little bit
less definfined do exactly X, then it would be a judgment call whether or
not the other person was satisfied. Is that a concern?

Wesley Smith: Go ahead.

Manu Sporny: It is your right as an editor to merge if you feel like you've
addressed the person's commentary. plus one to what Ivonne's saying. There
are things that you want to of course take into consideration is the
commenter a hostile actor? I hope I'm not. So, …

Wesley Smith: Am I hostile?

Manu Sporny: and I'm sure that you, addressed the plus one. I mean, I'm
looking at it right now, but I would have been fine with you merging it.
even without looking at it, and then, if it didn't actually address the
concern I had, Wes, I'd just raise another issue, And so there's a response
cycle that allows for correction on the editors making the wrong judgment
call. so you want to be pretty sure but you don't need to be 100%.
especially if something's waited out there for weeks you're waiting on me.
3 weeks ago you added the example. I am so overloaded right now. I just
can't get back to reviews. So, I am certainly not going to be upset

Manu Sporny: ever if you merge something if you feel like you've addressed
the concern and I think that goes for just about anybody else providing
input the things that I think about as an editor is like one was this
person's request clear enough for me to act on it and if the request was
vague then too bad I tried my best I'm going to merge it because I think I
addressed it to the best of the ability the other thing is like I asked you
to Did you respond in a week? If not, too bad. I need to move on as an
editor. I tried to address your issue, in good faith. and I'm merging it,
asserting that I believe I've addressed your issue. finally, and this is
very very rare, but if the person is hostile or argumentative, and that
happens, only then do I kind of try and wait for their response.

Manu Sporny: And I usually ping them every three days I need a response, I
need a response. and only after gathering enough, evidence that I tried to
get, them to respond and they were unresponsive for a week or two and I
went ahead and merged it. Usually you want to just build your case for like
I did my best as an editor but as a working group need to move forward and
letting PRs hang out here for three weeks is just not that big of an issue.

Manu Sporny: The other thing that comes into play is are you modifying
normative language because if it's just editorial stuff like an example
doesn't matter right meaning you don't have to make them happy right it's
an example it's non-normative they can't raise process objection over it
but if you're touching normative text and it's a highly contentious topic
that's when you have to be a little more careful. So hopefully those things
kind of help make the judgment call, but it's always your right as an
editor Wes to determine that you have done your best to address their
concern and…

Manu Sporny: you need to move on and you need to merge something.

Wesley Smith: Thank you for the guidance.
Data Integrity Updates

Wesley Smith: All right. With that in mind, I see Dave Longley just added a
wording tweak. So, I will go ahead and get that stuff incorporated and get
this merged after the call today. anybody else have anything on VC forgery
defense for the group? All right. moving on to data integrity. Greg
Bernstein sent an email to this group's mailing list with his updates for
data integrity. Would it be useful for folks if I briefly went through
those?

Wesley Smith: Are you all happy to read that email on your own time? What
do folks think? I got thumbs up at two different parts of that sentence.

Wesley Smith: So, I need some words. everybody read that email on your own
time.

Ivan Herman: Read it.

Ivan Herman: No, no, I said read.

Wesley Smith: I read it.

Ivan Herman: You read it.

Wesley Smith: All so, Greg Bernstein noted a few things for his work on
data integrity. he noted that there are three outstanding PRs that he's
created to I believe this is part of the generalizing the common algorithms
among the crypto suite work. he has some PRs out that try to explain the
selective disclosure work. He says he prematurely merged one of them. I
assume he's fixing whatever issues that incurred.

Wesley Smith: He also is fighting with the same GitHub EOL bug that is
taking many hours out of many of our lives these days. next steps he says
he wants to do selective disclosure refactoring updates to ECDSA quantum
resistant and BBS test vector updates in quantum resistant readability
improvements for data integrity 111 readability improvements for some of
the crypto suites based on the changes to 11 one and…

Wesley Smith: five other items. Those are steps. Ivon go ahead.

Ivan Herman: So I am not sure I understand the mail…

Ivan Herman: because the data integrity lists only one PR open not three. I
think what happened was that he had a PR on the explanatory stuff which I
created a PR with a version which was approved somehow both of them and…

Ivan Herman: merge and I think it's okay to be merged. So there is only one
PR that is open on the DIP spec which is a selective disclosure refactor.

Wesley Smith: Right. I think the merged PR in the base data integrity
specification yielded some progyny PRs in a bunch of the specific crypto
suites…

Wesley Smith: which are where those other PR Let me go ahead drop a link in
the chat so everyone knows…

Ivan Herman: Okay, that's a separate one so on the DIP spec there is one
open which is the selected disclosure refactor on specifically that one my
opinion is that it should be merged it has I'm sorry so I should subtopic
it or…

Wesley Smith: what we're talking about. Give me one sec. That is okay. Ivan
Herman:

Ivan Herman: to no topic Right.

Wesley Smith: Here I'll topic DI and then use that works too. Okay.

Ivan Herman: So, it has been reviewed by people. So, it's not like it's
there without review. and this is typically the kind of thing that will be
reviewed again indirectly when we get to see our space because after all
these are the algorithmic steps and maybe at somewhere some algorithm is
wrong and there is no way I will find it now but when someone begins to
really implement the spec then this will come up on the other hand this PR
is important because it is with this merged that all the other

Ivan Herman: PRs on the crypto suites become valid because all of them no
that's incorrect the other PRs on the crypto suites are on the refactoring
of the full disclosure part but the work on the other documents will be
finalized when this PR is merged and it's just too much in the air and it's
better if we have everything merged and done and put in the spec. The spec
is not yet finalized and it will be reviewed as I said during
implementation but it makes a much cleaner slate right now with all the
documents that we have around to be just done.

Ivan Herman: That's my view. Leaving it in P just leaves too much things up
in the air.

Wesley Smith: Avon, I'm apologies.

Wesley Smith: I lost the thread when you were speaking.

Wesley Smith: What action are you recommending the group take?

Ivan Herman: I am recommending to merge the 358 and…

Ivan Herman: together with that I also recommend to merge the other PRs
which are for specific crypto suites refactored on the full disclosure.

Ivan Herman: Do that and then do the same for the selective disclosure in
the case of the crypto suites.

Wesley Smith: heard. I will note that it seems that there is still an
outstanding whites space problem in that PR.

Wesley Smith: Do you still think that PR should be merged or that con the
content from that PR should be somehow merged elsewhere? Monty, you have
your hand up and you're emoting aggressively.

Wesley Smith: Go ahead.

Manu Sporny: Yeah. Yeah.

Manu Sporny: I very rarely use thumbs down, but this is a good time to do
it. yeah, we need to fix the whites space issue just a entire rewrite of
the file. Greg said he tried but he doesn't know how to do it. Someone
needs to go in there and just do a rebase and rewrite the commit that does
all the whites space changes. I know what to do. I just don't have the time
to do it. I also don't know how to push it to Greg's branch because the way
he's editing these specs is off of his own one instead of just raising PRs
on the spec directly, which makes it harder to do a history rewrite.

Manu Sporny: right, like this. So, it may be that someone needs to
basically check out Greg's branch, fix it up, and then push it to a new PR
without destroying any of Greg's legitimate changes. And then once we do
that, I completely agree with Avon. Let's just merge this because, it's an
improvement and we can iterate towards a better future. I do note though
that there are still some outstanding things that I don't know…

Wesley Smith: Ted, go ahead.

Manu Sporny: I don't know if it's been addressed by Greg or not. that's it.

Ted Thibodeau Jr: No argument with any of that,…

Ted Thibodeau Jr: but I will ask one more time that whomever is appropriate
in W3 staff,…

Ivan Herman: I intend to raise it on the global meeting we have on every
Thursday.

Ted Thibodeau Jr: hint hint, could raise this as a thing. I believe W3 is
paying GitHub for the services they are providing and this is causing a lot
of cost on volunteer side. it's not just this work group, it's not just
this spec, it's everywhere in GitHub and it really needs to be addressed.

Ted Thibodeau Jr: Thank you.

Ted Thibodeau Jr: Please do.

Wesley Smith: All right.

Wesley Smith: That sounds good. I'll poke at this PR and see if I can get
it fixed up. anything else on data integrity?

Ivan Herman: for the records.

Ivan Herman: I love what Greg did.

Wesley Smith: Changing all the white space in the file to be wrong.

Ivan Herman: No, no, no. but the work that he did for the refactoring etc.
and the result that we get super simple document for the crypto suites it's
just absolutely great work.

Wesley Smith: Yeah, it's good stuff.

Ivan Herman: More power to retired people.

Wesley Smith: Mon, go ahead.

Manu Sporny: Yes, plus one to that.

Manu Sporny: I totally forgot what I put myself in the queue for. yes,…

Wesley Smith: I said anything else about data integrity.

Wesley Smith: Hey, Manu Sporny:

Manu Sporny: thank we have had a contribution from an individual that's
doing postquantum. It's the ski sign thing. Ivon, I think he's suggested
he'd become an invited expert. He is.

Ivan Herman: is …

Manu Sporny: Okay, great. So, we just need to figure out a way to get him
on these calls. He's been contributing. I think it's a rust implementation
of all the DI specs of specifically the postquantum one specifically ski
which we're very interested in. would be, wonderful to have him on the
calls. I think he's based out of New York City. so just wanted to make sure
that that was proceeding upon you're saying it is. okay.

Ivan Herman: yeah, we approved it the day before. Yesterday, I believe.

Manu Sporny: So, we just need to fold him into this meeting. so, maybe we
can do some f …

Ivan Herman: I don't know whether he joined. That's something he has to do.
Manu Sporny:

Manu Sporny: All So maybe we need to ping him. I'm not going to have any
time to do that this week, I don't think. But I'm just want to make sure we
don't drop and that OS is relevant to data integrity because I think he
might be able to help Greg with some of those specs as well.

Wesley Smith: Yeah, And anything else on that topic?

Ivan Herman: Hello.

Wesley Smith: I think we're all in agreement there. Yeah. …

Manu Sporny: Are you on that email, Chain Wes?

Wesley Smith: I don't think so. can we say this person's name?

Manu Sporny: One second.

Manu Sporny: Yeah. Anthony.

Wesley Smith: If I am,…

Wesley Smith: I'm not aware. I will also note that I just offered to fix
the data integrity spec. I just realized I'm not an editor of the data
integrity spec. So, I can fix it by cloning the repo and raising a PR that
way. I don't know if that's the simplest way. Okay.

Manu Sporny: Yes. it's not ideal but yes that you can do that it'll just
show up as another PR hopefully without all the whites space errors.
VC Barcodes Updates

Wesley Smith: If it still has the white space errors, I don't know what I
will have been doing. sounds good. Have commit referenced here. Thank you.
Anything else on data integrity for today? All right. on to VC barcodes. I
don't have much further group to talk about today for VC barcodes.
horizontal review calls are out and have been for a week or two. and that.
There's some editorial work still to be done. but I think we're in a pretty
good space,…

Wesley Smith: pretty good place on that specification. Have anything there?
Ivon, go ahead.

Ivan Herman: So there are two things which are pending and I think they are
beginning to be timely and I think I raised issues for both of them is to
move out one of the XI crypto suite and…

Ivan Herman: to move out I don't remember the name for the bit.

Wesley Smith: the ter bit string status list entry.

Ivan Herman: So these two should be moved out and…

Wesley Smith: Yep. Yes.

Ivan Herman: to put in the right place because it's better if to be done
with before the horizontal reviews really start. for the exi thing then
it's a technical question to which I don't have an answer is that does the
XI feature if on the lack of a better word is something that should be
folded into the generic algorithm of the DIP spec or…

Ivan Herman: is it something that should be folded into the ECDSA crypto
suite spec which is now refactored so It's not clear to me what the
direction should be. The only thing I know that it should move somewhere on
that area.

Wesley Smith: Right. So the relationship between the XI crypto and…

Wesley Smith: the other cryptoes is that the XI crypto suite is exactly
ECDSA RDFC 2019 with the addition of an additional hash value. right.

Ivan Herman: I know Another possibility is to put the XI feature into the
generic algorithm that Greg put into the EIP spec and…

Wesley Smith: So I would argue that it would make sense for it to go in the
ECDSA crypto suite document. if there are reasons why it needs its own
document, I would love to hear them.

Ivan Herman: therefore the XI extra feature should be automatically valid
for other crypto suites as well.

Ivan Herman: It may be complete stupidity what I'm saying. I'm just idea

Wesley Smith: So, I would have to look at the abstractions that are there
more closely,…

Wesley Smith: but how it's unclear to me whether or not a quote unquote
extra hash could be cleanly added as a feature to those generic algorithms
and not to an instantiated algorithm for the crypto suite. Manu, go ahead.

Manu Sporny: Yeah, that was the same concern I had. plus one to Avon's
general desire, I am hoping that we can integrate this as a general feature
to the base algorithms in the crypto suites. it would be wonderful if we
could figure out a way to make it backwards compatible, but I'm also
concerned that if we try to do that,…

Manu Sporny: we might introduce some security vulnerabilities. so we would
have to do that, very carefully. I don't know if we can make an argument
that our charter clears us to do that. so for now I think is it really a
security issue or…

Ivan Herman: Why? modify specifications…

Manu Sporny: vulnerability? No. we are supporting new P.

Ivan Herman: if the new specifications raise an issue that has to be solved.

Manu Sporny: I just didn't know how much we could put underneath that
umbrella. I'm a bit concerned about how can we do this in two phases? The
first phase is getting it into the ECDSA thing just as is and not changing
anything and then the second phase is determine if we can generalize it
safely. Okay.

Ivan Herman: That's fine.

Ivan Herman: That's fine. Of course. That's fine.

Wesley Smith: Yeah, that sounds good.

Wesley Smith: And on a practical more mundane short term, what's the order
of operations here for me as an editor of the VCB spec? I mean, should I
wait until it's safely in another spec before I just nuke it out of this
spec? I mean, okay, it needs to exist in at least one place at all times or
something. Okay.

Manu Sporny: That's right.

Wesley Smith: Okay, sounds good.

Wesley Smith: So Avon I am curious what …

Wesley Smith: why you feel this is becoming timely. I thought when we had
discussed previously we were like worst case scenario this stuff just gets
reviewed by horizontal review multiple times. What's the pressure you're
feeling?

Ivan Herman: We are talking about CR and…

Ivan Herman: in CR by CR this must be done and we are end of August and…

Wesley Smith: All understood. I will get the ball rolling on that work.
Ivan Herman:

Ivan Herman: Another one is even more of a problem but more practicality…

Wesley Smith: What's the other?

Ivan Herman: because the one which modifies the B string specification…

Wesley Smith: Right. Right.

Ivan Herman: because that one has to be then officially reopened as a new
version. So that even more time.

Wesley Smith: That there's extra work. Yeah. Okay.

Wesley Smith: So I may need help from Ivon Monument or someone because I
don't know exactly what needs to happen there. We need to do a first public
working draft of Bitstream status lists 1.1 or something and…

Ivan Herman: Yes. Yes.

Wesley Smith: then after we do the first public working draft then we can
add new features. So that needs to happen in a vacuum before anything to do
with R I have some instructions somewhere in my email inbox for how to do
the first work stuff. I can go get that started. Mon, go ahead.

Manu Sporny: Do we have a resolution to pass to publish FPWD? We'd need
that, Avon. I can't remember. I don't think we did a res.

Ivan Herman: No, we need the resolution but not here but on the burkin
group…

Manu Sporny: Right. Exactly.

Wesley Smith: So, tomorrow I'll raise that as something that we would like
to get resolved or put up a proposal. and then once that's done, I'll go
push some FPWD buttons and then get going.

Ivan Herman: if it was simpler…

Wesley Smith: I just take you for granted,…

Ivan Herman: then if that's done then I have to do some boring
administration.

Wesley Smith: All sounds good. I think that's a good plan. Anything else on
VC barcodes for today? All right. I'm out of material. Anybody else have
any topics that will fit in seven minutes? Man, go ahead.

Manu Sporny: No, I think we're fine. I think it's worth mentioning that we
heard that Bannon has maybe deployed and the World Bank has maybe deployed
verifiable credential barcodes at scale. I don't know if anyone has any
more information on that. I know we've looked at some screenshots, but some
of this stuff was back in 2024 where I'd be surprised if they used
verifiable credential barcodes. I know that Simone connected some of us to
World Bank people. but I don't really know.

Manu Sporny: World Bank was very interested in verifiable credentials and
did five years ago and then I think people moved around and we didn't hear
anything from them and now all of a sudden we're hearing that, potentially
7 million people in Benon are walking around with verifiable credentials in
their pockets. the barcode stuff. So, I don't know…

Wesley Smith: Ela, go ahead.

Manu Sporny: where we would find out or if anybody knows or if Avon Simone
has said anything about this. Okay.

Ivan Herman: No idea.

Ivan Herman: No Maybe somebody in Geneva will know about that. Wow. Okay.

Elaine Wooton: Yes.

Elaine Wooton: So I'm the person who saw the slide by the World Bank in
Bangkok that said specifically W3C verifiable credential signed code. and I
did not manage to take a picture of it. So, I will endeavor to get more
information. but I think everybody should be on the lookout. I don't know
how we're going to find out for it'd be great to find out what the heck is
going on with that.

Wesley Smith: And that does sound extremely cool. all right.

Wesley Smith: Anything else for today? We got five minutes left. Lane, go
ahead. Or is that old hand? All right. Ivon, go ahead.

Ivan Herman: So, something totally different is just a kind of an FYI.

Ivan Herman: I saw some males passing on a workshop that seems to be
created by W3C maybe together with IETF but I am not sure on reopening the
XML signature work and specifically by adding quantum resistant keys and
methods to XML signature which is obviously something good to do. But
during the discussion I saw passing by what they are discussing what
algorithms should be used and accepted for that spec and there are some
overlaps with what we have and some other acronyms that are completely
unknown to me etc.

Ivan Herman: So I was just wondering whether it's worth somehow to talk to
people who are close to that work and find out ideally the algorithm that I
use for XML signature should be the same eventually than the one we use and…

Wesley Smith: want to go ahead.

Ivan Herman: I know that the list we have now is sort of temporary anyway
so I don't know whether anyone has heard about this at

Manu Sporny: I have been following the threads. I feel like it would be a
pretty big distraction for us at this point to engage because they're
talking about some fairly esoteric, things. I think when they get to last
call which will be sometime from now at that point we should pay attention.
but until then a lot of the discussions they're having are two years ago
one year ago it's rehashing things we've already discussed.

Manu Sporny: So yes, Savon, I'm like tracking that conversation, but I feel
like we,…

Ivan Herman: Okay.

Manu Sporny: it'll be a very big distraction for us because there's a lot
of politics between W3C and IETF when it comes to XML digital signatures.
And I don't think we need to get wrapped up, in that. We are very
interested in what they pick at the end, but they've already said more or
less they're going to end up picking the things that we've picked.

Ivan Herman: No, that's fine with me.

Wesley Smith: All right.

Ivan Herman: I just wanted to be sure that something is happening and I am
not in position to give any opinion on the technicalities here. That's all.

Wesley Smith: Thanks for bringing it to the group's attention. Anything
else for today? Two minutes All right. Thank you all for the time as always
folks and I will see some of you later this week and the rest of you next
week. Meeting ended after 00:53:38 👋 This editable transcript was computer
generated and might contain errors. People can also change the text after
it was created.

This transcription was generated by a large language model (LLM) and might
contain errors. When in doubt, check the audio recording. This page was
formatted by scribe.perl <https://w3c.github.io/scribe2/scribedoc.html>
version 248 (Mon Oct 27 20:04:16 2025 UTC).

Received on Tuesday, 25 August 2026 23:52:32 UTC