> IMHO you should add a special resource for getting the property types. > An easy way to do so is by using selectors, eg. > > /foo/bar.metadata.json > Ok, I can do that, but then who would use which in what situaions? (That was a mouth-ful :-P) I may not fully understand how you guys envisioned using the JSON renderer so I'd like to understand that.
> where "metadata" is the selector. And the json would give you the > metadata of the node, for example with a sub-object (in json) for each > property and then all the property type data as key-value pairs. > > That way you don't have to mess with the standard json rendering and > you don't have to find a solution for the is-not-an-object problem. > Ok, I'll have a look at doing that. > Regards, > Alex > Cheers, Craig
