[MINUTES] CCG Atlantic 2026-07-14

Meeting Summary: CCG Atlantic - July 14, 2026

The CCG Atlantic meeting on July 14, 2026, featured a presentation by Nik
Jenzer from the Swiss Federal Chancellory on the concept of "Record Web."
Jenzer introduced Record Web as a potential evolution of records
management, addressing current challenges like container-bound identity and
unreliable archiving by proposing a system where records are autonomous,
have defined technical states, and support continuous, provable engagement.
The discussion revolved around integrating existing W3C standards like DIDs
and verifiable credentials into this framework, exploring its potential
benefits for governmental record-keeping and citizen interaction. The
meeting concluded with an exploration of how the CCG could potentially
support the development of Record Web, particularly in the area of
decentralized identifiers.

*Topics Covered:*

   - *Record Web Concept:* Nik Jenzer presented the "Record Web" as a novel
   approach to records management, aiming to decouple records from their
   storage location and system, allowing for independent existence and state
   management.
   - *Problems in Current Records Management:* Current systems were
   identified as struggling with container-bound identity, leading to multiple
   copies and potential loss during migrations, and a disconnect between
   active work systems and archival systems.
   - *Record Web Principles:* Key principles of Record Web include "record
   first" philosophy, autonomous records, technical state management
   (draft/finalized), and the concept of a "record continuum" for continuous
   engagement.
   - *Integration with W3C Standards:* The Record Web aims to leverage
   existing W3C standards such as DIDs for identity, content hashing for
   integrity, and potentially Solid for decentralized storage.
   - *Record Web Architecture:* The proposed architecture includes identity
   (DID), payload (content with draft/finalized states), and metadata, with an
   emphasis on schema adherence for typed records.
   - *Case/Dossier Reimagined:* In Record Web, cases are no longer
   containers but links between records, forming a typed record themselves,
   potentially utilizing Merkle trees for integrity.
   - *Proposed Development Path:* Jenzer outlined a plan to develop Record
   Web through proof-of-concepts and community engagement, aiming for a W3C
   standard.
   - *Community Group Proposal:* Jenzer discussed the intention to
   establish a dedicated Record Web community group to foster governmental
   representation and technical collaboration.
   - *Support for DID Method:* The need for a DID method specification was
   highlighted, with a request for assistance from the CCG community.
   - *CCG Role and Support:* The CCG discussed its capacity to provide
   technical expertise and support for the Record Web initiative, particularly
   concerning DIDs and verifiable credentials.

*Action Items:*

   - Nik Jenzer will continue to develop the Record Web concept and
   protocol, seeking collaboration and feedback.
   - The CCG will explore how to best support the Record Web initiative,
   potentially through a dedicated task force or by offering technical
   guidance on DIDs and verifiable credentials.
   - Further discussion is needed regarding the proposal of a new DID
   method, including understanding W3C requirements for such proposals.
   - Individuals interested in supporting the Record Web initiative are
   encouraged to review the provided documentation and engage with Nik Jenzer
   and the proposed community group.

Text: https://meet.w3c-ccg.org/archives/w3c-ccg-atlantic-2026-07-14.md

Video: https://meet.w3c-ccg.org/archives/w3c-ccg-atlantic-2026-07-14.mp4
*CCG Atlantic - 2026/07/14 11:59 EDT - Transcript* *Attendees*

Amir Hameed, Benjamin Young, Elaine Wooton, Erica Connell, Gregory Natran,
Harrison Tang, Jennie Meier, Lancine Toure, Mahmoud Alkhraishi, Nik Jenzer,
Phillip Long, Ted Thibodeau Jr, Will Abramson
*Transcript*

Nik Jenzer: Hello. How are you? Okay, no problem.

Nik Jenzer: Yes. I have prepared a little presentation. Is it possible to
share? It's the first time I use Google Meets.

Nik Jenzer: I see. Sharers can. Yes.

Nik Jenzer: Do you see now my screen? Does this work? H Okay.

Nik Jenzer: But I will stop and share it.

Nik Jenzer: Okay.

Nik Jenzer: Just a minute. I will start the presentation. I think you can
see my screen. thank you very much for the chance to talk about the record
web.

