Hi, > >Currently I am under the impression that we have no knowledge of what >*might* break, with varying opinions on the matter. Maybe we should to >find out what *does* break.
I don't think it's possible to easily find out. Customer code might expect the current behavior, and might silently break (without exception, but with wrong behavior). > >As a remedy for implementations that rely on the current referencable >nature, we could provide tooling that automatically adds the >"mix:referencable" mixin to existing nt:resource nodes and recommend >adapting the code to add the mixin as well. That might work, but in some cases it might also result in problems (if the code expects this not to be the case). Regards, Thomas
