Governance
Governance
Governance aims to detect problems in published metadata and specific links of HTML documents.
This policy category is broken down into 4 policies.
- Detect DC Metadata
- Detect Incorrect Privacy Usage
- Detect IPSV Metadata
- Detect Incorrect Terms And Conditions Usage
Detect DC Metadata
Detects missing Dublin Core metadata from a required configuration entry list of metadata entries to check for. If metadata that is expected does not exist in the HTML document as published metadata a policy exception will be generated.
Given the following example and with input expected to find the metadata value 'DC.author', a policy exception would be generated.
<head>
<meta name="DC.creator" content="Mr Smith" />
<meta name="DC.published date" content="11/02/2007" />
<meta name="author" content="Mr Smith" />
</head>
This policy can be configured to find additional published Dublin Core metadata, that the customer does not expect to be published.
Detect Incorrect Privacy Usage
Detects incorrect usage of privacy links, by checking against a
configuration entry that specifies the URL of the privacy link for
a given page language, ensureing the correct hyperlink for an
English page is used and not the link to the French privacy
page.
The location to the privacy link will be looked up first off, if this link does not exist within the document a policy exception will be generated.
When the privacy link does exist in the HTML document the language of the document is determined. Based on the language of the page the URL taken from the privacy link element will be checked for a match against the matching value in the configuration entry.
A policy exception will be generated if the wrong URL is used for the language of the document.
Detect IPSV Metadata
Detects missing IPSV metadata usage from a required configuration entry list of metadata entries to check for.
Given the following example and with input expected to find the metadata value 'dc.subject', no policy exception would be generated.
<head>
<meta name="DC.creator" content="Mr Smith" />
<meta name="DC.published date" content="11/02/2007" />
<meta name="dc.subject" content="refuse collections" scheme='eGMS.IPSV” />
</head>
Each expected IPSV metadata entry will be checked for, if they do not exist in the HTML document as published metadata a policy exception will be generated.
Detect Incorrect Terms And Conditions Usage
Detects incorrect usage of terms and conditions links against a configuration entry that specifies the URL of the privacy link for a given language, for example ensuring the English terms and conditions page is found for English language pages.
The location of the terms and conditions link will be found, if this link does not exist within the document a policy exception will be generated.
When the privacy link does exist the language of the page is determined. Based on the language of the page the URL taken from the terms and conditions link element will be checked for a match against the matching value in the configuration entry.
A policy exception will be generated if the wrong URL is used for the language of the document.