From 44ead1dfae924340c7968d61f4c35bdc8725a987 Mon Sep 17 00:00:00 2001 From: Leon van Kammen Date: Sun, 24 Sep 2023 11:12:52 +0200 Subject: [PATCH] update documentation --- doc/RFC_XR_Fragments.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/RFC_XR_Fragments.md b/doc/RFC_XR_Fragments.md index 200c181..2db54b3 100644 --- a/doc/RFC_XR_Fragments.md +++ b/doc/RFC_XR_Fragments.md @@ -768,9 +768,9 @@ here are some hashtagbibs followed by bibtex: > when an XR browser updates the human text, a quick scan for nonmatching tags (`@book{nonmatchingbook` e.g.) should be performed and prompt the enduser for deleting them. -# Broken links +# Transclusion (broken link) resolution -There's a soft-mechanism to harden links & prevent broken links in various ways: +In spirit of Ted Nelson's 'transclusion resolution', there's a soft-mechanism to harden links & prevent broken links in various ways: 1. defining a different transport protocol (https vs ipfs or DAT) in `src` or `href` values can make a difference 2. mirroring files on another protocol using errorcodes in `src` or `href` properties