Using XSLT with RDF/XML is a pretty common solution for this. Otherwise, you might want to look at Pubby:
http://wifo5-03.informatik.uni-mannheim.de/pubby/ which seems no longer to be under development and has some limitations, but could be useful to you. It translates requests on URIs into SPARQL Describe queries against a backend (e.g. Jena Fuseki) and provides HTML representations. For more sophisticated HTML work, there are templating systems (e.g. Apache Marmotta LDPath Template [1]). Or, if you are less interested in providing a sophisticated query endpoint than in just publishing triples en masse, you might be better served by Linked Data Fragments [2] and the machinery associated therewith [3]. [1] https://marmotta.apache.org/ldpath/template.html [2] http://linkeddatafragments.org/ [3] https://github.com/LinkedDataFragments/Server.java --- A. Soroka The University of Virginia Library > On Apr 15, 2016, at 12:59 PM, Andy Seaborne <a...@apache.org> wrote: > > Fuseki itself does not provide HTML. It's a data server - appearance is the > responsibility of the client. > > What sparql.org does for HTML is add a stylesheet to > application/sparql-results+xml. > > request G > > GET .... &stylesheet=%2Fxml-to-html.xsl > > --> > > <?xml version="1.0"?> > <?xml-stylesheet type="text/xsl" href="/xml-to-html.xsl"?> > <sparql xmlns="http://www.w3.org/2005/sparql-results#";> > .... > > > > Andy > > On 15/04/16 16:42, Frans Knibbe wrote: >> 2016-04-15 17:02 GMT+02:00 A. Soroka <aj...@virginia.edu>: >> >>> It's not totally clear to me what you could mean by "a way to get HTML >>> format working". Do you mean some kind of RDFa templating? There's not a >>> normal way to translate triples into HTML. >>> >>> If you could say a little more about your use case for HTML, someone might >>> be able to recommend a tool or technique to use. Otherwise, Fuseki will >>> return the serializations for triples that you name below (and I believe >>> there may be some functionality for quads, but others would know more than >>> I). >>> >> >> The general use case would be displaying data in a human friendly way. For >> example when a data URI is entered in the address bar of a web browser. Or >> when a data URI appears in on a web page or in a web application and a user >> clicks on it. >> >> I do not have an idea of how the data should be presented on an HTML page. >> I guess it is like the SPARQL DESCRIBE response - there is some lierty in >> how it can be implemented. It could be table with subject, predicate and >> object columns for example. Or something like the DBPedia HTML output (e.g. >> http://dbpedia.org/page/Fuseki). Something that allows some kind of >> customization or templating would be great. >> >> I hope this helps to explain what I am looking for. And I hope it is >> somehow possible to have some form of HTML output. >> >> Regards, >> Frans >> >> >>> >>> --- >>> A. Soroka >>> The University of Virginia Library >>> >>>> On Apr 15, 2016, at 10:18 AM, Frans Knibbe <frans.kni...@geodan.nl> >>> wrote: >>>> >>>> Hello, >>>> >>>> I have just been testing content negotiation with my new Fuseki server >>>> (version 1.3.1). I tried to get data in Turtle, RDF/XML, Ntriples and >>>> JSON-LD formats and that seemed to work well. However, if I request data >>> to >>>> be formatted in HTML ("Accept: text/html"), I receive my sample data in >>>> RDF/XML format. >>>> >>>> Is there an overview of content types that Fuseki supports somewhere? I >>>> searched but have not been able to find it. >>>> >>>> And is there a way to get HTML format working? >>>> >>>> Greetings, and thanks in advance, >>>> >>>> Frans >>> >>> >> >
