What's so important about having your format not use quotation marks? Chances are there's something else you could change to make that requirement go away (which would be better).
As far as using regular expressions to parse JSON-like formats, no. This is a BAD idea; regular expressions were never really intended to parse recursive structures like JSON. At the very least you'll run into issues with performance of the many regex matches you'll need to use to attempt to deal with recursion; at worst you'll run into snafus of attempting to even sort out how to match and parse recursion in the first place.
Your format as proposed has its own issues, as well: how do you differentiate between a ,
, {
, or :
in the value of a key, and the actual ,
, {
, or :
that's part of the format? How do you deal with spaces in key or value names?