xmlns map Sitemap versus Topology or

May 6th, 2007

In my review of Roy Fielding's REST dissertation, I came across the term topology and how it relates to the term sitemap. This encounter led to a little sniffing around Cocoon and Popoon; projects which also use the term sitemap. In appreciation of standardization, I wanted to find out how similar or different each of these sitemaps document type definitions are.

Cocoon Sitemap

Kudos to the guys at bitflux for aligning popoon's sitemap dtd with cocoon's! Here's the example sitemap.xml included for slideml:


Nexista Sitemap Example

Nexista sitemap:


It is easy to note that this is syntactically very different from the Nexista sitemap dtd, which is frustrating to me, and something I'll want to fix in the coming months. However, I will probably suggest to Cocoon and Popoon that they reconsider their namespace in future versions, to something like site_topology. Sitemap is waaay to ambiguous for this type of critical entity. Maybe topology isn't the best term either, perhaps siteplan would work.

Various uses of the term Sitemap in the context of the World Wide Web

  • Web page(s) containing a list or index of links connecting to various pages within the same site, formatted for human visitors to observe and and interact with - sometime referred by two words instead of one, "site map".
  • An XML document containing a list of pages contained at a website for reference by search engines - see
  • An XML document used in web development to specify uris, resources, settings, as well as many other specifications for a web development framework to assemble, build, or otherwise process during different phases of the website or application, for example configuration or runtime.

The last entry there needs your help, and there are possibly other uses of the term sitemap. Those different uses alone are reason enough to try and clarify.

Sitemaps Standardized

Whether or not sitemaps gets clarified, it would be nice to have it standardized between nexista and cocoon. I'll check out some of the differences and estimate how feasible and time consuming that would be, and whether or not changing to the Apache Cocoon model would be an improvement. I've already noted some personal preferences in Cocoon's syntax:

  • Cocoon's sitemap uses
    , whereas Nexista uses

as well as some preferences to Nexista's sitemap syntax:


Yearly Indexes: 2003 2004 2006 2007 2008 2009 2010 2011 2012 2013 2015 2019 2020 2022