Closed chris2286266 closed 3 years ago
Would it be possible to allow for either n
or gn
/fn
as a compromise?
anyOf:
- required:
- n
- required:
- fn
- gn
IMHO Yes.
@chris2286266 why add a new file? I suggest we just keep adding to v1 for now.
Why do you want to add any certificate metadata to the hcert payload? As this information is bound to the key, it is part of the trusted list metadata - not the payload itself. IMHO, there's no reason for having take up vital information in the payload.
Please elaborate so we can better understand the use.
Why do you want to add any certificate metadata to the hcert payload? As this information is bound to the key, it is part of the trusted list metadata - not the payload itself. IMHO, there's no reason for having take up vital information in the payload.
Please elaborate so we can better understand the use.
Sorry for my probably inaccurate wording,
I of course meant the meta data of the health certificate, not of the signature certificate!
The requirements to integrate this meta information into the "hcert" come from the eHN guidelines. Viz. e.g. https://ec.europa.eu/health/sites/health/files/ehealth/docs/vaccination-proof_interoperability-guidelines_en.pdf
Regards, Chris
@chris2286266 all good, my cryptoself triggered on the word "metadata" and "expire". No worries!
I think we are talking the eHealth digital green metadata -- not the X.509 like data on the key.
As I am not aware of the "rules" within this team: who will/shall ... merge the PR? Can/shall I do it? Or does someone have to confirm it?
closes #1