(This page informs developers of user agents (UAs) that can handle sitemaps, including browsers and search engines. If you’re a developer of CMS software, you’re acting on behalf of a webmaster, so you should find the webmaster guide more appropriate.)
The possibilities…
The Firefox extension was written to to allow Firefox users to take advantage of SSP sitemaps, but sitemaps are not written for a specific browser. Keen developers are invited to write to their own sitemap-reading software, to support other browsers and user agents especially, but also for other related applications, and provide alternative renditions of sitemaps, according to the needs of the user.
Here are some alternative renditions:
- sidebar hierarchy
- breadcrumbs
- pop-up menu hierarchy
- neighbouring/related pages
- role/primary pages
- oral/spoken
Alternative classes of user agent include:
- desktop browsers (Firefox, Opera, Chrome, Safari…)
- mobile devices (smartphones, iPhone/iPad, Android…)
- search engines/indexing robots (Google…)
This page specifies what is expected of your software (the implementation) to maintain interoperability with sitemaps that webmasters offer with their content.
Resources for developers of third-party implementations
- Implementation Behaviour
- File format
- RFC2616: Hypertext Transfer Protocol -- HTTP/1.1
- RFC2396: Uniform Resource Identifiers (URI): Generic Syntax
- XML Namespaces: 1.0 (Third Edition)
- XML Path Language: XPath 1.0, XPath 2.0
- Standard-Sitemap Project on SourceForge
- SVN repository at SourceForge
- Mailing list
Additional resources for Firefox Extension developers
- View source in repository at SourceForge
- Source documentation
Additional resources for Safari Extension developers
Additional resources for Google Chrome Extension developers
Developer FAQ
None yet…