Footnotes

1 The W3C calls it's approved specifications "Recommendations", rather than "standards", because they are an industry consortium, rather than a standards body. However most people consider thier recommendations to be standards, because they almost always become de-facto standards.

2 AxKit is very flexible in how it lets you transform the XML on the server, and there are many modules you can plug in to AxKit to allow you to do these transformations. For this reason, the AxKit installation does not mandate any particular modules to use, instead it will simply suggest modules that might help when you install AxKit.

3 While we share the XSP syntax with Cocoon, Cocoon allows you to embed Java code in your XSP, while AxKit only allows you to embed Perl code.

4 AxKit and Cocoon's ESQL taglibs are identical apart from a few minor deviations, such as how columns of different types are returned, and how errors are trapped (in Cocoon there are ESQL tags for trapping errors, whereas AxKit uses exceptions).