search

TBD54566975 / web5-spec

https://tbd54566975.github.io/sdk-report-runner/
Apache License 2.0
6 stars 5 forks source link

Make a distinction between what we accept and what we create #140

Open nitro-neal opened 3 months ago

nitro-neal commented 3 months ago

Maybe another column here: https://github.com/TBD54566975/web5-spec/blob/main/spec/vc.md

Basically for example: We accept an issuer that is a {id:"myid", name:"myname"} and internally we represent as string.

Another example is the @context object on did document. It can be a string, string[] or a list of ordered maps. We can consume a list of ordered maps but in the end it will be a string[]

Just maybe need the distinction / new column on what our data model internally is vs what we accept from the outside

decentralgabe commented 3 months ago

@nitro-neal I am wondering if we should avoid this until we encounter a case where what we accept is different than what we produce. do you know if we've had this happen?