> no strict timeframe. For you/ the folks that are developing jcr, an early > adoptor means an early tester as well. that's certainly very welcome!
> B.t.w: If we find bugs, should we submit them (and possibly > patches for it) > to this list? yes, i'd very appreciate it. cheers stefan > -----Original Message----- > From: Eelco Hillenius [mailto:[EMAIL PROTECTED] > Sent: Sonntag, 16. M�rz 2003 18:06 > To: Slide Developers Mailing List > Subject: Re: status of JCR 170? > > > Thank you for clearing things up. > > Actually we have decided to keep on using the proposal code in > Slide, as we > think the API is a better one and we want to be standards > complient as early > as possible. At this stage, our project is mainly a student's graduate > project (he'll be working fulltime on this untill june/july, > possibly helped > by me and others of our company for a day a week). This means that there's > no strict timeframe. For you/ the folks that are developing jcr, an early > adoptor means an early tester as well. > > Thank you (and Day Software) for the effort, and we'll be looking > forward to > further additions to the ri! > > Cheers, > > Eelco Hillenius > > B.t.w: If we find bugs, should we submit them (and possibly > patches for it) > to this list? > > > ----- Original Message ----- > From: "Stefan Guggisberg" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Sunday, March 16, 2003 3:42 PM > Subject: RE: status of JCR 170? > > > > > Could anyone (Stefan Guggisberg?) tell me more about the status of JCR > > 170? > > sorry for the late reply, i just got on board ;-) > > > > > The official JCP site and http://jcrep-jsr.day.com/playground/en.html > give > > > different time frames, where according to the official JCP > site the spec > > > should be allmost final. > > always refer to http://jcr.day.com for the most up-to-date information, > > the official jcp site doesn't seem to get updated very often. > > > > > A few specific questions: > > > - what is the current time frame for JSR 170? > > see http://jcrep-jsr.day.com/playground/en/schedule.html for details > > (and allow for further minor delays for the community draft). > > > > > - can we get the standard document somewhere (it is referenced several > > times > > > in the proposal code) > > all expert group members are under nda (i.e. the current spec can't be > > handed out). > > the jcr specification document will first be made available to a broader > > audience > > during the community draft. > > > > > - what is the planned time frame for the slide implementation? > > there's no time-frame yet as jsr 170 is still only a proposal within the > > slide project. > > all i can say is that i'll be actively working on the current jsr 170 > > related > > code. > > > > > - will this implementation support (part of) level 2 functionality?* > > > * in particular for our case we are interested in access > management and > > > search (query) functionality > > as it is planned that slide will become the official jsr 170 reference > > implementation > > (in some way or another), the goal is to implement as much level 2 > > functionality > > asw faithful as possible. access control and search will > certainly be part > > of it. > > > > regards > > stefan > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
