Hi, >>My thinking was to make this opaque to oak-core. That is, set the value >> of the path property to the jcr path and let oak-jcr handle it. Unless >> there is a case (which might well be) where we need to dereference such >> paths properties from within oak-core this should work.
I don't think this will work for the query engine. Similar to namespace mapping, node types, the query engine in oak-core will probably have to resolve relative path as well, maybe even at execution time. Regards, Thomas
