sitemap - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:33:02Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:33, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~Sitemap~~</entry-title>~~		{{DISPLAYTITLE:Sitemap}}

	Per the [[process]], this is an effort to develop a sitemap microformat to 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.		Per the [[process]], this is an effort to develop a sitemap microformat to 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.

Tantek: move a summary statement to the top, expand problem statement, move a use-case to that section

2012-04-23T21:19:17Z

move a summary statement to the top, expand problem statement, move a use-case to that section

← Older revision		Revision as of 21:19, 23 April 2012
Line 1:		Line 1:
	<entry-title>Sitemap</entry-title>		<entry-title>Sitemap</entry-title>

	==~~Authors~~==		Per the [[process]], this is an effort to develop a sitemap microformat to 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.
			* [[sitemap-examples]]
			* [[sitemap-formats]]
			* [[sitemap-brainstorming]]

			==Editor==
	[http://www.bheap.co.uk/about/ross.html#about-me Ross McDonald]		[http://www.bheap.co.uk/about/ross.html#about-me Ross McDonald]

	== 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.		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.

			The separate sitemap.xml file is a "sidefile" and often violates [[DRY]] in that sites typically provide similar navigation structures in visible HTML.

	~~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.~~		== Use Cases ==
			A sitemap microformat would enable the following use-cases:

	~~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~~.		* 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.

	~~== 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 23:		Line 30:
	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.

	== ~~Proposal~~ ==		== See Also ==
	~~Per the microformats [[process]]:~~

	* [[sitemap-examples]]		* [[sitemap-examples]]
	* [[sitemap-formats]]		* [[sitemap-formats]]
	* [[sitemap-brainstorming]]		* [[sitemap-brainstorming]]
	* [[sitemap-issues]]		* [[sitemap-issues]]

Rossputin at 19:21, 23 April 2012

2012-04-23T19:21:21Z

← Older revision		Revision as of 19:21, 23 April 2012
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.

Rossputin at 19:14, 23 April 2012

2012-04-23T19:14:37Z

← Older revision		Revision as of 19:14, 23 April 2012
Line 5:		Line 5:

	== Problem ==		== Problem ==
	Enable the automatic generation of a number of different sitemap and related mechanisms from existing HTML by specifying a minimal amount of semantic information.		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.

	Examples ~~that~~ could be generated:		Examples of what could be generated if we had such information:
	* sitemap.xml		* sitemap.xml
	* HTML sitemap for usability/accessibility		* HTML sitemap for usability/accessibility

Rossputin at 17:29, 23 April 2012

2012-04-23T17:29:34Z

← Older revision		Revision as of 17:29, 23 April 2012
Line 19:		Line 19:

	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.

	~~== Existing standards ==~~
	~~The [http://www.sitemaps.org/protocol.html sitemap] protocol is very simple.~~

	== Proposal ==		== Proposal ==

Rossputin at 14:58, 21 April 2012

2012-04-21T14:58:55Z

← Older revision		Revision as of 14:58, 21 April 2012
Line 5:		Line 5:

	== Problem ==		== Problem ==
	Enable the automatic generation of sitemap~~.xml~~ from existing HTML by specifying a minimal amount of semantic information.		Enable the automatic generation of a number of different sitemap and related mechanisms from existing HTML by specifying a minimal amount of semantic information.

	Countless sites contain HTML navigation constructs which already detail parts of the information required to build a sitemap 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 ~~site map~~.		Examples that could be generated:
			* 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.

	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).		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.

	== Existing standards ==		== Existing standards ==
	The [http://www.sitemaps.org/protocol.html sitemap] protocol is very simple.		The [http://www.sitemaps.org/protocol.html sitemap] protocol is very simple.

			== Proposal ==
	Per the microformats [[process]]:		Per the microformats [[process]]:

Rossputin at 11:57, 20 April 2012

2012-04-20T11:57:01Z

← Older revision		Revision as of 11:57, 20 April 2012
Line 4:		Line 4:
	[http://www.bheap.co.uk/about/ross.html#about-me Ross McDonald]		[http://www.bheap.co.uk/about/ross.html#about-me Ross McDonald]

			== Problem ==
	Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.		Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.

Line 10:		Line 11:
	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).		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).

			== Existing standards ==
	The [http://www.sitemaps.org/protocol.html sitemap] protocol is very simple.		The [http://www.sitemaps.org/protocol.html sitemap] protocol is very simple.

Rossputin at 11:52, 20 April 2012

2012-04-20T11:52:55Z

← Older revision		Revision as of 11:52, 20 April 2012
Line 1:		Line 1:
	<entry-title>Sitemap</entry-title>		<entry-title>Sitemap</entry-title>

			==Authors==
			[http://www.bheap.co.uk/about/ross.html#about-me Ross McDonald]

	Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.		Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.

Rossputin at 11:50, 20 April 2012

2012-04-20T11:50:54Z

← Older revision		Revision as of 11:50, 20 April 2012
Line 3:		Line 3:
	Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.		Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.

	Countless sites contain HTML navigation constructs which already detail parts of the information required to build a sitemap file. Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a sitemap.		Countless sites contain HTML navigation constructs which already detail parts of the information required to build a sitemap 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 site map.

			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).

			The [http://www.sitemaps.org/protocol.html sitemap] protocol is very simple.

	Per the microformats [[process]]:		Per the microformats [[process]]:

Rossputin at 20:32, 19 April 2012

2012-04-19T20:32:59Z

← Older revision		Revision as of 20:32, 19 April 2012
Line 2:		Line 2:

	Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.		Enable the automatic generation of sitemap.xml from existing HTML by specifying a minimal amount of semantic information.

			Countless sites contain HTML navigation constructs which already detail parts of the information required to build a sitemap file. Add a way to specify 'priority' and maybe 'changefreq' and enough would be in place for machines to build a sitemap.

	Per the microformats [[process]]:		Per the microformats [[process]]: