hi michael
having said that: thinking of a ValueFactory implementation
in oak-jcr that creates Value objects that can server both as
jcr-values and oak-values. the internal representation could
still be anything including json-representation... but we
wouldn't be limited to JSON types on the API level.
This sounds like an interesting idea. It kind of covers the middle
ground between both approaches. Only that I'd put that implementation
into oak-core, not into oak-jcr.
fine with me.
i didn't dare suggesting this as it would be yet another
reason for having a dependency to javax.jcr in the oak-core
project... (which i don't have too much problem with).
angela
