On 4/25/17 17:19, Elwyn Davies wrote:
>From JSON to RFC 6690:
- Remove the double quotes from the JSON string value and do any
necessary decoding and encoding. Reapply double quotes. Note that
this may result in values that were originally not enclosed in double
quotes in the RFC 6690 repreentation becoming enclosed in double
quotes. However, [AFAICS] this does not alter the semantics of any of
the predefined parameters. For example the ABNF productions mean that
ct=40 and ct="40" are equivalent (the second case is needed so that
one can also have ct="40 41 42"). What IS needed is a statement that
this must also apply to any application specific parameters. For
example the case in examples 4 and 5 of ..;foo="bar";foo=3;...
transforming to "foo":["bar","3"] and then back to
...;foo="bar";foo="3";.. MUST require that the two RFC 6690
representations are equivalent.
This has the reciprocal problem that using quotes with (e.g.) sz and
hreflang is a violation of the ABNF in RFC6690.
/a