Documentation seems to be outdated

Linked Data
1

Hi Guys!

It seems that the documentation on this page is quite outdated:

http://vos.openlinksw.com/owiki/wiki/VOS/VirtLDP

A lot of those examples don’t work anymore (e.g. calling an LDP nonRDF resource with Accept: text/turtle headers now fails (as it should!) but the example shows it returning metadata about the non-RDF file) or the output doesn’t math the outputs that come from your LDP server (e.g. in the example, you do a POST, but the return message is lacking a Location: header… which the real LDP server does return, as it should!)

Also, the examples, and the code, are using a Link relation that, as far as I am aware, never got into the final spec. Your examples, and Virtuoso 7, use Link rel=meta. I believe that the relation that eventually became part of the standard is Link rel=describedBy

Some sprucing-up of those outdated docs would be very welcome!

Cheers!

Mark

2

@markwilkinson: We shall schedule to review and update the document accordingly …

3

I’m working on the documentation for Virtuoso / openlink Docs Generally, whilst i am doing so in a manner that is focused upon ‘local host’ implementations where virtuoso is sought to be part of an ‘AI Stack’ that incorporates ‘social semantic web’ (RWW/SOLID/Cross-Cloud) supports.

Link to WIP: GitHub - WebizenAI/OpenlinkDocs: This is a project to create modern openlink virtuoso documentation & related tools

I’m using obsidian presently, whilst the end-goal includes a desire to format the content in a manner that is best suited for incorporating into an LLM agent. If there are any recommendations about how best to achieve this outcome, input is welcomed.

Question:

I wondered if there’s a PDF or mark-down version of the docs?

Going through the documentation page by page (copy/paste) is time-consuming.

Are there any consolidated updates relating to version 8.x as docs appear mostly 7.x

4

We use to have a PDF rendition of the Virtuoso documentation, but no longer generate such.

There is now an OpenLink documentation git repository as well as a rendition in Markdown, which should be easier to work with.