Nik Jenzer: First of all about me I'm Nick from the Swiss Federal
Chancellory and first of all this is a governmental job I have there I'm
engaged for more than 10 years as a specialist for records management and
in this position I do also chair a Swiss standardization organization not
for web standards of course but for governmental standards and

Nik Jenzer: this is where we started the work about the record web.

Nik Jenzer: Also I think you have to know it is noted here Tbecat is an
enterprise on my own but it's not operational but this is done because I
have an agreement with the Swiss government if I do some explorating things
they are not really represented them for the government first I do this
work for Tribakat

Nik Jenzer: And if there is something later that can be used for the
government then it will be used for the federal chancellory. So this is the
reason why sometimes you will find both things and the Swiss government.
but I'm representing here the Swiss government. Okay.

Nik Jenzer: I talk about the record web now.

Nik Jenzer: Because the base of this

Nik Jenzer: is records management. This is a term from governmental sector.
it's about handling of records and this is document management we can say
we do this in the Swiss government for more than 20 years and of course we
have a standard to do this.

Nik Jenzer: And these standards are more than 20 years old and the ECH is
the structure who develops these standard in Switzerland and we decided or
we found we have to review these standards and while reviewing we thought
this year that we have to think about new not only do things better not to
evolve the standard.

Nik Jenzer: So we started to think let's start with the green field
approach and there is where the record web is coming from. So the records
management has several problems we found. there are only a few I go through
now. records management couples location and state is one of the major
things.

Nik Jenzer: What I mean with this is that the records management binds the
identity to a container. So you can imagine the old MSTOS world 20 30 40
years ago you have a directory and this is directory you have a document
and this is still the philosophy of records management today.

Nik Jenzer: So first of all you need to have this directory. We call this a
dossier or a file or a case. first you need to have this container and then
you can store your documents in there. And then followed is the second
problem is the article status.

Nik Jenzer: most of the time or is at least in Switzerland and all what I
know is you have to transfer your directory your documents when you want to
go and archive these documents. So every time you do this you maybe lose
some content you have to migrate things you have to convert documents to
other formats.

Nik Jenzer: So yes these two problems the containerbound identity means
that the document can only exist in one directory in one dossier and if
people for example Mahmood and we have the same case and I do not trust
Mahmood when he is organizing our dossier.

Nik Jenzer: So then I do normally make a copy into my structure.

Nik Jenzer: So that leads normally to have multiple dosm

Nik Jenzer: multiple files and of course also multiple documents and
everything has to be organized.

Nik Jenzer: Everything has finally to be archived and when things are
changing systems are migrating most of the time it is yeah what I saw most
of the time is you lose some documents you lose some dossier when you do
some migrations from one version of a system to another or finally to the
archive.

Nik Jenzer: So this is things that we want to make better and the problem
is not only a technical thing that what we decide what we defined in the
standards is working it is pretty well working and the problem I can't say
the problem is the stuff but it is actually the stuff but what we decided
is we don't have to

Nik Jenzer: to make more regulations, more government, more education with
the stuff, we need to change the system because the systems seems not to be
reliable or not be as good as it should for the people working with it.

Nik Jenzer: So yeah the people we want to change the system on how to
handle this record and yeah then what we want to do is at a couple things
this is in our words a game changer when we say record first this is really
the

Nik Jenzer: game changer because the most people think about ssier these
files and new we want to say record first.

Nik Jenzer: So that means the record can exist independently I said here
autonomously he exists and we can work with a record independent where it
is stored in which container because it doesn't need to be in a container.
we can link it together. I come to this a little bit later.

Nik Jenzer: The other thing with archiving is that we want to implement a
state.

Nik Jenzer: Also today documents have states of course but these are more
organizational states and now the states are becoming a technical part at
least we can see or we think about two a draft and a finalized state and
archiving is no longer moving the document to somewhere else but changing
the state to a stable version where it can't be changed anymore.

Nik Jenzer: more. And

Nik Jenzer: The idea is then the document the record itself doesn't have to
leave the system. it does only need to change its state. So nothing move
and nothing will be losing this transit.

Nik Jenzer: And the continuum on the right side is a thing there exist in
Australia the record continuum idea that means that the record does not go
as we think.

Nik Jenzer: We have a system of work where we work with this record. We
change it. Then we have a system of record where we store it and do not
longer change. And we have a system of archive where it is be stored for
the next several 10th or 100 years. But we then have a problem when you
want to work with these documents.

