From WebDAV Folder to Published Weblog

Watch the Construction Chain

The screencast follows the storyboard scene order: the WebDAV source folder, the index.vsp weblog engine and publication shell, RSS and Atom feeds served from the same collection, the friendly public route, a selected post rendered inside the weblog shell, and finally that post's direct WebDAV resource link.

The Source Folder

The weblog begins with ordinary HTML documents at /DAV/home/demo/Public/fifa-kg-player-reports/. Each player report is already a self-contained intelligence artifact generated from the OpenLink FIFA World Cup Knowledge Graph. The folder is not a staging abstraction — it is the publishing substrate.

• Lionel Messi
• Rodri
• Erling Haaland
• Ousmane Dembele
• Pau Cubarsi
• Lamine Yamal
• Michael Olise
• Kylian Mbappe
• Jude Bellingham
• Achraf Hakimi
• Luis Diaz
• Mohamed Salah

Posts, Engine, and Publication Shell

Each .html file is treated as a weblog post. Virtuoso enumerates the WebDAV collection dynamically through its resource tables — the post list is not hand-maintained, and the newest resources appear first. Every post keeps two identities: its direct WebDAV resource URL, and its weblog permalink through the VSP route.

index.vsp is the weblog engine. It renders a publication shell — a sticky masthead, RSS/Atom/AtomPub links, a recency-ordered archive sidebar, search and filtering, and selected-post rendering through ?post={filename} — around the reports, while preserving the reports themselves inside an embedded reading frame. The reader experiences a weblog; the system still operates on files.

Feeds From the Same Folder

The same index.vsp entry point serves alternate feed modes from the same discovered post list used by the HTML view — no separate feed generator required. Each feed item points back to the weblog route and the selected report.

The AtomPub service document downloads rather than renders inline in most browsers (its atomsvc+xml content type is not a browser-displayable format), so the screencast shows RSS and Atom live; the AtomPub response is captured here instead:

The Route

Virtuoso maps friendly public paths to the DAV collection via a VHOST mapping, declaring index.vsp as the default page. This is the moment the folder gains a public weblog address — and the mapping keeps the DAV collection executable as VSP, so the browser receives the rendered weblog rather than raw server-page source.

Living Posts and the Deployable Bundle

Each report HTML file keeps its own intelligence sections — identity, tournament snapshot, passing and physical analytics, event maps, and live SPARQL query links. The weblog does not flatten or rewrite that content; it presents the selected report in context and supplies navigation around it. When a report is improved, the WebDAV resource is replaced, and the weblog picks up the improved document from the same collection.

The construction bundle that deploys the engine separates two concerns: content publication (the player report HTML files in WebDAV) and weblog engine publication (the VSP page, deploy SQL, and route mapping). That separation is what keeps the weblog maintainable.

Metadata and Facets

WebDAV resource metadata can carry schema:category values. When present, the weblog engine can expose category facets and filtered archive views without a separate content-management database — the file remains the post, and DAV properties enrich how it is discovered.

Publication Checks

The final check confirms the whole construction chain: the reports are in WebDAV, the VSP engine enumerates them, the route executes the engine, the weblog shell renders the selected report, feeds expose the same archive, and direct resource links remain available. At that point, the WebDAV collection has become a weblog.

Ordinary files became a live, feed-enabled weblog through Virtuoso Server Pages over WebDAV.