-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In message <[email protected]>, Mauro De
Gennaro <[email protected]> writes
>The other point concerns header field names in
>recipes. It is not entirely clear from the text whether the JSON keys must be
>lowercased or may retain their original case.
currently up to you ... but the spec does say
Matching of header field names is always done without regard to case
and there MUST NOT be JSON keys that differ only in case.
> Steve's implementation expects
>lowercase and rejects mixed case,
that is not aligned with the current spec.
But we could say that header field names should be lower-cased... for
simplicity (but then we need an error message for a validator to
complain when they are not).
RFC6532 makes it clear header field names are in ASCII so this is not at
all problematic. I have not put this into spec-04 since there are no
other comments on the issue so far.
- --
richard @ highwayman . com "Nothing seems the same
Still you never see the change from day to day
And no-one notices the customs slip away"
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1
iQA/AwUBakp01WHfC/FfW545EQJhmgCgjSfNcUWQkpnvnhtw7QCI+S9Uf5MAn07v
FNkm+axkrRTr5W7miQxIC+Y5
=PFYF
-----END PGP SIGNATURE-----
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