Nik Jenzer: when is in the records management system almost you will not
find it or when you find it you cannot work with it because it is in a
format you can't work with it and when it is in the archive for the most
people the archive is like a grave. So when you put something in the
archive you will never get it you will never have it again.

Nik Jenzer: So the record continuum idea is people want to work
continuously with this record and the problem there is when you
continuously work with it from websites they change and in the language of
government a change is not really reliable. so what we want to do is look
for something that we can have both worlds.

Nik Jenzer: we can continue working with the record itself but also in a
provable way we can what we want to do.

Nik Jenzer: So this is the three major things that we want to change in
this green field approach and how we developed it or I have to say how I
developed it because I started this idea because I get the job from this
ECH technical group think make green field approach and I did it in one
weekend with

Nik Jenzer: AI assistant. So, a lot of things are a co-work with AI. also
because my English is not the best especially when writing. So, I'm very
thankful about this also. For example, this presentation of course was done
by Claude with my inputs. So, come back to the record web then is not
something really new.

Nik Jenzer: we don't have to need complete new standards.

Nik Jenzer: So on the direct the record web is more or less an operan
operonization of these three decouplings and most important with existing

Nik Jenzer: W3C standards. so we will not change the web standards. We will
use them and we use them in a separate kind of way. And this is then
finally usable as a record web in the governmental part. what does this
mean according to the web?

Nik Jenzer: I think multiple generations of the web architecture first of
all the worldwide web I don't have to go in all these data I think there
was the first thing missing several parts then came up link data an
improvement but on the governmental part still lacking several things so
the record web should be a next step where we work in the focus of a record
instead

Nik Jenzer: instead of a document. just a technical thing but the more
important is the identity the DID where we want to go we will use graph not
only a version number also the accountability should be an owner and what
we want to do is the content hashing to prevent changes later in the
content or in the payload of any record.

Nik Jenzer: And for us in the governmental sector is more important that
the type of record following a schema and this must be mandatory today. or
at least a good part of records are not really typed a general type and
this is a problem when you want to find the record again.

Nik Jenzer: Not really new things and that brings me to some more details
what a record is.

Nik Jenzer: the record or you can more imagine as a document. in our
wording we say this is a record because this is small smallest meaningful
unit of information and the thing it is autonomous information.

Nik Jenzer: So it can exist by itself because it is describing itself and
says what it is and not just It is a described descriptive form of
information. Okay. it is built in three parts.

Nik Jenzer: First of all is the identity where we want to go to of course
also today records have an identity but these identity are typical to the
system where it is used.

Nik Jenzer: So you can't exchange the identities and

Nik Jenzer: when you change your system you normally also migrate the
identity and if you change this once you will lose them.

Nik Jenzer: So the idea is to go with the ID4 identity.

Nik Jenzer: Of course we have the payload the content in different version
of course in a draft where the format can be any proprietary format of
course and then we have a finalized state of the payload and this finalized
should be of a type where archives or others can read this content for the
next 100 years.

Nik Jenzer: So a PDF exist in there as a special version of PDF is called
PDF 1A. something like this. text formats are there. yeah of course JSON,
XML and also some picture formats but not every CAD format or any other
special format. Then of course Metadata is also nothing new.

Nik Jenzer: we have it today in these systems but of all these metadata are
not used because the human needs to fill this metadata and this is one of
the part the people the staff doesn't do it very well and our idea is if
this is typed we can automate the metadata.

Nik Jenzer: So also nothing really new but the combination of all should
make it more meaningful in the future. Here below you can see some
examples. for example these meeting minutes existing from this meeting
maybe a record or any other things too. the version graph I think also this
is nothing really new to you.

Nik Jenzer: For us the record management guy we normally version our
documents in the name of the document or somewhere in some text files on
the first page in any kind.

Nik Jenzer: And what we want to change here is to use the version graph as
you can see also with branches and merges possible things that we can't do
today and you can say or you can define that a special version has a
special state and you can work with them.

Nik Jenzer: I think this better than me. I'm not yet really comfortable
with GitHub but this is a thing that should come in the next few months.

Nik Jenzer: So this is also one thing that will change for us record
management guy and also a big change for us is the case or as I said the
dossier

Nik Jenzer: Yep.

Nik Jenzer: because today this is a container this is the directory and in
the new record webology or I don't know how to say in the wording of record
web now the case is no longer a container the case only links records
together and finally of course the case is then too a special typed record
with its only job is to link records

Nik Jenzer: And of course this record can also be finalized and if
everything is finalized we do it with a hash also nothing new and the case
contains then the hashes of all its records and then you can form a merkel
tree about all these hashes.

Nik Jenzer: This is what you see on this and why this is a question about
the future. we have it already in Switzerland that you can lose I don't
know how to say when you go to a judge if you have something with a judge
and with another citizen.

Nik Jenzer: the government already lost one of this conflict because the
government was not able to prove that the document was existing at the
moment of the decision and this is something that we want to make part of
this. This is why we propose to hash all these things so that you can prove
in 30 years that something existed and didn't change in the meantime.

Nik Jenzer: So here you can see what we plan to do is not to really make
something new. so this is not a competition to other standards. So it is
more a composition of several things.

Nik Jenzer: as already said the VC data model for the verifiable
credentials. also something I do not really know it now is the proof
standard.

Nik Jenzer: This was a hint from colleagues from me that already use this
in the governmental sector for working and also an idea should be the solid
protocol.

Nik Jenzer: Yeah, nice one.

Nik Jenzer: why not to store the records the government store it on a solid
pot and also provide it to a citizen that they can save these records on
their own solid pots so that for example the driving license I can carry it
on myself as a citizen and show to the police as needed.

Nik Jenzer: and also be verified then okay and what we want to do is a lot
I hope so we can do a lot of proof of concept we will not only provide the
record web as a concept or a protocol and just publish it and that's it we
want to make a proof of it with several

Nik Jenzer: several really useful use cases. here is one that could be the
building permit.

Nik Jenzer: What I want to do is something more in the governmental part
and the idea is also that we publish these proof of concept or these use
cases in our repositories. Okay. this is why I am here.

Nik Jenzer: we had this idea of this record web and then I asked my
assistant and now what I'm having in my hands and how to proceed and then
the answer was yes of course you have to do a standard with it the question
was are we going to only ECH Swiss standard and my idea was no this is more
than that so we should also exchange

Nik Jenzer: information records with other governments. also our standards
are based on ISO standard. So my question was are we going more direction
to the ISO or we going to web3 standards? And then the idea was clear go to
W3C and I have no idea how to do this.

Nik Jenzer: So I came up with some community how to say this things I
posted also on your GitHub yes to look some on support to develop this
record web. So what we need then sorry no first of all the record web
protocol as it's written here is a single author foundation.

Nik Jenzer: So yes, it is basically my idea with support of AI discussed in
this technical group where we said okay we go further further now we want
to make it more so I'm now here this is the first time I present this in a
W3C community group so thank you very much for your interest and I'm also
here because as I understand

Nik Jenzer: is the VC compatibility profile will be something that you host
here.

Nik Jenzer: and even more the DID method and when we like to have our own
method specification then we need to register it and for this is something
I do not understand now but as I written here I'm seeking for a editor or
someone who can help us to do these things well and to check if are these
things really useful for

Nik Jenzer: our ideas and on a next level to bring them alive into a rec.
not only the concept but also the protocol more of a normative kind on how
to use this record.

Nik Jenzer: Also the solid integration is written here again this is not
the group I know just for you for information but it is not one of the core
things that we really need but it is something that I like to think about
it and also on this is the algorithm.

Nik Jenzer: This should be a minor. Is this shot at 256 still okay to go in
the next few years or should we change something there while hashing to the
snapshots then? Okay, where we stand today is really today.

Nik Jenzer: Of course the record web the C is for the concept and the P is
for the protocol are published as a defensive publication. This was the
idea that no one how to say can guard things or can do the idea is that the
idea the record web should be from the beginning really open and not a
closed idea.

Nik Jenzer: So there you can find the document itself.

Nik Jenzer: The number three at the end is the concept and I think the five
should be the protocol but this is not really needed just for information
because in progress no sorry first of all here on GitHub we have the
organization record web and in there we have several repositories at least
we have two one for the concept and the second for the protocol itself and
more should come

Nik Jenzer: for the proof of concept of course but hope so also for the DID
method and in progress is the WC Z record reps. so I proposed the ZG you
can find this is still ongoing. Does this work with the screen sharing?

Nik Jenzer: As you can see on the proposed

Nik Jenzer: post the record web community group is there and I'm looking
still for some sponsors so if you like it you can support the creation I
think we will complete this very soon my colleagues from the other
governments in Switzerland from the conton this is more the states of
Switzerland do support this but we started the holidays so it takes one or
two weeks to have them but if you like to support you can go for

Nik Jenzer: And of course we have the ECH record management technical
committee. This is where I'm coming from.

Nik Jenzer: What we plan there is to discuss the issues as a Swiss chapter
we can say and come back with a Swiss response and not only with a signal
from me as representing the Swiss government or other state representative.
So the idea is that we form there a kind of a Swiss chapter.

Nik Jenzer: And of course we have the proof of concept the first is in
there for the Swiss government and I hope so other will follow and what I'm
seeking is of course first of all is a editor from your community to help
me understand better what I need from you how does this work with the DID
and other things and hopefully also

Nik Jenzer: helping to make a record web as a W3C publication or how to say
a report and a normative document. I hope so. And the second is
institutions for PC but I think the audience here is not from the
institutions from the government. So this is what I'm seeking from other
countries.

Nik Jenzer: I'm there or I will start communicating this also with other
countries of course in Europe or around the world of course also with
Australia as a state for the record continue.

Nik Jenzer: So yes, this is what I had prepared to say.

Nik Jenzer: Okay. I hope I understood it right.

Nik Jenzer: Normally when we do in Switzerland some standards you can do it
the way you ask what we want to do this is my experience after this more
than 10 years it ends up in a hell a lot of discussions and you basically
can not come not to an end.

Nik Jenzer: So the better way is that someone come up with an idea, propose
this idea and then we discuss it and we change things and then it develops
much faster and this is the way I choose here.

Nik Jenzer: I got the job from my colleagues to start Greenfield and so I
started with a first idea and it is the first idea that doesn't mean that
it has to go really in this direction but it is a concept containing almost
everything but everything has to be discussed now is it this right or
wrong? Do we have changed things?

Nik Jenzer: Do we have to respect others? As I know for example our driving
guides they already have also a standard but not a technical standard more
awarding standard. So we have to adopt our wordings to confir to be aligned
with these wordings there.

Nik Jenzer: So the record web as it is now is just a first starting point
that you can discuss that you don't come group together and ask yourself
what we want to do but you can start on already existing idea of a concept
and say what is good on this idea? What needs to be changed?

Nik Jenzer: What is black spots we have to put the light on and where is
some other ideas or standards we didn't

Nik Jenzer: about.

Nik Jenzer: And finally, have a real new W3C standard. not as a standard,
but yeah.

Nik Jenzer: Yeah.

Nik Jenzer: Yes, I discussed this with Yan. he helped me to make the
proposal and then we changed several things in the description.

Nik Jenzer: So the concept will be as you described this community report
but the protocol and this where we decide to make this in a separate
repository and the license there is different.

Nik Jenzer: the protocol should a little bit more normative but I know this
will not be already the standard but it should be more normative and we
discussed it all already that the Swiss government or let me say this Swiss
standardization group they produce also standards and they can refer to
this normative description of the record web protocol and

Nik Jenzer: make this for the Swiss government already as a standard even
if it is not a 3 official standard. So we can make this normative in the
Swiss government and of course yes as you described when there is some
experience later we can level up then the record web if needed.

Nik Jenzer: Mhm.

Nik Jenzer: Mhm. Yeah.

Nik Jenzer: Okay. Yeah. if I can answer quick.

Nik Jenzer: I thought about it first of all to join an existing group but
then I also discussed it with my colleagues and what we then prefer is not
only to have technical people working together but also have the
governmental representation.

Nik Jenzer: So if I then said to my colleagues or other countries join the
CCG I think they have more question marks and concerns about what and how
to join and what is discussed there. in contrary if you have your own
records web with a terminology or a wording they do understand.

Nik Jenzer: So in the description of the community group is also noted that
we explicitly look for governmental people and let them join as a
governmental representation and I think with this it will be much more
easier also to have not only the technical guys as you are in the group but
more or less also how to say the people from the governments

Nik Jenzer: That's the main reason why we decided to go for our own
community group.

