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

Support for non-DID based trust frameworks #47

Open
sloops77 opened this issue Jun 4, 2024 · 3 comments
Open

Support for non-DID based trust frameworks #47

sloops77 opened this issue Jun 4, 2024 · 3 comments

Comments

@sloops77
Copy link
Contributor

sloops77 commented Jun 4, 2024

Trust frameworks like OpenId Federation currently are non-DID based. https://openid.net/specs/openid-federation-1_0.html

I would like to see a spec broad enough to support TOIP being used in non-DID environments, otherwise we just have more bifurcation

@andorsk
Copy link
Contributor

andorsk commented Nov 28, 2024

We're doing issue cleanup and we noticed this was never addressed. We'll bring this back to the front.

We have a few OIDF implementors generally on the TRTF calls. We will surface this issue to them to understand better how we can make sure OIDF based implementations are supported in the TRQP.

@andorsk
Copy link
Contributor

andorsk commented Dec 5, 2024

@darrellodonnell to do a quick write up on URI vs. DID.

@andorsk
Copy link
Contributor

andorsk commented Dec 5, 2024

@ScottPerryCPA discussed on TRTF Call December 5 : Good starting point to discuss this is what is an identifier. Placeholders in for identifiers. Have some resolution mechanisms. Core spec.
@talltree : Should be a URI at a minimum.

@andorsk

graph TD 
   subgraph spec
     coredatamodel 
   end
   spec -->|  describes the identifiers and resolution mechanisms | profile
Loading

@darrellodonnell : do not need to put a profiling mechanism into the specification.

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