The StyleBook DTDs are found in the archive "xml-site-style.tar.gz" and
conform to the validation tests found in the StyleBook repository.

The XALAN-C documentation appears to conform to the StyleBook validation
examples.

The XALAN-J documentation and the current web pages have some deviation
from the StyleBook validation examples.  Frequently Asked Questions
"xalan/faq.xml" does not validate according to the StyleBook tests because
a <group> element is used.  The XALAN-J "faq.xml" also requests validation
using "document.dtd" instead of "faqs.dtd" resulting in no DTD definition
of <faqs> and <faq> elements.  This works only because non-validating XML
parsing is used and the consuming XML application understands the markup.

I will be correcting these deficiencies with my work on the XALAN-C and
XALAN-J documentation projects.

Source:  xalan/java/trunk/xdocs/sources/xalan/faq.xml

This file does not conform to the StyleBook DTD validation.  However, the
current web page is created from this XML.  I will try to accommodate XML 
validation in the rework of the documentation, making changes to the style
DTD validation library as needed.

The use of the <group> element is currently problematic, but support can
be designed into the new transformations for web page design.  My work
with the XALAN-C faq uses automatic list enumeration with template
recursion.  I will try to make the XSLT changes to accommodate the <group>
element as used in the XALAN-J faq page and still preserve the XALAN-C
StyleBook faq page design.

I note that a <group> element is defined as a child of the <book> element.
 This has a separate issue wherein the <entry> child element has no label
attribute.  This affects the document navigation area.  A DTD edit is also
required to fix this.

I have created XSLT stylesheets that understand the StyleBook test suite
and am using them as the basis for XALAN, XALAN-C, and XALAN-J web page
creation.  This effort also provides a migration path away from the Java
StyleBook program to something that is easier to maintain.  I am also
creating a XALAN documentation style guide to assist documentation project
contributors.

Sincerely,
Steven J. Hathaway



---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscr...@xml.apache.org
For additional commands, e-mail: xalan-dev-h...@xml.apache.org

Reply via email to