Nik Jenzer: yeah probably not the concept or the protocol itself but I
think when we need this DID method then that this should be part of your C
CCG I think and for this of course

Nik Jenzer: I think I need a core editor or am I wrong? Okay.

Nik Jenzer: this is where I'm not really used about the details of the W3C
stuff. So I'm not sure what I really need. So this is where I also need
some support.

Nik Jenzer: What I can say is I have the support of just give me a second
of Melvin Carvalo.

Nik Jenzer: as he will also share the community group as record web and I
think he will also or I hope him and he can explain me more in details what
I really need then and how to proceed because I'm not really comfortable
with all these technical details where to do

Nik Jenzer: Mhm.

Nik Jenzer: Mhm.

Nik Jenzer: Thank you very much for the chance.

Mahmoud Alkhraishi: Hi, Nick. How are you? Great. thank you for joining us
today. we're just going to wait for people to join in. It usually takes
five minutes to get started. and then I'll run the just, basic housekeeping
stuff. Then I'll turn it over to you. Hopefully, you have something for
40ish minutes. Excellent.

Mahmoud Alkhraishi: And then we're good, I guess. Yes. Yeah, you will be
sharing. so at bottom of your screen. Should be a share screen right next
to your mic video. Share screen. Perfect.

Mahmoud Alkhraishi: Yes it does. We're just going to give it a little bit
of time cuz Yeah. Thank you. No, we're just going to give it

Mahmoud Alkhraishi: Hi We're just holding off till the 5 minute mark before
we get started.

Mahmoud Alkhraishi: Hi, welcome.

Mahmoud Alkhraishi: All right, we're just going to give it one more minute
before we get going. Thank you all for joining us today.

Mahmoud Alkhraishi: All right. we're at the 5m minute mark. It is Tuesday,
July the 14th. Thank you everyone for joining us on this CCG call. a couple
of reminders of our code of ethics and professional conduct. Please make
sure that you adhere to it and thank you all for adhering to it so far.

Mahmoud Alkhraishi: IP note any substantive contributors to the CCG work
items must be members of the CCG with full IPR agreements.

Mahmoud Alkhraishi: Anyone of course can participate on these calls. do we
have any introductions? Are there anybody who'd like to introduce
themselves to All any announcements, anything people want to bring up?

Mahmoud Alkhraishi: On the chair's end, we do want to make note of asking
people if they have any topics they would like to speak about, if they have
any speakers they would like to recommend to us. So, please just reach out
to us. We are running low on the speakers list.

Mahmoud Alkhraishi: So if you have anybody that you think would be able to
submit something that is great or something that you want to hear about,
please do not hesitate to refer them to us. With that out of the way, Nick,
the floor is yours. Would you mind giving yourself quick intro, who you
are, and then let's get into the topic.

Mahmoud Alkhraishi: Yeah.

Mahmoud Alkhraishi: Thank you, this is wonderful so far. So, I know you
asked a lot of questions and a lot of asks from the community.

Mahmoud Alkhraishi: I'm going to turn it over to the community if anybody
has direct answers. If not, I'll do my best at answering some of these
things. And I also have questions of my own. So before we get there, does
anybody have any responses or questions they would like to bring up to Nick?

Mahmoud Alkhraishi:

Mahmoud Alkhraishi: Please.

Mahmoud Alkhraishi: Was there anything else you wanted to cover there? Are
you okay?

Mahmoud Alkhraishi: So on a similar note, I had a question of why you
wanted to start a proposed community group rather than just open a task
force within the CCG. This seems like something that would probably fit
within the CCG and it will probably be significantly less friction on your
end and it'll be a lot easier to get started and a lot easier to get people
to contribute if it is a CCG task force.

Mahmoud Alkhraishi: the end result would still be a report and you would
take that report as I was mentioning and you can promote it to some of the
W3C groups right working groups and from there you can actually go down the
standardization path right so just to reiterate Will's point a community
group cannot create standards and I understand that on the Swiss side you
can absolutely do that but for it to be a W3C standard it has to be from a
working

Mahmoud Alkhraishi: group. it does seem like so Ben I agree it is a little
bit wider than the CCG but we've had task forces before that are not
strictly defined within the CCG.

