[MINUTES] Data Integrity 2025-08-29

Meeting Summary: Data Integrity - 2025/08/29

*Attendees:* Benjamin Young, Phillip Long

*Topics Covered:*

   - *Meeting Cancellation:* The meeting was cancelled, as indicated by a
   (presumably) emailed notification and lack of calendar entry.
   - *Can I VC Playground:* Discussion focused on the Can I VC playground
   (a test results aggregator for W3C test suites), specifically its handling
   of Verifiable Credentials (VCs) versions 1.1 and 2.0.
   - *OBV3 Implementation Issues:* Challenges with OBV3 (Open Badges v3)
   implementations were raised. Implementers supporting both VC 1.1 and 2.0
   face difficulties due to schema differences, leading to confusion and
   warnings during compliance checks. A recommendation was made to simplify
   implementations by focusing on the latest specifications.
   - *Playground Support for OBV3 and VC Versions:* The discussion covered
   the Can I VC playground's ability to handle OBV3 implementations using
   different VC versions. It was confirmed that the playground itself is
   version-agnostic, but the verifier used downstream determines compatibility.
   - *Improving Playground Integration Partner Information:* A need for a
   more dynamic and informative system for integration partners to specify
   their supported VC contexts and versions was identified. This would improve
   the user experience and clarity of the playground.

*Key Points:*

   - The Data Integrity meeting was unexpectedly cancelled.
   - The Can I VC playground supports both VC 1.1 and 2.0, but downstream
   verifiers dictate compatibility.
   - OBV3 implementations are causing confusion due to support for both VC
   versions without clear specification of which is used. Simplifying to the
   latest version is recommended.
   - The Can I VC playground should dynamically display which integration
   partners support which VC versions, improving transparency and usability.
   Currently, this information is manually added by partners and is not always
   up to date. A system for automatic exchange of this information among
   partners would be beneficial.

Text: https://meet.w3c-ccg.org/archives/w3c-ccg-data-integrity-2025-08-29.md

Video:
https://meet.w3c-ccg.org/archives/w3c-ccg-data-integrity-2025-08-29.mp4
*Data Integrity - 2025/08/29 10:01 EDT - Transcript* *Attendees*

Benjamin Young, Phillip Long
*Transcript*

Benjamin Young: Hey, Philip.

Phillip Long: Hey Ben,…

Phillip Long: how are you?

Benjamin Young: I'm not sure this call is happening, though. Not much of a
crowd here.

Phillip Long: That's what I'm wondering. And I wonder if No, I'm but I
remember I thought of saying it would continue today from the last meeting.

Benjamin Young: Yeah. Yeah. This one's a weird one because it doesn't show
up on the W3C calendar, so I don't think Right.

Phillip Long:

Phillip Long: It doesn't. that in general it doesn't.

Benjamin Young: In general, it doesn't.

Phillip Long: It is. Hold on a second. let me just look.

Benjamin Young: Maybe it does. Yeah, it does. And it's not Yeah,…

Phillip Long: Yeah. No, joining instructions are here. where's is that…

Benjamin Young: I think it's data integrity canceled for August 29th.

Phillip Long: was there an email?

Benjamin Young: Yeah, I didn't see an email, but here's the link.

Phillip Long: You must have put it in chat here.

Benjamin Young: I put it in this chat.

Benjamin Young: Yeah. …

Phillip Long: Okay. but you have Yeah,…

Benjamin Young: I don't know when it was cancelled. Do it.

Phillip Long: that's fine. That's great. I could use the time.

Benjamin Young: Yeah, it's fine by me. Yeah, no kidding. Can't we all?

Phillip Long: Yeah. All right.

Benjamin Young: It's good to chat for a second.

Phillip Long: Let's just assume it is. Nice to see you. I have a quick
question while you're here.

Benjamin Young: Yeah, Yeah. the VC playground.

Phillip Long: You guys maintain what's the current name of the playground?
Yeah. Does it have a new name?

Benjamin Young: Yep. …

Phillip Long: I thought it had a new acronym Yes,…

Benjamin Young: are you thinking of Can I VC?

Phillip Long: that's what I'm thinking.

Benjamin Young: So, that's test results.

Phillip Long: That's what Right.

Benjamin Young: Test results from the W3C test suites aggregated in a sort
of a promotional view of…

Phillip Long: Right. Yeah.

Benjamin Young: how the community is doing.

Phillip Long: And I guess the question I was wondering is There is for
those folks that are doing the OBV3 ver in the one tech style it's kind of
a mess at the moment…

Benjamin Young: Right. Okay. Yeah.

Phillip Long: because they claim to support both VC 1.1 and 2.0 versions.
the problem is of course that if that's the case then you have to be very
explicit about which schema you're using and the like because they differ
and so they're running what they did at their end when people are checking
compliance they raise a warning that when they haven't chosen either the
right schema or the right version of the right context file and…

Phillip Long:

Benjamin Young: H. Okay.

Phillip Long: and it's causing some frustration on the part of new
implementers…

Benjamin Young: Interesting.

Phillip Long: who are not sure whether this is really a problem or how to
resolve it and…

Benjamin Young: Yeah. right?

Phillip Long:

Phillip Long: and the So, we had a meeting yesterday at one edtech to talk
through it and we urged them, Carrie and I urged them to simply choose the
most recent stuff and drop the rest.

Benjamin Young: Especially for new implementers,…

Phillip Long: Yeah,…

Benjamin Young: I would think, …

Phillip Long: Right.

Benjamin Young: But it really depends on who your integration partners are.
So, we support both, but a whole lot of our kit from the last five years is
1.1.

Benjamin Young: So some of our rollouts are not up to speed yet with VC2
and if we have to do a new integration with that then we have to go use VC
1.1. So it's the transitional time that's trick tricky.

Phillip Long: That's exactly right. And a lot of people who have been
implementing OBV2 all these years which is the nonVC version of this are
now transitioning to this one.

Benjamin Young: Right. Right. Yeah.

Phillip Long: And so unfortunately, from my perspective, the language that
they used in the description of the OBV3 recommend spec uses and has
sections that are only relevant to people…

Phillip Long: who are familiar with the prior platformbased implementation.
badge classes and…

Benjamin Young: Yeah,…

Phillip Long: things like that…

Benjamin Young: Right.

Phillip Long: which don't have any place. and that's what's adding to sort
of some of the confusion I think.

Benjamin Young: Yeah, no doubt.

Phillip Long: So yeah.

Benjamin Young: Another moment.

Phillip Long: So I just wanted to alert you to that. we've made the
recommendation that they move it forward. I think they're in agreement with
doing so and…

Benjamin Young: Yeah. Yeah.

Phillip Long: I think it's not sufficiently changing in the actual spec to
require them to go back to have a technical review and…

Benjamin Young: …
00:05:00

Phillip Long: all of this stuff that you would do for a minor release
update.

Benjamin Young: that's good. Yeah. Yeah.

Phillip Long: So I just have heads up about that because we want to be able
to point people to the playground when they're looking at OBV3s as well and
have it work there. But if they're going to send you a U I'm not sure what
it would work out to be…

Phillip Long: if they sent you an OBV3 that was in the 1 VCDM approach to
what would the playground do with that?

Benjamin Young: The playground right now won't care.

Benjamin Young: It supports both.

Phillip Long: Okay. Mhm.

Benjamin Young: The playground itself actually doesn't do a lot with the
VCs. It will issue them with VCJS which supports both and then it will pass
them off to a verifier. so it does only minimal things and you can
configure it to work with other issuers besides the BCJS one in which case
it's going to be on that other issuer…

Benjamin Young: what they support and we need to do a pass on the
playground that makes it clear what each integration partner will say
supports in terms of context and

Phillip Long: Right. Right.

Phillip Long: So when you pass it off to the verifier, it depends on what
the verifier is going to be expecting at that point.

Benjamin Young: Right. Right.

Benjamin Young: And I think there's almost a whole specification space that
doesn't exist yet…

Benjamin Young: where these groups can publish…

Phillip Long: it. Yes.

Benjamin Young: what they do support and at least exchange it between
shared partners because just straight up publishing it could be
problematic, if you had a DMV that says we support a bunch of old stuff
that has problems and they advertise that in their list of context and
things and don't clearly support the new stuff that fixes those problems,…

Benjamin Young: then that could get them in trouble. But there may be
reasons why that's the case that it may be another year or whatever.

Phillip Long: Yeah. Yeah.

Phillip Long: In internally.

Benjamin Young: But there still needs to be able to say we have an
agreement to share information about contexts and…

Phillip Long: Yeah. Yeah.

Benjamin Young: versions and whatever and we have some sort of handshake
for advertising that to each other and then the playground interface could
then adapt to that. So, when you go on the VC2 tab, it would only show you
the ones that are and it does do that but that content is manually added by
the integration partner. they have to opt into saying they support VC2.
we're not assuming people do, but that also means…

Phillip Long: Right. Right.

Benjamin Young: if somebody adds it to their implementation and doesn't
tell us, that's a missed opportunity because then they're not showing up in
the right category. So I'd like it to be more dynamic.

Phillip Long:

Phillip Long: Yeah, you're right. it'd be nice if it would be more dynamic
and probably needs to have some more explicit guidance for the folks to
know what the steps are and their obligations.

Benjamin Young: Yeah. Yeah. Exactly.

Phillip Long: All thank you. Appreciate it.

Benjamin Young: Yep. …

Benjamin Young: You're welcome, Phillip. It's good to see you again.

Phillip Long: And good to see you, too. And have a great weekend.

Benjamin Young: All right.

Phillip Long: Long weekend,…

Benjamin Young: Take care.

Phillip Long: hopefully. …

Benjamin Young: Yeah, I I'm looking forward to rearranging some house
stuff. I'm moving my office to the attic and my kid down to my office. And
so, we got big plans.

Phillip Long: that's good. I hope you have the air conditioner up there.

Benjamin Young: Hope you do. Yeah, We do. It's actually cooler than my
downstairs southacing windowed office. So, I'm looking forward to All
right,…

Phillip Long: That's All right. Good luck. Bye-bye.

Benjamin Young: take care, Yeah, thanks. We'll see you.
Meeting ended after 00:08:38 👋

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