Hi Nina, Egon, All,
   I performed some measurements to tell how Jena performs when
different representations are requested from the remote service. Till
now we worked exclusively with RDF/XML so we tried the alternatives of
TURTLE and N3-TRIPLES. The result is that RDF/XML is downloaded and
parsed faster than TURTLE and N3-TRIPLES (take a look at the attached
file). I'll do the same with JSON as well.

@Nina: I'll try to create a Model (com.hp.hpl.jena.rdf.model.Model)
using different methods from the ModelFactory outside ToxOtis and send
you the results. If there's a benefit from using some other Model
implementation, we'll rearrange a bit the source code in ToxOtis to
enhance the performance. What's more, for the time, if one needs to
serialize an RDF graph has to invoke the method
"write(java.io.OutputStream):void" but we study AMBIT's implementation
with StAX and will provide an alternative method. For the time I'm a bit
confused but I'll take a look at the documentation first...

Interlude: Manualism
Manualism (syn. Documentationism) is a technological movement that began
in Java (the country) by programmers in the early 90s. It's purpose is
the construction of interfaces and methods, so complex that the ONLY way
to make something work is to read the Users' Manual. A prime example of
a manualist masterpiece is Jena. [To my surprise, the term manualism is
found in wikipedia but with a different meaning:
http://en.wikipedia.org/wiki/Manualism_%28hand_music%29 ]

Best Regards,
Pantelis



On Wed, 2010-10-06 at 20:00 +0300, Nina Jeliazkova wrote:

> On Wed, Oct 6, 2010 at 7:58 PM, Nina Jeliazkova
> <jeliazkova.nina at gmail.com>wrote:
> 
> > Egon,
> >
> > Thanks for the pointers.
> >
> >
> > On Wed, Oct 6, 2010 at 4:29 PM, Egon Willighagen <
> > egon.willighagen at gmail.com> wrote:
> >
> >> Nina,
> >>
> >> On Wed, Oct 6, 2010 at 3:24 PM, Nina Jeliazkova
> >> <jeliazkova.nina at gmail.com> wrote:
> >> > Has anybody tried/ can recommend how to serialize/read RDF objects
> >> to/from
> >> > JSON ?  Would be nice to compare with RDF/XML.
> >>
> >> I have not had time to test it, but here are some options:
> >>
> >>
> >> http://www.semanticoverflow.com/questions/1506/how-can-i-use-jena-to-serialize-rdf-in-the-json-syntax
> >>
> >
> >
> > @All
> >
> > Using   http://code.google.com/p/linked-data-api for RDF JSON
> > serialization  is quite straightforward and the dataset resource output
> > looks like .
> >
> 
> Sorry, json output should be here, but omitted - hope curl commands are
> sufficient.
> 
> Nina
> 
> 
> >
> > Datasets are now available in JSON as well, via Accept header
> > application/json.
> >
> > curl -H "Accept:application/json" '
> > http://ambit.uni-plovdiv.bg:8080/ambit2/dataset/9?page=0&pagesize=1000' 1>
> > 9.json
> >
> > curl -H "Accept:application/json" '
> > http://apps.ideaconsult.net:8080/ambit2/dataset/9?page=0&pagesize=1000' 1>
> > 9.json
> >
> > It seems there is not much difference neither in file size, nor in response
> > time, but I havent' done enough measurements to be sure.
> >
> > Also, I am not sure the right mime type should be "application/json" - how
> > does one tell between different json contents?
> >
> > Best regards,
> > Nina
> >
> >
> >> Egon
> >>
> >> --
> >> Dr E.L. Willighagen
> >> Homepage: http://egonw.github.com/
> >> LinkedIn: http://se.linkedin.com/in/egonw
> >> Blog: http://chem-bla-ics.blogspot.com/
> >> PubList: http://www.citeulike.org/user/egonw/tag/papers
> >> _______________________________________________
> >> Development mailing list
> >> Development at opentox.org
> >> http://www.opentox.org/mailman/listinfo/development
> >>
> >
> >
> >
> >
> _______________________________________________
> Development mailing list
> Development at opentox.org
> http://www.opentox.org/mailman/listinfo/development
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: OptimizingPerformance.odt
Type: application/vnd.oasis.opendocument.text
Size: 406928 bytes
Desc: not available
URL: <http://lists.opentox.org/pipermail/development/attachments/20101006/d40f0114/attachment.odt>