Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vehicle DID structure #2

Open
johnx25bd opened this issue Feb 3, 2020 · 1 comment
Open

Vehicle DID structure #2

johnx25bd opened this issue Feb 3, 2020 · 1 comment
Assignees

Comments

@johnx25bd
Copy link
Member

johnx25bd commented Feb 3, 2020

Proposal to include an additional field in the DID for vehicles, indicating vehicle type.

This could be used as a condition in smart contracts, and to enable more sophisticated visualization in the browser.

Thoughts?

* "@context": always the same as above. 
 * "created": timestamp of when the DID is created. 
 * "entity": can be "device", "company:company name", or "individual". 
* "vehicleType": "car:ev", "car:hev", "commercial:lorry", "ship:container", "ship:tanker", etc.
 * "creator": optional, only used if its a device DID. 
 * "imei": optional, only use if its a pebble tracker
@jason-james
Copy link
Collaborator

Yeah let's do it.

Btw, we are being liberal with the DID document at this point, I'm not sure that we are 'permitted' by the DID spec to have extra fields like imei, entity, vehicleType in a DID document, they are probably more suited to a "verifiable claims" JSON, but I can't find any reference to where a verifiable claims document will be stored and how to link it to a DID.

But its a hackathon and a new concept so I'm comfortable doing it this way for now..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants