We’re attending the main call for the W3C Credentials Community Group and we have our own repository set up in line with the work item that was approved by W3C. The repo is empty at the moment.
We have some things to do to establish a presence there so they can help us better. We need to set out some tangible deliverables that make sense both for us and the wider community of folks at CCG.
If there is anything significant we need to get published for wider relevance, beyond co-ops, we need to define it properly in a way that the wider CCG audience can understand it. They have a lot of ‘protocol’ around this and some useful templates. More formal definitions of our use cases would be a great place to start!
I have reported back to them that we are making good progress with engagement of other co-ops and in getting research underway. They’re keen to hear from us, so after our own community call maybe we could give them an update on our status and plans and list some questions so that we can get wider advice, especially on VC standards.
On this week’s call we talked about status of the new version of the VC spec v1.1 which is coming up for approval and about the work item process.
We also talked about a new work item proposal this week to have VC’s automatically refreshed in the background if they are expiring. This makes it easier to have short-lived credentials. It is based on the VC API work done in another task force. Looks very useful for managing risk around credentials and also in prompting manual checks when they are necessary - just like an expiry date on a paper document or inspection certificate.
The (very full!) archive of the minutes of all the meetings is here: