From 73c2001e7790132a0bb39785168bac117108f63a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martynas=20Jusevi=C4=8Dius?= Date: Fri, 19 Jun 2026 08:42:33 +0200 Subject: [PATCH] Fix non-canonical XMLLiteral in dataspace.ttl MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Replace the numeric character reference → with the literal → so the rdf:XMLLiteral is canonical XML. Jena 6 rejects entity references in XMLLiteral lexical forms with "not valid for datatype XSD XMLLiteral". Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/reference/dataspace.ttl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/dataspace.ttl b/docs/reference/dataspace.ttl index ae6886c..1014519 100644 --- a/docs/reference/dataspace.ttl +++ b/docs/reference/dataspace.ttl @@ -67,7 +67,7 @@

Administration

Every administration application is related to one end-user application. It cannot exist standalone.

The base URI of an administration application is the base URI of its end-user application with the admin. subdomain - prefixed to the host (e.g. https://example.com/ → https://admin.example.com/). Because the admin application lives on + prefixed to the host (e.g. https://example.com/ → https://admin.example.com/). Because the admin application lives on its own subdomain (origin), it no longer occupies a path within the end-user application.

Since LinkedDataHub 5.1.0 the administration application is served on the admin. subdomain rather than under an