=============================================================
PEG refstring_dtd--tjl: A DTD for refstrings
=============================================================
:Author: Tuomas J. Lukka
:Last-Modified: $Date: 2003/09/28 12:35:29 $
:Revision: $Revision: 1.1 $
:Status: Current
:Affects-PEGs: alph_lite--tjl
With Alph lite, we need to stabilize at least that data format.
There are several problems with the current XML format:
- for RICC (URN5) text spans and fake text spans, the actual
text is not written into the XML inside them. This would be
useful
- the element names are less than clear
Issues
======
- What is the name for this DTD? RefString is what it started
as, but later it was realized that these are *not* referential
strings but *idded* strings.
RESOLVED: Transcludable String, or TString for short.
Spans are Transcludable Spans or TSpans
- Should we have an element that surrounds a whole TString?
What about elements for fake spans?
RESOLVED: We should have an **optional** surrounding
element, to allow easy integration in different ways.
Using elements for fake spans is pointless
as they are best modeled by plain strings: consider::
abcd
abcd
In *all* semantics, these two lines should be equivalent.
- What should be the public identifier of this DTD?
RESOLVED: The best reference to public identifiers
I've found on the web is http://docbook.kldp.net/stuff/tdg/ch02s03.html
According to those rules, we should probably use
``+//IDN fenfire.org//DTD Transcludable String v1.0//EN
- What should be the URI for use with XML namespaces?
RESOLVED: The URI should be, analogous to the RDF vocab
conventions,
``http://fenfire.org/xmlns/2003/09/tstring#``
The Transcludable String XML DTD
================================
Define a Transcludable String DTD as follows::
XXX Change to XML schema!
Publish the DTD and a start a short document of how it is used (follows).
Using the DTD
=============