Joel Thorstensson

A json-schema for the basic profile could look something like this: ```json { "$schema": "http://json-schema.org/draft-07/schema#", "$ref": "#/definitions/BasicProfile", "definitions": { "BasicProfile": { "title": "BasicProfile", "type": "object", "properties": { "name": { "type":...

Great suggestions @PaulLeCam! A few thoughts: ISO for nationality and birthDate make sense. For gender, the ISO you linked seem to be about *sex* not *gender*. We specifically want to...

> maybe we can still define an enum of value if there is no standard so that developers can know what to read/write? People are quite sensitive about their gender....

For sure @sylar217 That's entirely possible and I imagine you have much more information about you're profile which you might not want to share publicly on a decentralized network. So...

I like this structure generally. It's clean and keeps the validation part as one complete package. The main problem with this is that we use it in the `@ceramicnetworkdoctype-caip10-link` package...

Here is a PR in ceramic that could potentially mitigate the issue mentioned above: https://github.com/ceramicnetwork/js-ceramic/pull/668

Thanks for you comment @ericelliott! With regards to privacy, there are a few ways this is be addressed. The most straight forward one is just encrypting the content of any...

Hey @vongohren We've presented Ceramic and IDX to both DIF and the Credentials community. There is definitely a lot of synergies between IDX and SDS and other emerging standards! Just...

⚠️ This repo is being deprecated ⚠️ The cosmos implementation isn't finished yet either.

The schema for this is a bit tricky. There is a regex that matches the key and the value of the map: ```json { "$schema": "http://json-schema.org/draft-06/schema#", "$ref": "#/definitions/AccountLinks", "definitions": {...