hi geir, thank you for your comments. i share your view.
> > Well, it turned out that not only it didn't get traction (which is not > > surprising, given the fact that the specification is not yet publicly > > available), but it resorted in major abuse of that code by some other > > software products that looked at that code as it represented the > > *real* JCR API and went around saying that they were compliant with > > the JCR API. > They legally can't. You can't be compatible w/ an API w/o passing the > TCK. There is no TCK yet. What are the licensing terms for the JSR? true. and of course the tck is not available yet, since the spec is not finished. i think this situation is due to the urgent need for something like jsr-170 that people started to built _applications_ on top of the unfinished ri. and of course the applications cannot be jsr-170 compliant since there will be no tck for applications but just for repositories (i think this is the same problem that people had with so-called "j2ee-compliant-applications", which meant that applications ran in a j2ee appserver, but obivously there is only a tck for the appservers). additionally i think nobody actually claims to be "jsr-170 compliant" but things like "adhere to jsr-170", etc... i think the whole situation came about, because of what has been called "marketing abuse", but i am not sure if there is a legal situation at hand. > How are the spec materials licensed? the licensing terms were presented to the pmo, ec and eg with the submission of the community review draft. they have been written and submitted by roy and are as far as i understand in essence an adaption of the apache 2.0 license. if you have any further questions, please just let me know. regards, david --------------------------------< [EMAIL PROTECTED] >--- This message is a private communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. The sender does not assume any liability for timely, trouble free, complete, virus free, secure, error free or uninterrupted arrival of this e-mail. For verification please request a hard copy version. mailto:[EMAIL PROTECTED] http://www.day.com David Nuescheler Chief Technology Officer Day Interactive Management AG Barfuesserplatz 6 / Postfach 4001 Basel Switzerland T 41 61 226 98 98 F 41 61 226 98 97 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
