OK, sorry for the confusion.
What I *should* have said is that we shouldn't discuss the definition of setValue/SetProperty(null), but Section 3.7.3 ("No Null Values"), which is part of Section 3, "The Repository Model" (sic).
Best regards, Julian Mark Waschkowski wrote:
"If you want to discuss a data model change, please be clear about it, and stop discussing the API. What the API does depends on the data model, not the other way around." I think we've had this discussion in another thread already... Anyway, I'm discussing the API. JCR is an API, not an implementation. Please see: http://en.wikipedia.org/wiki/JSR-170 "*Content Repository API for Java* (*JCR*) is a specification for a Java platform <http://en.wikipedia.org/wiki/Java_platform> API<http://en.wikipedia.org/wiki/Application_Programming_Interface>for accessing content repositories<http://en.wikipedia.org/w/index.php?title=Content_repository&action=edit>in a uniform manner. " I don't care that there are 800+ implementations out there already for content repository or the data models that each of the those implementations uses. I'm sure that consideration was made for the implementations that existed prior to the spec, but I'm also sure that not every one of those implementations could easily accommodate conforming to the spec, and thats why different levels were introduced. In any case, its the mandated behavior of the new spec that I'm trying my best to provide feedback on, which I'm actually hoping may improve it. Regards, Mark
