You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In all the examples, the JSON object is not specified. One has to look inside the type parameter to find out what sort of JSON object it is. However, when the object is embedded in another object e.g. credential inside profile, then the object type is specified. I therefore suggest that each object should starts by stating what type of object it is. Thus Example 1 would become
@David-Chadwick adding that to the example content would make the JSON invalid, so I'd be 👎 on adding credential: or profile: to either of the examples (or any of the others).
Example code gets copy/pasted frequently, so adding anything that would make it invalid is inhibitive.
In all the examples, the JSON object is not specified. One has to look inside the type parameter to find out what sort of JSON object it is. However, when the object is embedded in another object e.g. credential inside profile, then the object type is specified. I therefore suggest that each object should starts by stating what type of object it is. Thus Example 1 would become
This would have the added advantage that the first value from the type property can be omitted.
and example 17 would become (removing any reference to JSON-LD)
Example 17: A simple verifiable profile in JSON Format
The text was updated successfully, but these errors were encountered: