My point is completely distinct from RDF. My point is that there is a lot of Javascript + CSS out there that make many sites way more usable (for certainly classes of users, including me!), but I wish more of these interactive features were available without having to use an idiosyncratic implementation of them in a full fledged, but inconsistently implemented, programming language.

Javascript programmers have done amazing things (just see OAT), but I like web pages to be safer than they are and still usable. Some things are easy to roll in (toggling visibility of text…that should be built in; footnotes; lots of widgets). They would be easier to use as well (though the best Javascript libraries do a pretty good job of making widgets plug and go).

Finally, none of the Fresnel implementations have one of the most charming features of Exhibit: working in standalone pages. It’s obviously not impossible to make one up, but doing it straight from RDF would probably be pretty painful. Something Fresnelish tuned for Exhibit databases would certainly be easier to get going, I’d imagine.

My point is completely distinct from RDF. My point is that there is a lot of Javascript + CSS out there that make many sites way more usable (for certainly classes of users, including me!), but I wish more of these interactive features were available without having to use an idiosyncratic implementation of them in a full fledged, but inconsistently implemented, programming language.

Javascript programmers have done amazing things (just see OAT), but I like web pages to be safer than they are and still usable. Some things are easy to roll in (toggling visibility of text…that should be built in; footnotes; lots of widgets). They would be easier to use as well (though the best Javascript libraries do a pretty good job of making widgets plug and go).

Finally, none of the Fresnel implementations have one of the most charming features of Exhibit: working in standalone pages. It’s obviously not impossible to make one up, but doing it straight from RDF would probably be pretty painful. Something Fresnelish tuned for Exhibit databases would certainly be easier to get going, I’d imagine.

My point is completely distinct from RDF. My point is that there is a lot of Javascript + CSS out there that make many sites way more usable (for certainly classes of users, including me!), but I wish more of these interactive features were available without having to use an idiosyncratic implementation of them in a full fledged, but inconsistently implemented, programming language.

Javascript programmers have done amazing things (just see OAT), but I like web pages to be safer than they are and still usable. Some things are easy to roll in (toggling visibility of text…that should be built in; footnotes; lots of widgets). They would be easier to use as well (though the best Javascript libraries do a pretty good job of making widgets plug and go).

Finally, none of the Fresnel implementations have one of the most charming features of Exhibit: working in standalone pages. It’s obviously not impossible to make one up, but doing it straight from RDF would probably be pretty painful. Something Fresnelish tuned for Exhibit databases would certainly be easier to get going, I’d imagine.

I might try the experiment of extracting stuff via this RDFization. Though, the XSLT is pretty trivial and has done the job.

I might try the experiment of extracting stuff via this RDFization. Though, the XSLT is pretty trivial and has done the job.

I might try the experiment of extracting stuff via this RDFization. Though, the XSLT is pretty trivial and has done the job.