Hi Richard and Yves, hi all,
I made a change to xmlspec (the dtd we are using for editing
specifications in the W3C [0] ), it does not concern any element /
attribute declaration, but since the changes in the xmlspec-i18n.dtd
file are rather heavy, I created a new version. You will find it under
[1]. The only difference is that the default attribute "version" at the
spec element now has the value "002".
See the file i18n-extensions.mod [2] for last changes. All i18n
extensions for parameter entities have been seperated into the file
"i18n-extensions.mod". The comments on the extensions and the change log
is in this file as well. The respective element declarations are in the
file "i18n-elements.mod" [3]. They are invoked by the parameter entities
%i18n-extensions; and %i18n-elements;. Due to the order of XML DTD
processing it is necessary to put %i18n-extensions; BEFORE the parameter
entity definitions in the xmlspec-i18n.dtd, and %i18n-elements; at the
end of the file.
With the separation of the i18n declarations into separate parameter
entities it is now possible to evoke and stop certain i18n features
seperately. Buy using a statement like <!ENTITY % local.emph.class
"IGNORE">, the respective parameter entites are ignored, and the
original definition in the xmlspec-i18n.dtd is evoked.
This modularization technique (which is very common e.g. in Docbook or
the TEI [4]) makes it easier to separte the i18n extensions from the
original tag set, or - speaking in ITS terms - to have a mechanism for
separating an its tag set from the original dtd. So this is one solution
of our problem, which will also be discussed in the extreme paper / the
project review. If you have some comments already, let me know.
Best, Felix.
[0] http://www.w3.org/2002/xmlspec/#spec29
[1] http://www.w3.org/International/xmlspec/002/xmlspec-i18n.dtd
[2] http://www.w3.org/International/xmlspec/002/i18n-extensions.mod
[3] http://www.w3.org/International/xmlspec/002/i18n-elements.mod
[4] http://www.tei-c.org