Skip to content
This repository has been archived by the owner on Feb 6, 2023. It is now read-only.

oem-id and class-map.vendor #122

Open
nedmsmith opened this issue Aug 24, 2021 · 0 comments
Open

oem-id and class-map.vendor #122

nedmsmith opened this issue Aug 24, 2021 · 0 comments

Comments

@nedmsmith
Copy link
Collaborator

The vendor in class-map is type text (tstr). The rationale for this is it only needs to match a value chosen by the Endorser who also choses the format / value in Evidence. It could be base64 encoded binary, URI or just text. The verifier is only looking for a match.

The EAT oemid Claim doesn't allow tstr but does define 3 binary alternatives. Does it make sense to make vendor a type choice so that a oemid could be used?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant