Re: resources

you could use something more elaborate if you've got the need,
although we haven't seen that here.  i originally meant, however, only
that there aren't even any : or = in it.  quoted strings are provided,
but even they are trivial to parse.  in fact, the entries can be
parsed by String->unquoted (same as tokenize in 9) which is a lot
smaller and simpler than even most sexp implementations i've seen,
with perfectly adequate functionality here.

for a structured-data file system, xmlfs, which allows navigation of
an XML file through the file system, and can therefore produce trees
when read, i do use a more elaborate syntax--
thing[innerthing[mostinnerthing], innerthing2[]]--that might be
slightly harder to parse than s-expressions.  i chose it because Xduce
used it.  originally i intended to present xml subtrees in xml but of
course it's too much code in the client to read that in, so i adopted
the Xduce notation.  short definition; easy to parse.