Mahmoud Alkhraishi: I think this would be the easiest way to incubate such
work and if it needs to move then it can move right the hardest part as
always with all these start getting started is to get people right and it's
a lot easier to do that if you don't have to bootstrap everything yourself
right so that's my biggest points and hopefully that would help

Mahmoud Alkhraishi:

Mahmoud Alkhraishi: All right, that's fair enough. does anybody else have
any comments or any questions they want to bring up to Nick Air seems
interested in being a co-editor if this is a CCG work item, but I think
Nick was saying it probably will not be.

Mahmoud Alkhraishi: So maybe this is a conversation for you guys to have on
a sidebar.

Mahmoud Alkhraishi: No, I mean I believe you need a Will, please correct
me, but I think on the DID side you do need two sponsoring companies,
right, to proposing.

Mahmoud Alkhraishi: I'm assuming it's going to start as a work item and
then progress from there to be a nuded method while they iron out the
initial parts.

Mahmoud Alkhraishi: All right. do we have any other comments or anything
else anybody wants to bring up? All right. then thank you everyone for your
time today. Thank you Nick for the wonderful presentation and talk to you
all soon.

Mahmoud Alkhraishi: Hog every day.

Lancine Toure: Hello everyone.
00:35:00

Lancine Toure: Thank you. All right.

Will Abramson: Hi, Yeah, I mean I think this is very interesting, right?

Will Abramson: It sounds like is there some work that

Will Abramson: you did by yourself with your AI to produce this but then
there is a community behind you right of Swiss government entities and you
mentioned some standards group or maybe it's a national standards body that
kind of has vetted because I was a bit hesitant when you said AI but it
feels it's quite interesting that you're in this domain and then you used
AI to discover how to take this out and it's already been validated so I
think that's great sort of stepping

Will Abramson: stepping stones to getting this adopted. My question was,
you set up a community group or you try and set up a community group at the
W3C and I was wondering whether this work item that you're trying to get
started is best under there versus under the TCG or maybe it's a collab
sort of thing. I don't know if you have thoughts about that particularly.
but yeah, I think it's very interesting stuff.

Will Abramson: Yeah. Oops.

Will Abramson: Just on that, I guess I would say, just to fill you in on
the W3C steps. So, it's called the credentials community group, right?

Will Abramson: We're a community group under W3C. We do not produce
standards. We produce community reports. I think they call final reports.
but it's important, what you're doing right now is socializing an idea to
this community of people who are also involved in the standards work at the
W3C.

Will Abramson: And what typically happens is we incubate work by taking it
through a process producing a final report and then if that work has
momentum and there are people who want to the next step is to take that
into a working group right to start either to start your own working group
under the W3C or to get it adopted by an existing working group and then it
goes through a process of standardization which usually takes as input that
final report that is this work item you're proposing
00:40:00

Will Abramson: and refineses it and then goes through the WCC ratification
process to become eventually a recommended standard.

Will Abramson: So as I think you see what you're aware right it's a long
and windy road with lots of discussion but this is absolutely the right
place to start I think

Will Abramson: No, no, that was great.

Will Abramson: Yeah, thank you.
00:45:00

Will Abramson: I'm a bit confused. Are we talking about proposing a new did
method? what is that correct, Nick?

Will Abramson: Mhm.

Will Abramson: Yeah. Mhm. Yeah.

Will Abramson: So I mean it sounds to me like you're looking to the CCG for
technical support around the standards that we are quote unquote experts in
right decentralized identifiers and verifiable credentials and I think
that's great that is absolutely the right place to ask and I guess for
anyone listening on this call that's interesting I mean I think reviewing
your work item proposal and the document in there is a good place to

Will Abramson: start whether that becomes a work item in here or not.
Right? That's kind of like a summary of where you're at.

Will Abramson: And I think also as you, progress and learn more maybe
through conversations with Melvin, just figuring out what it is you need or
the questions that you really need are helpful, I think we can always do
another call or, you can use

Will Abramson: the mailing list is a great place to kind of reach out with
specific asks, but absolutely we as a CCG, I think are happy to where
reasonable and possible to support you and help you figuring out how to use
divs for your use case like that. I'm happy to help for sure.

Will Abramson: Yeah. Thanks,

Amir Hameed: Thank you everybody.
Meeting ended after 00:49:07 👋

*This editable transcript was computer generated and might contain errors.
People can also change the text after it was created.*