OIDF-automation

### Imported from AB/Connect bitbucket - Original Commenter: mbj It’s absolutely appropriate for specs other than the Federation spec to define any new entity types that they need. As discussed...

### Imported from AB/Connect bitbucket - Original Commenter: mbj A week has passed with no further comments. Closing during the 20-Jan-23 Federation Editors' call, as proposed last week.

### Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda I think we were discussing if we need a text in openid4vc specs and I don't have an answer yet. it...

### Imported from AB/Connect bitbucket - Original Commenter: peppelinux I’ve learned that Verifiers/RP uses "client\_metadata" as defined in OpenID4VP. It's so wide ... considering that it is a just VC...

### Imported from AB/Connect bitbucket - Original Commenter: peppelinux The new entity types proposed, as a result of the experience of the implementers, are listed below: - wallet\_provider - wallet\_relying\_party...

### Imported from AB/Connect bitbucket - Original Commenter: oliver-terbu Is there a mechanisms that already exists that would allow the wallet to obtain the Verifier Metadata from a .well-known URL?...

### Imported from AB/Connect bitbucket - Original Commenter: alen_horvat In simple cases, yes, in more complex cases no. When verifier is always asking the same claims \(only 1 scope exists\),...

### Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda `client_metadata_uri` does not have to be static. How I have seen people solve the issue you are describing is by putting...

### Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda please see PR#524. it adds a client\_id\_scheme using a sender constrained JWT in a header which I think is very close...

### Imported from AB/Connect bitbucket - Original Commenter: EECC I think the link is wrong. It refers to an issue from 2012 which does not appear to be related. My...