On 2012-04-12 23:46, Michael Dürig wrote:
...
I'd ideally like to keep it JSON-like so we can easily implement a
JavaScript-friendly HTTP mapping directly based on the Oak API without
having to go through extra levels of mapping.
Hmmm, seems reasonable. What about Angela's concerns?
Michael
...
That means that the JCR<->JSON mapping we define here effectively would
become the mapping used in JSOP (if we ever get there), so it would be
part of a public protocol contract.
Not saying that this is a bad idea, but we need to be aware of the
consequences :-)
Best regards, Julian
