I spent yesterday just getting a feel for the general flow of
axkit.org. My notes are below. Now for my feelings about the
overall design of www.axkit.org:
1 - there are certain pages in axkit.org which should be raw
completely anonymous XML. These files are:
index.xml, faq.xml, features.xml, install.xml, license.xml,
mailinglist.xml, and support.xml
Because they are not raw XML, this is undesirable for others
wishing to use these files in their sites in a different way. it
is also undesirable because it led to repeated manual entry of
the same DOCTYPE lines. And finally, it is undesirable because it
leads to unparseable XML (unparseable by MSIE 5.1... visit
http://www.axkit.org/index.xml?passthru=1)
2 - as raw XML, they need to be completely free of any view
dependencies or preferences
3 - display preferences (stylesheet delegation) for raw XML files
should be specified in one location
4 - not only display preferences but display dependencies (ie,
faq.xml should be displayed with sidebar.xml and news.xml),
should also be in one central location.
5 - such centralization would allow xml developers to make raw
xml documents, while site maintainers could "weave together" all
the various xml by centralized declaration of the display
preferences and dependencies. In fact, given the "why axkit?"
document, it is clear that such design is almost obligatory.
6 - webpage_html.xps could be the central place for defining
axkit.org's central look-and-feel. Or alternatively, is there
someway to setup the Apache httpd.conf so that the protocol for
stylesheet delegation is there? Ie,
<Directory /axkit.org>
AddAxStylesheet "default" "/stylesheets/webpage_html.xps"
AddAxStylesheet "alternate" "/stylesheets/webpage_html.xps"
AxAddViewDependencies "/sidebar.xml" "/news.xml"
</Directory>
[ day one notes on axkit.org design ]
- index.xml
1. Sets up its default and alternate stylesheets to be
webpage_html.xps
2. Includes /sidebar.xml and /news.xml via DOCTYPE statement
Both of these files are pure XML data with no references to
stylesheets. In fact, news.xml may have been downloaded via some
sort of batch process and never been touched by the site author!
3. Describes index webpage content (the part in the middle between
the sidebar and the RDF bar... hey where's the Hershey bar?) in
XML
4. Other pages have the exact same things in them, except they do
not list both stylesheets, just one. These pages are faq.xml,
features.xml, install.xml, license.xml, mailinglist.xml, and
support.xml.
- sidebar.xml: Plain xml page with no stylesheet info
- news.xml: Plain xml page with no stylesheet info
- webpage_html.xps
This is an xpathscript file (ie, one written to be processed with
XML::XPath, which one could say is alternative to XML::Twig and XSLT)
1. This includes sidebar_html.xps, rdf_html.xps and spacer.xps via
server-side include notation
File Inclusion Mechanisms
!--#include - used in Xpathscript
taglib - used somewhere, somehow!
doctype - used at the top of XML files to include other XML files
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
