Mahesh_Balan_-_pocketcred.com: Yeah my name is Mahesh pollen and I'm new to this group but have been active in a few others like the VCI initiative and so on and so forth I had that great you know fortunate to meet Carrie in the recent iiw and I'm interested in this whole area of verifiable credentials for learner brackets so thank you. ✪
Julien_Fraichot: The site so yeah I've been you know the course he do we see what the men we see chapter 12 and I guess I'm interested there on the what this call discusses and not I mean this similar time zone I'm not in Europe it's falling on a easier time for me to join so I'm just gonna see if there's something relevant for me here so. ✪
<dmitri_zagidulin> (yeah, the VC display part would be of more interest to general CCG and VC-WG)
<phil_l_(p1)> What about the VP layer?
<dmitri_zagidulin> @Phil - the VP layer is assumed
<dmitri_zagidulin> (meaning, the VC Exchange API deals in VPs specifically)
<dmitri_zagidulin> we should have an example OBv3 badge in a day or two.
<kerri_lemoie> Thanks @Andy!
<kerri_lemoie> This is great
Topic: VC-API interoperability test suites
Topic: IssueCredentialResponse does not allow for metadata
<dave_longley> "last passing date" could be some meta data in the test suite for a given implementation and test
<kayode_ezike> My thoughts exactly @Dave
<mike.varley> tests are in git - maybe we can use git tags to help here?
<tallted> Some semblance of semantic versioning with pre v1.0 during experimental phase can be useful... Implementations that happen pre v1.0 are inherently experimental, and can be usefully labeled as "targeting v0.75" or whatever for interop (e.g., "targeting 0.4" may not be expected to interop with "targeting 0.75").
<mike.varley> Maybe tests, rather than implementations, can have the "last updated" tag...