[
https://issues.apache.org/jira/browse/OAK-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285670#comment-13285670
]
Julian Reschke commented on OAK-101:
------------------------------------
We discussed the current handling at the Hamburg Oakathon; in theory it's
desirable to have identifiers that are more stable. One way to achieve this
would be to make them relative to the closest referenceable parent node. The
downside is that the information needed for this computation may be
access-restricted, and thus may not be available to any caller.
To deal with this we talked about two different approaches:
# Expose OAK nodes in a way that they can be traversed for name resolution even
though they may not be readable
# Push down identifier computation and lookup to oak-core.
In the end we decided *not* to deal with this right now, as it's not clear that
the stability of these identifiers really is a problem. We may have to revisit
this if we get to support of multiple workspaces.
> implement identifier handling (byUUID, byIdentifier, etc)
> ---------------------------------------------------------
>
> Key: OAK-101
> URL: https://issues.apache.org/jira/browse/OAK-101
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: Julian Reschke
> Assignee: Julian Reschke
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
