two questions about rdfQuery user experiences
xi.bai
Two questions are still bothering me currently. I want to list them
here and hope some of you can share your opinions.
1. If the snippet with rdfa is not in the DOM tree, rdfQuery will not
parse it because
rdfQuery is built on top of jQuery and jQuery can not select this kind
of snippet. One
solution is to add the snippet with rdfa to an invisible node inside
the HTML document.
After being parsed, this snippet should be deleted. But there is still
a risk that the
snippet will cause problems when the browser renders the whole HTML
document. My
question is "will rdfQuery provide a way of parsing the nodes in the
memory (generated
on the fly) but not in the DOM tree?".
2. The parsing time for some page is slow maybe this is because my
laptop is very slow.
I know you guys are still improving the efficiency of rdfQuery. My
question is if a page
contains a large number of triples (well, you can say this page is
crappy and unuseful
but it is possible), the parsing will be slow and my browser is like
dead for seconds.
This is not friendly to users. My question is "is there any ways of
hiding this kind
of lag?". For example, people use loading indicator in ajax programmes
and any
possibilities for similar client side solutions? I know this is not
about rdfQuery
itself but it may happen when people use rdfQuery.
Michael Hausenblas
> 2. The parsing time for some page is slow maybe this is because my
> laptop is very slow.
> I know you guys are still improving the efficiency of rdfQuery. My
> question is if a page
> contains a large number of triples (well, you can say this page is
> crappy and unuseful
> but it is possible), the parsing will be slow and my browser is like
> dead for seconds.
> This is not friendly to users. My question is "is there any ways of
> hiding this kind
> of lag?". For example, people use loading indicator in ajax programmes
> and any
> possibilities for similar client side solutions? I know this is not
> about rdfQuery
> itself but it may happen when people use rdfQuery.
tried to come up with a sort of explanation in [1]. I think we should really
invest more time into this, but as you rightly say, little if not nothing to
do with rdfquery per se ...
Cheers,
Michael
[1] http://ld2sd.deri.org/lod-ng-tutorial/#checklist-usability
--
Dr. Michael Hausenblas
LiDRC - Linked Data Research Centre
DERI - Digital Enterprise Research Institute
NUIG - National University of Ireland, Galway
Ireland, Europe
Tel. +353 91 495730
http://linkeddata.deri.ie/
http://sw-app.org/about.html
Norman Heino
Am 15.07.2009 um 11:49 schrieb xi.bai:
>
> Congratulations to the success of the rdfQuery dazzle last weekend!
> Two questions are still bothering me currently. I want to list them
> here and hope some of you can share your opinions.
>
> 1. If the snippet with rdfa is not in the DOM tree, rdfQuery will not
> parse it because
> rdfQuery is built on top of jQuery and jQuery can not select this kind
> of snippet. One
> solution is to add the snippet with rdfa to an invisible node inside
> the HTML document.
> After being parsed, this snippet should be deleted. But there is still
> a risk that the
> snippet will cause problems when the browser renders the whole HTML
> document. My
> question is "will rdfQuery provide a way of parsing the nodes in the
> memory (generated
> on the fly) but not in the DOM tree?".
Why would you want to create RDFa nodes in memory? rdfQuery can parse
triples from N3, RDF/XML or RDF/JSON [1] if you want to feed it
triples not in the page.
> 2. The parsing time for some page is slow maybe this is because my
> laptop is very slow.
> I know you guys are still improving the efficiency of rdfQuery. My
> question is if a page
> contains a large number of triples (well, you can say this page is
> crappy and unuseful
> but it is possible), the parsing will be slow and my browser is like
> dead for seconds.
> This is not friendly to users. My question is "is there any ways of
> hiding this kind
> of lag?". For example, people use loading indicator in ajax programmes
> and any
> possibilities for similar client side solutions? I know this is not
> about rdfQuery
> itself but it may happen when people use rdfQuery.
I use Ben Adida's RDFa parser [2] and feed the resulting triples to
rdfQuery. That is much faster for the time being and I can add events
to the elements. :)
Regards,
Norman
[1] http://n2.talis.com/wiki/RDF_JSON_Specification
[2] http://www.w3.org/2006/07/SWD/RDFa/impl/js/rdfa.js
BAI XI
Thank you for the link you provided. Yes, the "seeAlso" is a possible trade-off for this problem. The page with rdfa can point to another RDF/XML document or even another XHTML+ RDFa page if necessary. At least we can use ajax + server-side parser to asynchronize the end users' activities. For the client-side parser case, i hope javascript geeks could share their trade-off solutions.
Best,
Xi
BAI XI
>Why would you want to create RDFa nodes in memory? rdfQuery can parse
>triples from N3, RDF/XML or RDF/JSON [1] if you want to feed it
>triples not in the page.
Best,
Xi