Good Practice Guide for Developers of Cultural Heritage Web Services
Good Practice Guide for Developers of Cultural Heritage Web ServicesAn audit was made of the Good Practice Guide Web site on Thursday 3rd March 2005.
The ,rvalidate HTML validation tool was run over the entire Good Practice Guide Web site
from the entry points listed below:
| Area | Report | Comments | Current findings |
|---|---|---|---|
| GPG entry point | [View report] | All 16 pages compliant. | [Validate] |
Based on these findings the site has been found to be valid HTML.
The ,cssvalidate tool was run over the
Good Practice Guide Web site in order to validate a number of the external stylesheet
files. The check was carried out from the entry points listed in the following
table.
| Area | Comments | Current findings |
|---|---|---|
| Good Practice Guide entry point | Valid CSS file. | [Validate] |
| Good Practice Guide Introduction Page | Valid CSS file but error message is given | [Validate] |
The CSS files checked appeared to comply with the CSS standard However an error message is given when pages other than the home page are checked.
The message is:
Please, validate your XML document first!
Line 5 Column 6
The processing instruction target matching "[xX][mM][lL]" is not allowed.
This error is caused by a number of variables being inserted above the DTD in the source code. The css is the same as for the entry page and is valid.
Exceptions: This form of validating does not cover inline style sheets.
The ,rchecklink tool was run over the entire Good Practice Guide Web site.
| Area | Report | Comments | Current findings |
|---|---|---|---|
| Good Practice Guide entry point | [View report] | 16 pages were checked. | [Check] |
1 broken link (404 error message) was found on the site.
Note that the link-checking tools do have some limitations. For example some Web sites have a short 'time out' time, others blocked access to checking tools by the robots.txt, the Web site may be temporarily unavailable, etc.
In addition to the tool described above the
Xenu software
(version 1.2d) was also used to link-check the Good Practice Guide Web site. This tool was
used in order to ensure that all resources on the Good Practice Guide Web site were checked
and to see if any link problems not detected by the ,rchecklink
tool were found.
Xenu was used first to check local links. Then it was used to check all links.
The Xenu link check results for local links and external links are available. A number of link problems not detected in the above reports were found. These problems are being investigated. Note that some problems are artifacts of the link checking process.
The NetMechanic spell checker was run over the entire QA Focus site from the points listed below:
All spelling mistakes were noted.
All spelling mistakes were corrected.