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?
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?