Hi Chetan I would not do that even if it was possible as it will break every single application that relies on nt:resource to extend from mix:referenceable... these applications would need to change their code adding the mixin manually which may lead to follow up issues, because adding a mixin by specification requires different privileges than creating a node with just a name where the primary type (in this case nt:resource) was the applicable node type selected by the system.
I don't see anything wrong with introducing oak:Resource and let application developers decide on which variant they prefer. Kind regards Angela On 20/07/16 11:41, "Chetan Mehrotra" <chetan.mehro...@gmail.com> wrote: >On Wed, Jul 20, 2016 at 2:49 PM, Bertrand Delacretaz ><bdelacre...@apache.org> wrote: >> but the JCR spec (JSR 283 10 August 2009) only has >> >> [nt:resource] > mix:mimeType, mix:lastModified >> primaryitem jcr:data >> - jcr:data (BINARY) mandatory > >Thats interesting. Did not knew its not mandated in JCR 2.0. However >looks like for backward compatibility we need to support it. See [1] >where this was changed > >@Marcel - I did not understood JCR-2170 properly. But any chance we >can switch to newer version of nt:resource and do not modify existing >nodes and let the new definition effect/enforced only on new node. > >Chetan Mehrotra >[1] >https://issues.apache.org/jira/browse/JCR-2170?focusedCommentId=12754941&p >age=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comme >nt-12754941
