sitemap: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 5: Line 5:


== Problem ==
== Problem ==
Enable the automatic generation of a number of different sitemap and related mechanisms from existing HTML navigation constructs by specifying a minimal amount of semantic information.  There is currently no way to encode in a machine readable way which navigation link elements pointing to locations in a site should be considered for inclusion in a sitemap.xml, cache manifest or related artifact, additionally information is not currently available which would enable specification of priority weighting or frequency of change.
Enable the automatic generation of a number of different sitemap and related mechanisms from existing HTML navigation constructs by specifying a minimal amount of semantic information.   


There is currently no way to encode in a machine readable way which navigation link elements pointing to locations in a site should be considered for inclusion in a sitemap.xml, cache manifest or related artifact, additionally information is not currently available which would enable specification of priority weighting or frequency of change.
Currently accurate sitemap.xml files, HTML sitemaps and cache manifests are written manually, or created by supplying information generator services/sites.  This is rather disconnected from our sites, and not always as accurate as we would like.
== Use Cases ==
Examples of what could be generated if we had such information:
Examples of what could be generated if we had such information:
* sitemap.xml
* sitemap.xml
Line 15: Line 20:


Typically these constructs leverage link elements which conveniently expose an 'href' attribute.  Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a sitemap.xml.
Typically these constructs leverage link elements which conveniently expose an 'href' attribute.  Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a sitemap.xml.
Currently the alternative is to either write a site map manually, or supply information to a generator (the said data being disconnected from your site).


Useful metadata could be generated by machines or browser plugins with both leveraging a simple microformat.
Useful metadata could be generated by machines or browser plugins with both leveraging a simple microformat.

Revision as of 19:21, 23 April 2012

<entry-title>Sitemap</entry-title>

Authors

Ross McDonald

Problem

Enable the automatic generation of a number of different sitemap and related mechanisms from existing HTML navigation constructs by specifying a minimal amount of semantic information.

There is currently no way to encode in a machine readable way which navigation link elements pointing to locations in a site should be considered for inclusion in a sitemap.xml, cache manifest or related artifact, additionally information is not currently available which would enable specification of priority weighting or frequency of change.

Currently accurate sitemap.xml files, HTML sitemaps and cache manifests are written manually, or created by supplying information generator services/sites. This is rather disconnected from our sites, and not always as accurate as we would like.

Use Cases

Examples of what could be generated if we had such information:

  • sitemap.xml
  • HTML sitemap for usability/accessibility
  • HTML5 cache manifest

Countless sites contain HTML navigation constructs which already detail all/most of the information required to build an HTML sitemap or cache manifest, and parts of the information required to build a sitemap.xml file.

Typically these constructs leverage link elements which conveniently expose an 'href' attribute. Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a sitemap.xml.

Useful metadata could be generated by machines or browser plugins with both leveraging a simple microformat.

Proposal

Per the microformats process: