> Well, if by jcr:uuid you mean a canonical, unique identifier for the > resource, I've got that as an 'oid' (object id), created by a 10ms > delayed, non-repeating (timestamped) ID factory. The system identifier
Check out the JCR spec on this one. It's a globally unique ID of a Node. > If you're talking about the prototype we've discussed, I mean more > information about the ability to continue to use non-JSR 170 backends, > as we may need to. We may have a very strong need to if we end up > backing the system into a CMS (which I wouldn't particularly like but > it might not work with our archiving system otherwise, dunno yet). I think the chances of using a non-JCR backend is essentially zero, because it would mean duplicating the entire metadata layer and essentially redesigning JSR-170. But this is a very long topic and I don't have more time... /Janne
