On Fri, May 1, 2009 at 09:23, Stian Soiland-Reyes <[email protected]> wrote: > mydata-2009-05-01.t2data (zip-format) > content.rdf (the research object manifest) > t2references.rdf (list structures, error documents, references, > references to data/.* )
I was just thinking that we probably want to have the lists themselves also be separate files, they could potentially be quiet large. Say a list of 100.000 items, each item requires at least 40 bytes (assuming a readable hex-filename) to reference a data value, that's 40 MB just there - perhaps not too bad, but do you want to force your RDF parser to work with all of these? It comes down to a trade off between scalability and how difficult it would be to use.. part of the job of such a format would be interoperability, for users of the Taverna engine, integration with other systems, archiving and provenance, etc. .. but yes - we have thought of something 'better' than Baclava - but I'm sure if you compare the idea I just described with the Baclava format, then doing some base64 decoding isn't really much work compared to parsing this suggestion.. ;-) Stian, who's supposed to be on holiday but still feels an urge for coffee and emails.. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ taverna-hackers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/taverna-hackers Developers Guide: http://www.mygrid.org.uk/usermanual1.7/dev_guide.html FAQ: http://www.mygrid.org.uk/wiki/Mygrid/TavernaFaq
