Re: [stir] Proposal for update of erratum #6519 - ppt syntax

[Christer Holmberg <[e-mail]>]

Hi,

>There are quite a few people who use ABNF grammars to create field parsers or validators. Providing them with the most specific grammar possible makes their job easier.

In general I agree. But, people should not have to modify their existing parsers if they can already handle both quoted and non-quoted ppt values.


>In general, they would not need to update the parser. The critical point here is the opposite. We do not want to require that anyone who only supports quoted tokens as the ppt value would have to >update their parser to support the quoted strings. If they choose to support full quoted strings and then accept a wider range of values (like accept spaces around the token), they can do so without >causing any interop issues. As long as they do not send anything that does not match the grammar, this is acceptable.

That's why I said that we should only allow token inside the quoted string, not having to deal with spaces etc.

How does the suggested "DQUOTE token DQUOTE" syntax prevent spaces between the quotes and the token characters?

Regards,

Christer