anchor.diff:    <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 standard 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>
  +  <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>
  
positive.code:   </ul>
    <h3>Practical Requirements</h3>
    <h4>Findability</h4>
    <p>To achieve a standard certificate, you must provide at least one URL linking to the data from your website so people can find it. We recommend adding links to pages of relevant topics to the data.</p>
  
    <p>You need to provide at least one URL that demonstrates the data appearing within a list of similar data: this might be a repository such as <a href="http://data.gov.uk/">data.gov.uk</a> or alongside other similar datasets with a relevant search term on Google.</p>
  
    <p>You also need to provide the URL of at least one document that references the data in publications, such as reports of blog posts.</p>
    <h4>Accuracy</h4>
  
    <p>You can only achieve a standard level certificate for a one-off release of a single dataset, a collection of datasets, or an API operating over a static set of data that is always up to date. For example, the results of an experiment will never go out of date, but the locations of bus stops will change, therefore must be regularly updated to achieve a standard level certificate.</p>
  
    <p>If you are publishing a series of datasets over time, the delay between creating a dataset and publishing that dataset should be no more than half the gap between releases; for example if the data is released monthly, the data in that release should never be more than two weeks out of date. This helps to ensure that people work with up-to-date data.</p>
    <p>If you are publishing an API, you must provide downloads of the data behind that API to achieve a standard level certificate. New dumps must be created within a week of any change to the data. If the data can be changed, you must also commit to correcting any errors people find within it.</p>
    <h4>Quality</h4>
    <p>You must provide documentation about any known quality issues with the data you are publishing. This helps reusers judge how much the data should be trusted.</p>
  
  
negative.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 silver 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 silver 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 silver 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 silver 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 silver level)</li>
    </ul>
    <h3>Social Requirements</h3>
    <p>To achieve a silver 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>
  