for those of you who'd like to know more about jcr and jackrabbit, here's a good article: <http://www.artima.com/lejava/articles/contentrepository.html>
<originally posted to ietf-caldav> any open source CalDAV client projects going on out there? i'm looking for a simple command line tool to help with developing and testing our server. unfortunately neither curl nor lwp-request seem to support arbitrary HTTP methods, so they won't be immediately useful. the perldav project (<http://www.webdav.org/perldav/>) doesn't seem to have been active in years, but it looks to have a good base to build on. i've contacted the author but haven't heard back yet. if nobody has anything more substantial, i'll probably hack together something based on perldav. if anyone's interested in helping out, let me know. thanks!
are any of you familiar with hCalendar? <http://developers.technorati.com/wiki/hCalendar> thoughts on how it might be useful for cosmo or scooby?
Yes, I've met Tantek too and talked to him about this scheme. I was thinking someday we'd probably get around to using it when we display an event or a list of events in Scooby, so that someday if somebody writes an hCalendar-based tool they can scrape the data right out of the page. We'd still obviously need to use iCalendar for export and CalDAV support and invitations (maybe a couple other places too). lisa On Jun 8, 2005, at 5:39 PM, Brian Moseley wrote: > are any of you familiar with hCalendar? > > <http://developers.technorati.com/wiki/hCalendar> > > thoughts on how it might be useful for cosmo or scooby? > _______________________________________________ > Cosmo mailing list > Cosmo <at> osafoundation.org > http://lists.osafoundation.org/mailman/listinfo/cosmo >
Lisa Dusseault wrote: > Yes, I've met Tantek too and talked to him about this scheme. I was > thinking someday we'd probably get around to using it when we display an > event or a list of events in Scooby, so that someday if somebody writes > an hCalendar-based tool they can scrape the data right out of the page. > We'd still obviously need to use iCalendar for export and CalDAV support > and invitations (maybe a couple other places too). seems like we could do multipart/alternative invitations with hcalendar and icalendar parts. hopefully that would satisfy all the different little groups of geeks out there :)
I don't think that's worthwhile although I may be proven wrong if email clients and calendar applications come to accept hCalendar and *not* iCalendar. Since iCalendar is more expressive (Tantek reduced the scope for decent reasons) and since it's the only accepted iMIP format, it's the only thing you have to send. Where you'll see hCalendar client code -- at least at first -- is in little browser plug-ins or extensions that parse a Web page and can let you know "there's an event described in this Web page" and let you send it to your calendar application. One of the broken things about the iCalendar spec series, RFC2445-2447, is that you can't send multipart/alternative in iMIP messages. The standard is written so you can only legally send text/calendar MIME types. Ever. No upgrade mechanism. No description of what a client is supposed to do if it receives multipart/alternative (might be ambiguous, after all). Lisa On Jun 8, 2005, at 5:56 PM, Brian Moseley wrote: > Lisa Dusseault wrote: >> Yes, I've met Tantek too and talked to him about this scheme. I was >> thinking someday we'd probably get around to using it when we display >> an event or a list of events in Scooby, so that someday if somebody >> writes an hCalendar-based tool they can scrape the data right out of >> the page. We'd still obviously need to use iCalendar for export and >> CalDAV support and invitations (maybe a couple other places too). > > seems like we could do multipart/alternative invitations with(Continue reading)
Lisa Dusseault wrote: > I don't think that's worthwhile although I may be proven wrong if email > clients and calendar applications come to accept hCalendar and *not* > iCalendar. Since iCalendar is more expressive (Tantek reduced the scope > for decent reasons) and since it's the only accepted iMIP format, it's > the only thing you have to send. Where you'll see hCalendar client code > -- at least at first -- is in little browser plug-ins or extensions that > parse a Web page and can let you know "there's an event described in > this Web page" and let you send it to your calendar application. i think there's a firefox extension/greasemonkey script/whatever that does that now. > One of the broken things about the iCalendar spec series, RFC2445-2447, > is that you can't send multipart/alternative in iMIP messages. The > standard is written so you can only legally send text/calendar MIME > types. Ever. No upgrade mechanism. No description of what a client is > supposed to do if it receives multipart/alternative (might be ambiguous, > after all). yeah, that completely ignores common sense. any sane mail client would prefer to display a text/plain or text/html part and give you a control to do something with the text/calendar part (like put it on a calendar server).
Hello, The build is currently trying to pull JCR 1.0 and failing. Should we build this ourselves? PS. I was delayed a little this weekend but I'm still on MKTICKET. Hoping to have something by the end of the week. Regards, Kervni
Hello, I take it that this expired draft... http://www.watersprings.org/pub/id/draft-ito-dav-ticket-00.txt is the only documentation on MKTICKET that we will work with? Thanks, Kervin
If we have multiple interoperable implementations (Cosmo, your work, Xythos server and Xythos client) then it's pretty worthwhile to reissue the draft and bring it to RFC status (possibly Experimental, possibly Proposed Standard). I can help with that or do it if nobody else wants to. Lisa On Jun 13, 2005, at 9:27 AM, Kervin L. Pierre wrote: > Hello, > > I take it that this expired draft... > http://www.watersprings.org/pub/id/draft-ito-dav-ticket-00.txt > is the only documentation on MKTICKET > that we will work with? > > Thanks, > Kervin > _______________________________________________ > Cosmo mailing list > Cosmo <at> osafoundation.org > http://lists.osafoundation.org/mailman/listinfo/cosmo >
RSS Feed1 | |
|---|---|
1 | |
1 | |
1 | |
1 | |
1 | |
3 | |
1 | |
3 | |
2 | |
4 | |
8 | |
2 | |
1 | |
4 | |
8 | |
2 | |
4 | |
7 | |
41 | |
1 | |
25 | |
45 | |
31 | |
25 | |
39 | |
62 | |
76 | |
55 | |
46 | |
57 | |
68 | |
114 | |
196 | |
220 | |
285 | |
200 | |
244 | |
301 | |
218 | |
272 | |
189 | |
326 | |
322 | |
301 | |
225 | |
315 | |
217 | |
215 | |
134 | |
289 | |
159 | |
103 | |
74 | |
67 | |
166 | |
102 | |
71 | |
57 | |
29 | |
35 | |
21 | |
12 | |
18 | |
34 | |
25 |
