anchor.diff:      <li>If you are publishing an API, you should have a URL for the endpoint of that API at which a description is also published.</li>
     </ul>
   
  -  <h2>Pilot Certificate</h2>
  -  <p>A Pilot certificate has a number of additional requirements to ensure a pilot release of open data is successful.</p>
  -
  -  <p>To achieve a Pilot certificate, you must have a webpage describing the data. This can be on a repository such as <a href="http://data.gov.uk/">data.gov.uk</a>.</p>
  -
  -  <h3>Legal Requirements</h3>
  -  <p>If your right to publish the data is complicated or unclear, to achieve a Pilot certificate you must publish a document that describes the risks that reusers of the data would be taking on if they use and publicise the data. For example, there may be a risk of the data being removed because of a legal challenge.</p>
  +  <h2>Silver Certificate</h2>
  +  <p>A Silver certificate has a number of additional requirements to ensure a silver release of open data is successful.</p>
  +
  +  <p>To achieve a Silver certificate, you must have a webpage describing the data. This can be on a repository such as <a href="http://data.gov.uk/">data.gov.uk</a>.</p>
  +
  +  <h3>Legal Requirements</h3>
  +  <p>If your right to publish the data is complicated or unclear, to achieve a Silver certificate you must publish a document that describes the risks that reusers of the data would be taking on if they use and publicise the data. For example, there may be a risk of the data being removed because of a legal challenge.</p>
   
     <p>If the data originally comes from elsewhere, you must publish a document that describes where the data comes from. This helps people who want to use the data to know how much to trust it.</p>
   
  
positive.code: 
    <p>If you provide an API to access the data, and you are publishing dumps of the data as well, then you should create a new dump every month or more frequently. This means that people who want to get hold of the whole set of data can get hold of a dump that isn't too out of date.</p>
  
    <p>You must consider how long you intend to publish the data for. For a pilot certificate, you should intend for the data to be available in the same form for at least a year. If it is not going to be available for at least a year, it is unlikely any reuser will invest time to use it except in proofs of concept.</p>
    <h3>Technical Requirements</h3>
    <p>If you are publishing a one-off release of a dataset, you must be able to provide a URL directly linking to that dataset so it can be downloaded.</p>
  
    <p>If you are publishing a series of datasets, the URLs for the datasets in the series should follow a consistent pattern so that people can predict the URL for a particular month for example, or create a script that downloads them all.</p>
  
    <p>To achieve a pilot certificate, the data must be published in a machine-readable format. Further to this:</p>
    <ul>
      <li>if you are publishing <strong>documents</strong> these must be published in a format for documents (which can include Word, OpenOffice or PDF at the pilot level)</li>
      <li>if you are publishing <strong>statistics</strong> the data must be published in a format for tabular data (which can include Excel at the pilot level)</li>
      <li>if you are publishing <strong>geographical data</strong> or any other kind of structured data, it must be published in a structured data format (which can include JSON, XML or CSV at the pilot level)</li>
    </ul>
    <h3>Social Requirements</h3>
    <p>To achieve a pilot certificate, you must provide technical documentation about the data to help people understand it with a URL for this documentation.</p>
  
    <p>You must also provide instructions for people to contact you:</p>
    <ul>
  
negative.code:   <p>You must take a regular offsite backup of the data. It is good practice for this to be a public backup (perhaps hosted by another organisation for you) in case access to your website is interrupted.</p>
  
    <p>If you are providing an API, you must provide documentation that informs people of the service level available. For example, what guarantees can you give about the uptime of the service, what rate limiting do you do, and how long are outages likely to last? You will need to provide a URL to a document describing the service level that you are providing.</p>
    <p>For a gold certificate, publication of the data must be a business-as-usual activity; you must ensure that its continued publication is incorporated into your medium-term plans.</p>
    <h3>Technical Requirements</h3>
    <h4>Locations</h4>
    <p>If you are publishing a series of datasets, you must:</p>
  