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
Continuing from #8, this group should focus just on business data modeling, use cases, and policy - not attempt to define technical specifications. I suggest we don't list concrete formats on https://uncefact.github.io/spec-untp/docs/specification/VerifiableCredentials, but rather describe the general 3-party model, and let that settle in the technical communities where it belongs.
The text was updated successfully, but these errors were encountered:
very happy to leave technical stuff to technical communities. But we also need to define something concrete and implementable. What about making explicit references to existing technical community work like the DHS SVIP interop profile - and all we do in the UN spec is say that technical implementations of DPP, conformity credentials, etc etc SHOULD (or MUST?) conform to the reference technical interop profile/version?.
Continuing from #8, this group should focus just on business data modeling, use cases, and policy - not attempt to define technical specifications. I suggest we don't list concrete formats on https://uncefact.github.io/spec-untp/docs/specification/VerifiableCredentials, but rather describe the general 3-party model, and let that settle in the technical communities where it belongs.
The text was updated successfully, but these errors were encountered: