2014-04-08 13:07 GMT+02:00 Leandro Doctors <[email protected]>: > 2014-04-07 22:57 GMT+02:00 Alexandru Todor <[email protected]>: >> I think it's a good approach and it's really perfect for a warmup task. You >> will be able to get to know the different components and help us get rid of >> the php code. > >> Although if you decided to use scala, please refactor the code >> in such a way that you can make it an Extractor and place it in /mappings.
As suggested by Alexandru Todor, I have just checked the package org.dbpedia.extraction.mappings. There, I found a partial implementation of the PHP script (precisely, the link extractor). If I continue with my original plan (seemed OK by Dimitris (@jimkont) and Franco (@marfox)), and I first implement a Scala "standalone" version of flickrwrapper, based on the logic of the PHP code, I will have to implement lots of ad-hoc functions for IO and networking purposes (which would be discarded immediately after I finish it), but the flickrwrappr logic would not change so much. If I follow Alexandru's suggestion, I will have to go through all the package and understand its logic (which would take more time). However by doing this, I would yield a "better" result. I'm not so sure which approach to follow. What would you suggest? Leandro ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Dbpedia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-developers
