On May 8, 2009, at 07:27 AM, Kingsley Idehen wrote:
Peter Ansell wrote:
One major one is the introduction of content negotiation, which has
been tested for N3 (using text/rdf+n3) and RDF/XML (using
application/rdf+xml). It was made possible this quickly after the
last release by the use of the content negotiation code from Pubby,
the driver behind the DBpedia web interface and URI resolution
mechanism. It is also possible to explicitly get to the N3 format
currently by prefixing the URL with /n3/ See [2] for an example.
The ability to explicitly get to the RDF/XML will be added in future.
Great move re. content negotiation improvements!
Important correction:
Pubby *was* used to deploy Linked Data in front of the Virtuoso SPARQL
endpoint for DBpedia during the early stages of the project.
Virtuoso's in-built Linked Data deployment functionality [1] is how
DBpedia's Linked Data has been deployed for a quite some time now.
The DBpedia architecture page may help clarify this, too. This page was
updated in August, but the shift from Pubby to Virtuoso as front-end had
happened some time previous.
<http://wiki.dbpedia.org/Architecture>
Be seeing you,
Ted
Just want to keep the facts crystal clear :-)
[SNIP]
Links:
1.
http://virtuoso.openlinksw.com/Whitepapers/html/vdld_html/VirtDeployingLinkedDataGuide.html
--
A: Yes. http://www.guckes.net/faq/attribution.html
| Q: Are you sure?
| | A: Because it reverses the logical flow of conversation.
| | | Q: Why is top posting frowned upon?
Ted Thibodeau, Jr. // voice +1-781-273-0900 x32
Evangelism & Support // mailto:[email protected]
OpenLink Software, Inc. // http://www.openlinksw.com/
http://www.openlinksw.com/weblogs/uda/
OpenLink Blogs http://www.openlinksw.com/weblogs/virtuoso/
http://www.openlinksw.com/blog/~kidehen/
Universal Data Access and Virtual Database Technology Providers
