From 465a7779b47e6f88b0e1077a1a454669480ffd0b Mon Sep 17 00:00:00 2001
From: Lou
Date: Wed, 20 Dec 2023 16:48:56 +0000
Subject: [PATCH] Update howtoChain.xml
---
Documents/pureODD/howtoChain.xml | 37 ++++++++++++++++----------------
1 file changed, 19 insertions(+), 18 deletions(-)
diff --git a/Documents/pureODD/howtoChain.xml b/Documents/pureODD/howtoChain.xml
index 9e384e5a7d..c4f2bb0423 100644
--- a/Documents/pureODD/howtoChain.xml
+++ b/Documents/pureODD/howtoChain.xml
@@ -9,13 +9,14 @@
Lou Burnard
- Discussion draft
+ As published on lb42.github.io
authored from scratch
+ Minor changes for publication on lb42.github.io
Expanded and announced on TEI-L
Uploaded for Council review
Drafted first part on train from Paris to La Souterraine; then lost
@@ -73,22 +74,21 @@
Let's look more closely at the way the TEI defines a very light weight schema called
TEI Bare. Its schema specification element begins like this:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
No source is specified, so declarations for the elements requested here will
be taken from the current p5subset.xml.
@@ -251,7 +251,8 @@
the value for the source attribute on the schemaSpec defining our
ODD. We could do the same thing (though I don't recommend it) even at the level of
individual elements, by specifying a different version as source for an
- elementSpec.
And just to make life a little simpler, there is an
+ elementSpec.
+ And just to make life a little simpler, there is an
officially recognized short cut built into the current ODD processing stylesheets:
instead of the lengthy URL above, we could simply say tei:3.0.0
. For
example, supposing that for some strange reason we don't want to add the current