[ https://issues.apache.org/jira/browse/OAK-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810184#comment-13810184 ]
Stefan Guggisberg commented on OAK-1126: ---------------------------------------- my main concern regarding SNNP is that it breaks the intuitive 1:1 JSON representation of repository content. artificial intermediary objects like e.g. ":children" are IMO non-intuitive and lead to awkward client code on the JSON consumer side. as discussed on the list: http://markmail.org/message/procpdcyctcibxdt > Same node and property name support > ----------------------------------- > > Key: OAK-1126 > URL: https://issues.apache.org/jira/browse/OAK-1126 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: core, doc, jcr > Reporter: Tobias Bocanegra > Attachments: OAK-1126.patch > > > The initial MK abstraction mandated that the nodes and properties share the > same namespace > (http://wiki.apache.org/jackrabbit/RepositoryMicroKernel#Data%20Model). This > is a regression from Jackrabbit 2.x, which supports same name nodes and > properties (SNNP). > OTOH, the NodeStores can easily support SNNP and with proper escaping, the > MKs can also support it. > We should try to keep the support for SNNP in order to keep backward > compatibility for existing content, and also keep the support for importing > XML documents with same attribute and element names. -- This message was sent by Atlassian JIRA (v6.1#6144)