[Json] Leading and trailing whitespace

["Jim Schaad" <[e-mail]>]

The current specification allows for arbitrary whitespace to occur before
and after an array or object.  I would like to know if this is what was
intended to begin with or not.

There are two different things that could be done about this (one of which
would potentially be necessary if you allowed all values in a JSON-text.


1.  Some of the ABNF could be cleaned up to eliminate situations where you
end up with two ws non-terminals in a row.  Thus the ABNF could be modified
from

   JSON-text = object / array

      begin-array     = ws %x5B ws  ; [ left square bracket

      begin-object    = ws %x7B ws  ; { left curly bracket

      end-array       = ws %x5D ws  ; ] right square bracket

      end-object      = ws %x7D ws  ; } right curly bracket

      name-separator  = ws %x3A ws  ; : colon

      value-separator = ws %x2C ws  ; , comma

      object = begin-object [ member *( value-separator member ) ]
               end-object

      member = string name-separator value

   array = begin-array [ value *( value-separator value ) ] end-array

to

JSON-text = object / array
begin-array = %x5B  ws ; [ left square bracket
begin-object = %x7B ws ; { left curly brace
end-array = ws %5D ; ] right square bracket
end-object = ws %7D ; } right curly brace
name-separator = ws %x3A ws ; : colon
value-separator = ws %x2C ws ; , comma

If needed then JSON-text would become either
JSON-text = ws value ws 
Or
JSON-text = ws object ws / ws array ws

2.  There is nothing in the current parser or generator text which says what
to do if you come across a string which either has leading/trailing white
space or a string which has a complete JSON-text string followed by
non-white space characters.   I would hope that the second case should cause
either an error or some other indicator that the entire string was not
consumed.  I am slightly agnostic about the first case but would kind of
like to eliminate leading and trailing whitespace.


Jim