W3C home > Mailing lists > Public > public-wai-evaltf@w3.org > November 2011

AW: Defining website scope using Sitemap protocol

From: Kerstin Probiesch <k.probiesch@googlemail.com>
Date: Sun, 27 Nov 2011 11:25:17 +0100
To: "'RichardWarren'" <richard.warren@userite.com>, "'Alistair Garrison'" <alistair.j.garrison@gmail.com>, "'Eval TF'" <public-wai-evaltf@w3.org>
Message-ID: <4ed20ff9.5b38df0a.0dce.4c5f@mx.google.com>
Hi Alistair, Richard, all,

I also agree that one method is to use sitemaps.org. One other method could be using a freeware like "Xenu's Link Sleuth" (http://home.snafu.de/tilman/xenulink.html). Originally it was developed for finding broken links, but it is possible to exclude external links and to deactivate Broken links reports. Xenu's Link Sleuth is very fast (573 URLs in 43 seconds) but of course took it's time for very huge websites. It comes along with different export functions. One creates a sitemap (as .htm) according to the title-element another one creates a Google Sitemap File. If we decide for a software/freeware we need some test cases: smaller websites but also very huge websites for comparing the results, the time and also to find out if there might be problems (creating reports - especially for very huge sites). One problem might be that there seems to be no way to exclude image files, but probably there is no need to do this and it would depend upon the wording and a clear statement.



Kerstin Probiesch - Accessibility Consultant
Web: http://www.barrierefreie-informationskultur.de
XING: http://www.xing.com/profile/Kerstin_Probiesch
Twitter: http://twitter.com/kprobiesch

Von: RichardWarren [mailto:richard.warren@userite.com] 
Gesendet: Samstag, 26. November 2011 16:54
An: Alistair Garrison; Eval TF
Betreff: Re: Defining website scope using Sitemap protocol

Dear Alistair,
I agree that one method of defining the scope could be to use the site map (either the XML as used by google etc., or even the bog standard html site map) . You would need to provide a copy of the site map as it existed at the time of evaluation. It is a good example of “how an evaluator can express the scope”.
I don’t know how many examples we need to provide, the important thing is to make it clear that any scope statement is clear and reliable.
From: Alistair Garrison 
Sent: Saturday, November 26, 2011 1:06 PM
To: Eval TF 
Subject: Defining website scope using Sitemap protocol
Dear all,  
It seems that a good number of website owners / webmasters submit a sitemap to search engines.  The schema of choice for this sitemap (file) is apparently the Sitemap protocol - http://www.sitemaps.org/ (supported by Google, Yahoo!, and Microsoft.)
What would your thoughts be on using this sitemap file generated for a website, by the website owners / webmaster, to define the scope of a website? Possibly answering the question - How can an evaluator express the scope of a website.

Would be interested to hear thoughts / comments.

All the best 

Received on Sunday, 27 November 2011 10:25:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:40:19 UTC