[foaf-protocols] FOAF+SSL demo: Shoutbox
henry.story at bblfish.net
Fri Apr 10 21:05:13 CEST 2009
On 10 Apr 2009, at 20:57, Toby A Inkster wrote:
> index.php says:
>> HTTP Status 500
>> org.openrdf.rio.UnsupportedRDFormatException: No parser factory
>> available for RDF format null
> This seems to be because my WebID is <http://tobyinkster.co.uk/#i>
> which has content type "text/html" (it's XHTML+RDFa) which Sesame
> doesn't currently support (it supports N3, N-Triples, RDF/XML, TriG,
> TriX and Turtle).
yes, I need to add that. Is there an XSLT or XQuery transform that I
could use, to translate
rdfa to rdf or N3?
> As a temporary workaround, it would be nice to catch this exception,
> pass the file through the W3C RDFa distiller <http://www.w3.org/
> 2007/08/pyRdfa/> and continue from there. (The heading "Alternative
> access to the Distiller" on that page has information on using it as
> a web service.)
I'll look into that, thought an xstl solution would be much preferrable.
> As a longer term fix, an RDFa parser for Sesame which can be
> committed upstream would be fantastic.
> The RDFa specification is
> remarkably clear on how to parse RDFa (and kudos to the RDF in XHTML
> Task Force for that!), so it would probably not be more than a couple
> of hours work for someone familiar with Java and the internals of
> Sesame to put together. (Unfortunately, I don't fit that description,
> otherwise I would have already done this!)
> I think that even from this early stage we should try not to tie FOAF
> +SSL too much to RDF/XML and other such formats which might seem
> esoteric to most people outside the semantic web community (and even
> to some inside the community!). If your WebID can just be some HTML
> hanging off your homepage, then it really lowers the barrier to entry.
yes, rdfa just has a little bit less tool support... That takes a bit
of time to develop.
> Toby A Inkster
> <mailto:mail at tobyinkster.co.uk>
More information about the foaf-protocols