Skip to content

The File Create, Save, and Share Paradigm — Revisited

Situation Analysis

Before the arrival of the HTTP abstraction—popularly known as the Web—data was held captive in documents containing application-specific content. In fact, content type is what distinguishes a plain file from a document: documents are application-specific files.

Through the introduction of URIsURLs, HTTP, and HTMLTim Berners-Lee unleashed a groundbreaking innovation that still resonates today and forms the foundation for:

  1. Unambiguous entity naming
  2. Negotiable document content types
  3. HyperText — documents referencing others via hyperlinks, as showcased by HTML
  4. HyperData — data linking to other data using RDF and Linked Data principles

Items 1–3 gave rise to the World Wide Web. Item 4 is now coming into its own—as a Giant Global Knowledge Graph loosely coupled with Large Language Models (LLMs), ushering in a new era of AI intelligence.

The Create, Save, and Share Paradigm in Practice

The /html/ folder added to our website is more than just a directory—it’s a digital staging ground for content meant to be shared with the world. Here, I follow a simple yet powerful pattern: create, save, and share. It’s a minimalist approach that mirrors the early spirit of the Web. For example, this is how Tim Berners‑Lee continues to document Design Issues related to the Web’s architecture.

Weblogs and Blogging

Recognizing the complexity that managing web servers and content distribution posed for most users, blogging solutions—pioneered by Dave Winer—emerged to address the need, offering user-friendly interfaces that embraced and extended the create, save, and share paradigm. Tools like Radio UserLand enabled authors to publish HTML documents and syndicate content easily via RSSAtom, and OPML, fostering an open ecosystem of publication and subscription.

Due to the rise of Web 2.0 centralization, weblogs and podcasts—once easily discoverable and subscribable via open feed readers—have become fragmented across proprietary, walled-garden platforms. This marked a shift away from the open publishing ethos of early blogging and syndication, trading interoperability and user control for convenience and monetization.

🧰 WebDAV & Briefcase: Local Habits, Global Reach

In the Age of AI, we can modernize this pattern using tools that blend local simplicity with global reach.

🧠 AI Tools Meets Web-Style Publishing

Today, with tools like ChatGPTClaude, and Gemini, content creation is faster than ever—but content ownership and distribution remain key questions.

Enter Virtuoso‘s Briefcase and its support for WebDAV. This infrastructure revives the early Web’s publishing model by enabling you to:

  • Use modern writing tools (including AI assistants)
  • Save directly to structured, public folders like /html//screencasts/, or /screenshots/
  • Offer content syndication and subscription via RSS, Atom, and OPML
  • Optionally add metadata like titles and descriptions for improved context and discovery
  • Automatically syndicate and share across both human-readable and machine-consumable channels
  • Use fine-grained, attribute-based access controls (ABAC) to manage document access

Fundamentally, this setup supports decentralized, standards-based publishing—without surrendering control to centralized platforms.

Here’s a sequence of screenshots from Virtuoso’s Briefcase, depicting how this comes together when its mounted via WebDAV to macOS Finder.

Briefcase Screenshots Folder mounted via WebDAV to macOS Finder
Briefcase Screencasts Folder mounted via WebDAV to macOS Finder
Briefcase HTML Folder mounted via WebDAV to macOS Finder

This approach lets users drag-and-drop files into shared folders like:

All folders auto-generate RSSAtom, and OPML feeds, readily consumed by AI agents, feed readers, and other Web clients.

🏷️ Metadata Makes the Difference

The Briefcase interface also allows optional addition of titlesdescriptions, and other metadata for each document or file—enhancing discoverability and guiding both human and machine consumption.

Basic Briefcase Folder View
Basic Briefcase Folder RSS Snippet
Briefcase Metadata UI

These enriched metadata elements power feed entries, making it easier to extract meaning and context from each resource.

📌 Final Thoughts

The file create, save, and share paradigm remains timeless—whether you’re writing a blog post, publishing research, or curating AI-ready knowledge artifacts. Tools like Virtuoso’s Briefcase bridge local workflows and global publishing seamlessly.

This isn’t nostalgia—it’s pragmatic innovation.

📚 Additional Information

Another Fediverse Test

Checking to see if ActivityPub propagation to the Fediverse is still working etc..

Fediverse Test 3

This time around, I expect this post to end up in BlueSky courtesy of the brige account https://bsky.app/profile/kidehen.mastodon.social.ap.brid.gy pegged to my Mastodon account.

BTW — If I “like” the Mastodon post, using my @kidehen@threads.net handle, I hope that makes its way over to Threads too!

Magic Folder Test 3

This time around, I an using the OpenLink Data Spaces (ODS) AI Agent to write to an ODS-Briefcase magic folder bound to WordPress (WP). This post will also show up across Mastodon (via Fediverse propagation) and Threads (via WP to Threads upstreaming)

Magic Folders Test 1

This is a test post from my OpenLink Data Spaces (ODS) Briefcase that I expect to propagate to Mastodon via the Fediverse and Threads via direct connection.

Second Fediverse Test Post

Another post testing propagation to the Fediverse.

Fediverse Test Post

This is a sample post to the Fediverse directly from my wordpress account. I expect to see this post via Mastodon by subscribing to to the handle @kidehen@idehen.me.

WebID

ID Claim: di:sha1;AqUL_k4oDxzUwmfsk0YgkOQg2Ts?hashtag=webid&uri=http%3A%2F%2Fid.myopenlink.net%2Fc%2FBNVWUO

WebID

WebID place-holder, generation in progress

WebID

WebID place-holder, generation in progress