AxKit

Apache AxKit was an XML Apache publishing framework run by the Apache foundation written in Perl. It provided conversion from XML to any format, such as HTML, WAP or text using either W3C standard techniques, or flexible custom code.

Apache AxKit
Developer(s)Apache Software Foundation
Final release
1.7 / November 4, 2005 (2005-11-04)
Written inPerl
Operating systemCross-platform
TypeXML
LicenseApache License 2.0
Websiteweb.archive.org/web/20141008204847/http://www.axkit.org/

AxKit was a standard tool in early digital humanities presentation work, being used to convert formats such as Text Encoding Initiative XML to HTML.[1] It is still used by some institutions,[2] but software such as eXist and Apache Cocoon is normally used in modern projects.[3]

Apache Axkit was retired in August 2009.[4]

References

  1. Morgan, Eric Lease (2005). "Creating and managing XML with open source software". infomotions.com. Retrieved 2 December 2011.
  2. "OSS Watch - Colophon". oss-watch.ac.uk. 2011. Retrieved 2 December 2011. The XML documents are transformed dynamically when they are accessed. The Apache web server is configured to use Apache AxKit to do the transformation, and AxKit is configured to use some XSLT stylesheets to do these transformations. Depending on the XSLT stylesheet used, an XML document will render either as HTML, HTML (for text only), HTML (for simple printing) or PDF (for more sophisticated printing).
  3. "simple dynamic transformation of xml with htaccess, php, and xslt | In my <element/>". blogs.oucs.ox.ac.uk. 2011. Retrieved 2 December 2011. I often transform from TEI XML to XHTML as part of projects, but in some instances it is more difficult to manage using things like the eXist XML Database or Apache Cocoon, or even AxKit.
  4. "Apache AxKit - Apache Attic". attic.apache.org. 2011. Retrieved 2 December 2011. Apache AxKit moved into the Attic in August 2009. Apache AxKit was an XML Application Server for Apache. It provided conversion from XML to any format, such as HTML, WAP or text using either W3C standard techniques, or flexible custom code.

Further reading

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.