From: Florent J. <flo...@un...> - 2008-04-07 09:02:24
|
Hi, I don't want to interfere as I'm not an Aperture developer but could the invalid Unicode problem from this thread http://sourceforge.net/mailarchive/message.php?msg_name=711A6E44E5028648A8D1 5B1DC32E58E0CF1784%40scomp0038.wurnet.nl could be check also? I think having clean and valid xml output is also important for aperture... For the RDF2go update you're talking, I just want to let you know that I'm using aperture with sesame2.0.1 and rdf2go 4.5.x without any problems. But it might be more complicated for nepomuk... at least simple case works. Regards, Florent > -----Ursprüngliche Nachricht----- > Von: ape...@li... [mailto:aperture- > dev...@li...] Im Auftrag von Leo Sauermann > Gesendet: Donnerstag, 3. April 2008 18:39 > An: Antoni Myłka > Cc: aperture-devel > Betreff: Re: [Aperture-devel] Next Aperture release > > It was Antoni Myłka who said at the right time 03.04.2008 18:07 the > following words: > > (LEO: Please read the bullet number 6 below and answer) > > > > I think we can think about a new Aperture release. > > > > We got the MP3FileExtractor, the JPGExtractor, the VcardSubCrawler > and > > the MboxCrawler. I'd suggest a following timeline: > > > > * now - decide what do do in next three weeks > > * 28.04 - feature freeze > > * 14.05 - release > > > > Almost four weeks for new features and two weeks for testing and > release > > preparation, there is quite a lot to do. Please voice your opinions > now. > > > > In more detail: > > > > 1. Finish the issues with imap crawler. It's being worked on now, so > > it's not a bad idea to sneak in some older feature requests. > > - crawler/accessor conflict > > - new incremental crawling strategy (SF: 1531657) > > - (optional) lazy connection handling (SF: 1480423) > > - (optional) implement a MimeSubCrawler using some of the > > AbstractJavaMailCrawler code and thus solve the (SF: 1779556) > issue > > > ok > > 2. Implement the new AccessData interface > > - remove the deprecatedUrls set from the CrawlerBase (could take a > > while, probably some minor interface changes will be necessary, > > hopefully only on the side of the crawlers, the users won't > notice). > > - solve the the data object hierarchy issue that arose when we > > started thinking about SubCrawlers > > > ok, but this I need to check again, I lost context and we would need to > write down all the nitwitty arguments we had before we can make a good > architecture decision > > 3. Migrate the website crawlers to NAO and test them (simple, > shouldn't > > take more than a day). Remove the TAGGING 'ontology'. > > > ok > > 4. Clean up the dependencies, > > - state clearly what is an official release jar and what is a > hacked > > version. It is not clear at the moment. We can use jars prepared > > by Apache Felix guys, those that already contain osgi manifests. > > > well, that should be easier.... > > - the libraries from sun impose certain constraints on > redistribution > > i raised an issue with JAI. the redistribution conditions of JAI > are > > inacceptable. Thilo Götz from IBM/UIMA wrote that they don't do > it. > > We shouldn't either, some temporary solution is necessary until > the > > apache folks remove the JAI dependency from PDFBOX. > > > make a flag in the ant-script "weasely whimpy chicken release without > JAI", > in PDFExtractor, make a check and throw the-hell-of-a-exception > if JAI miasses (class.forname"...") and say prominently in log, > system.err > that clients have to download JAI and add it, also giving the download > url there > (ok? if this is ok, make a ticket for this and we do it) > > - for the hacked versions, include the patches in the distribution. > > > hm.... ok > > > 5. Clean up the wiki and include a snapshot in the distribution. > There > > is the "export to HTML" feature. We should use it. We could place the > > exported snapshot on the website and state that the wiki corresponds > to > > the current trunk - a constant work in progress - whereas the actual > > release documentation is on the website. > > > NO, > people should always use the wiki, because if they read the doc > offline, > we lose the chance that they MAY edit and improve the documentation > when > they find errors > > 6. We still use sesame 2.0 beta 6. Updating it would probably require > an > > update in the RDF2Go driver and in Nepomuk. This might be difficult. > > Leo? What do you think? > > > we need to update, that should be on the list > I talked with Max, he said he will test RDF2Go througoughly to check if > all is right for sesame2 > > best > Leo > > All kinds of comments welcome. > > > > Antoni Mylka > > ant...@gm... > > > > --------------------------------------------------------------------- > ---- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/market > place > > _______________________________________________ > > Aperture-devel mailing list > > Ape...@li... > > https://lists.sourceforge.net/lists/listinfo/aperture-devel > > > > > > > -- > ____________________________________________________ > DI Leo Sauermann http://www.dfki.de/~sauermann > > Deutsches Forschungszentrum fuer > Kuenstliche Intelligenz DFKI GmbH > Trippstadter Strasse 122 > P.O. Box 2080 Fon: +49 631 20575-116 > D-67663 Kaiserslautern Fax: +49 631 20575-102 > Germany Mail: leo...@df... > > Geschaeftsfuehrung: > Prof.Dr.Dr.h.c.mult. Wolfgang Wahlster (Vorsitzender) > Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: > Prof. Dr. h.c. Hans A. Aukes > Amtsgericht Kaiserslautern, HRB 2313 > ____________________________________________________ > > > ----------------------------------------------------------------------- > -- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/market > place > _______________________________________________ > Aperture-devel mailing list > Ape...@li... > https://lists.sourceforge.net/lists/listinfo/aperture-devel |