OIDF-automation

### Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda duplicate of #24 .

### Imported from AB/Connect bitbucket - Original Commenter: mbj Having multiple ways to do something is generally a red flag and can result in interop problems. How can we get...

### Imported from AB/Connect bitbucket - Original Commenter: danielfett I see that the transaction\_id is not included in the possible responses of the pre-auth code flow, but I couldn’t find...

### Imported from AB/Connect bitbucket - Original Commenter: dwc8 @Jeremie commented “I have immediate concerns about the security implications of adding any schema definition to the metadata. Is the client/consumer...

### Imported from AB/Connect bitbucket - Original Commenter: dwc8 @Kristina Yasuda asked for descriptive text to be added to PR#241. The following is a strawman proposal “Credential `types` and `schemas`...

### Imported from AB/Connect bitbucket - Original Commenter: mbj I don’t believe there’s a standard schema for JSON that’s widely deployed. That argues against doing this. It’s also not clear...

### Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda discussed in SIOP Jan-12-2023 call. Direction was that it makes sense to add schema parameter to the credential issuer metadata. A...

### Imported from AB/Connect bitbucket - Original Commenter: dwc8 Verifier discovering the issuer’s schema is unrelated to #1551 \(as this discusses how the wallet can trust the verifier\). The answer...

### Imported from AB/Connect bitbucket - Original Commenter: tlodderstedt Closed PR #241

### Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda Discussed during 2021-12-16 SIOP call. We discussed that if we are to use polling, this parameter makes sense. it was suggested...