Add KBC schema

[tomdaffurn]

No description provided.

[frankhinek]

@tomdaffurn @mistermoe Should we rename this repo to be more generalized if we're going to include both KCC and KBC specs / schemas? Similar to the issue @decentralgabe raised.

Another thought is that we could create a schemas or json-schemas sub-directory in this repo, which would make it simpler for automating hosting.

[decentralgabe]

I would prefer we used this version everywhere, just noting that the other schemas use draft 7.

I'd recommend keeping this and let's take an action to update the other schemas.

[decentralgabe]

We also need to make sure our libs are set up to handle 2020-12

[mistermoe]

lib support for 2020-12 is largely untested at the moment. we know for a fact that 07 works. if we can get someone with cycles to test 2020-12 across several languages or even just rust, js, go, and dart that'd be awesome

[decentralgabe]

should we also add id as a top level required property?

[decentralgabe]

noting that the regex for date-time is not quite conformant to xml date time as required by the spec

you can find a full regex for xml date time here https://github.com/w3c/vc-data-model/blob/main/schema/verifiable-credential/verifiable-credential-schema.json#L216

[tomdaffurn]

@tomdaffurn @mistermoe Should we rename this repo to be more generalized if we're going to include both KCC and KBC specs / schemas? Similar to the issue @decentralgabe raised.

Another thought is that we could create a schemas or json-schemas sub-directory in this repo, which would make it simpler for automating hosting.

Moved to a dir 👍 We should have a conversation about where the schemas should live. I'll post about it elsewhere

[mistermoe]

hesitant about 2020-12 for the reasons explained in the comments i left. aside from that looks good!