Published on data.gov.uk (https://data.gov.uk)

Home > Code of Practice

Code of Practice

Secretary of State for Justice’s Code of Practice (datasets) on the discharge of public authorities’ functions under Part 1 of the Freedom of Information Act

Issued under Section 45 of the Act.

April 2013

Presented in Parliament by the Secretary of State for Justice pursuant to section [xx] of the Freedom of Information Act 2000.

Foreword

  1. This Code of Practice (datasets) fulfils the duty of the Secretary of State for Justice set out in section 45 of the Freedom of Information Act 2000 ("the Act”) in relation to datasets.
  2. Section 102 of the Protection of Freedoms Act 2012 amended section 11 (Means by which communication to be made) and section 19 (Publication schemes) of the Act and inserted new sections 11A and 11B. The practical effect of the amendments is to require a public authority releasing a dataset under that Act to do so in a way that enables the dataset to be used and re-used. This means that the public authority must, firstly, provide the dataset in a re-usable format, where reasonably practicable; and, secondly, grant a licence (in accordance with one of the specified licences in this Code) under which the dataset can be re-used.
  3. In addition, Section 45 of the Act has been amended so that there will be a Code of Practice issued under that section to include provisions relating to datasets.

CODE OF PRACTICE

This document provides guidance to public authorities as to the practice which it would be desirable for them to follow in connection with the discharge of their functions under Section 11,11A, 11B and 19 of Part I of the Act in relation to datasets.The Secretary of State for Justice, having consulted with the  information Commissioner, issues this Code of Practice under section 45 of the Act on April 2012. (Exact date TBC)

Laid before Parliament on April 2012 pursuant to section 45. (Exact date TBC)

Introduction

This Code of Practice provides guidance to public authorities as to the practice which it would, in the opinion of the Secretary of State for Justice, be desirable for them to follow in connection with the discharge of their functions in relation to datasets under section 11 (Means by which communication to be made), 11A (Release of datasets for re-use), 11B (Power to charge fees in relation to release of datasets for re-use) and section 19 (Publication Schemes) of Part I of the Act. It supplements the Code of Practice on the discharge of a public authority’s function under Part I of the Act, which covers all information (not specifically datasets) previously issued separately.

  • Log in to add reply [1]
[2]

Wouldn't it be better to have

Posted by JohnCrab [2] on Tue, 18/12/2012 - 17:07

Wouldn't it be better to have a code of practice based on a consensus of relevant stakeholders rather than the opinion of a Secretary of State.

 Flag as offensive [3] 

Words and expressions used in this Code have the same meaning as the same words and expressions used in the Act.

  • Log in to add reply [4]

Neither the Act nor this Code require the creation of datasets for publication, nor do they require datasets to be updated if they would not otherwise be updated as part of the public authority’s function. They are intended to increase publication of updated datasets which are already accessible and to make them available for re-use and, where possible, in a re-usable format.

  • Log in to add reply [5]
[6]

"Neither the Act nor this

Posted by MarionOswald [6] on Mon, 07/01/2013 - 11:55

"Neither the Act nor this Code require the creation of datasets for publication"

As set out in the ICO's new code of practice on anonymisation, certain datasets may require anonymisation before publication to ensure that personal data is protected appropriately. Would this be regarded as creating a new dataset?

 Flag as offensive [7] 

Public authorities should handle a request for a dataset in a way that meets their obligations under the Act and that conforms to the relevant Code of Practice issued under section 45. A public authority must disclose any information that has been requested under the Act, including datasets, unless an exemption applies. The amended provisions in sections 11, 11A, 11B and 19 create additional rights for applicants and additional duties for public authorities in respect of datasets but they do not affect whether or not a dataset should be released under the Act. In deciding whether to release a dataset, a public authority should consider any exemptions which may apply and in particular, consider the exemption in section 40 of the Act relating to personal data and the Information Commissioner’s Code of Practice on Anonymisation.

  • Log in to add reply [8]
[6]

"In deciding whether to

Posted by MarionOswald [6] on Mon, 07/01/2013 - 11:59

"In deciding whether to release a dataset, a public authority should consider any exemptions which may apply and in particular, consider the exemption in section 40 of the Act relating to personal data and the Information Commissioner’s Code of Practice on Anonymisation."

It may also be worth noting that there could be a risk of anonymising the 'wrong' field. A dataset may be anonymised and then proactively released. If subsequently a request is made for the same dataset with the previously anonymised field disclosed, then this may not be possible due to the risk of re-identification based on the comparison with the original dataset. Hence, the benefits of proactively disclosing some datasets may be reduced unless there is detailed consideration of the purposes to which they may be put.

 Flag as offensive [9] 

There is no special provision for incomplete datasets. Even if a dataset is incomplete, or in draft form, it is subject to requests under the Act in the same way as complete datasets or any other recorded information.

  • Log in to add reply [10]

The guidance in the Code covers the following areas: a. Scope b. Disclosing datasets in an electronic form which is capable of re-use c. Standards applicable to public authorities in connection with the disclosure of a dataset d. Giving permission for datasets to be reused e. Costs and fees f. Considering publication of datasets as part of a publication scheme g. Advice and assistance to persons making requests for information with requests for datasets h. Complaints

  • Log in to add reply [11]

Scope

This Code applies to datasets held by or on behalf of a public authority. The definition of dataset limits the application of the Code to datasets in electronic form that meet the criteria specified at section 11(5) of the Act.

  • Log in to add reply [12]

The definition of dataset at section 11(5) is as follows:

In this Act “dataset” means information comprising a collection of information held in electronic form where all or most of the information in the collection -

(a) has been obtained or recorded for the purpose of providing a public authority with information in connection with the provision of a service by the authority or the carrying out of any other function of the authority,

(b) is factual information which -

(i) is not the product of analysis or interpretation other than calculation, and

(ii) is not an official statistic (within the meaning given by section 6(1) of the Statistics and Registration Service Act 2007), and

(iii) remains presented in a way that (except for the purpose of forming part of the collection) has not been organised, adapted or otherwise materially altered since it was obtained or recorded

  • Log in to add reply [13]
[2]

Subject to interpretation

Posted by JohnCrab [2] on Tue, 18/12/2012 - 17:18

Point (b) (iii) - It is unclear (to me anyway) what this is getting at. Data is necessarily organised. Datasets often consist of many data items that are collected over a period of time and to publish them may require them to be anonymised, filtered, categorised or checked for accuracy.

 Flag as offensive [14] 
[15]

I agree with JohnCrab. The

Posted by Rick Mason [15] on Wed, 19/12/2012 - 13:35

I agree with JohnCrab. The intent of ensuring raw data is good, but the definition appears to exclude valid alterations like anonymisation and accuracy-checking.

 Flag as offensive [16] 
[17]

Definition of a dataset

Posted by IRU [17] on Tue, 08/01/2013 - 17:02

The definition of a dataset should have an 'and' or 'or' after the word authority.  Paragraphs 9 and 10 suggest it should be 'and'. 



 Flag as offensive [18] 

The first part of the definition (subsection (5)(a)) means that the datasets caught by the Act are those datasets which a public authority has originally obtained or recorded for the purposes of providing services or carrying out its functions, including decision-taking. The purpose of releasing these datasets is to increase transparency and accountability of a public authority’s decisions and functions.

  • Log in to add reply [19]

The second part of the definition limits datasets for the purposes of the Act to factual information subject to the three criteria in subsection (5)(b). The intention behind the first criterion, “not the product of analysis or interpretation other than calculation” is to catch ‘raw’ or ‘source’ data. The definition makes clear that mere calculation of information within the dataset does not count as ‘analysis’ or ‘interpretation’. Accordingly, the aggregation of data to form a high-level dataset (such as the creation of regional figures that were collected at district level, or the creation of annual figures from data that were collected weekly) would not by virtue of being aggregated take a dataset outside the definition.

  • Log in to add reply [20]

The intention behind the second criterion, to exclude official statistics, is to ensure there is no potential overlap with officials statistics (which may otherwise have been caught within the definition), which are subject to their own regime on disclosure and publication, including under the Statistics and Registration Service Act 2007.

  • Log in to add reply [21]

The third criterion, that the dataset “remains presented in a way that (except for the purpose of forming part of the collection) has not been organised, adapted or otherwise materially altered since it was obtained or recorded” again is intended to ensure only ‘raw’ or ‘source’ data is captured within the meaning. Again the purpose here is to exclude from the definition any data which has been manipulated, interrogated or has had any ‘value’ added or ‘expertise’ applied. Accordingly any changes or alterations made to the presentation of a dataset as originally compiled and recorded are relevant in considering whether the dataset is outside the scope of the definition. The key consideration here is whether the reorganisation or adaptation represents a ‘material alteration’ to the original presentation of the dataset. Minor, insignificant or insubstantial changes to a dataset will not take it outside the definition. Decisions will have to be made on a case by case basis by assessing what has been done to the raw data in the dataset.

  • Log in to add reply [22]
[23]

Valid cases of demand for non-raw data

Posted by TimDavies [23] on Mon, 03/12/2012 - 19:26

There are many cases where a requester might have a valid reason to request a non-raw dataset, but to want access to this as machine readable data.

For example, if an authority has taken a raw dataset of primary data on parking, then applied a process to aggregate this to generate spreadsheets on traffic or parking hot-spots, and this has then formed the basis of policy, a requester may be interested in the analysis spreadsheet, as well as, or instead of, the raw data.

These requesters appear to have no right to data under the current wording. Is there a valid justification for this? The desire to tightly define raw data should not lead to 'cooked' or prepared data only being available in PDF or print-out formats!

I realise the Act is worded with this restrictive definition that centres on raw data - and that unless my reading is wrong, it does not give a right to the processed data in machine readable form (even though this processed data could still be subject to the Freedom of Information Act). However, could the guidance highlight that, whilst raw data should be provided when requested and the tight definition is neccessary to ensure this, the definition should not exclude authorities from providing processed data products in machine readable forms if this is what the requestor wants. 

 Flag as offensive [24] 
[6]

An example of what would be

Posted by MarionOswald [6] on Mon, 07/01/2013 - 12:13

An example of what would be considered a minor or insubstantial change would be useful here. Also it may be worth clarifying that a requestor remains entitled to make a request under the FOIA for the data or information that underlies a dataset (they may be interested for research purposes for example), even if that dataset has been republished in useable format, and public authorities should deal with those requests in the usual way under the Act.

 Flag as offensive [25] 

The other key consideration in the definition is how much, if any, of the data in the dataset has been changed or altered. If ‘all or most’ of the data in the dataset meets the criteria set out in subsection 5, then the dataset will fall within the definition. It should thus not be possible for public authorities to get around the new provisions by making minor or insubstantial changes to the dataset as a whole, or making any changes to a minority of the data within the dataset. Even where a dataset has been significantly changed from the original dataset, such that the new information held no longer meets the definition of a dataset, the original dataset would still subject to the new provisions in the Act (provided of course it is still held by the authority).

  • Log in to add reply [26]

Where information requested meets the definition of a dataset, the authority will be under a duty to provide the dataset in a re-usable format (see below), where reasonably practical. However, the ‘re-use duty’ and relevant provisions relating to licensing in this Code do not apply to all datasets. The provisions that relate to licensing and the re-use of datasets apply only to datasets that are, or contain, a ‘relevant copyright work’. The definition excludes datasets subject to Crown copyright and Parliamentary copyright (see section 11A (8) of the Act).

  • Log in to add reply [27]

Disclosing datasets in an electronic form which is capable of re-use

When releasing any dataset under the Act public authorities must, as far as reasonably practicable, provide it in an electronic form which is capable of re-use, i.e. a re-usable format. A re-usable format is one that is machine readable, such as Comma-separated Value (CSV) format.

  • Log in to add reply [28]
[29]

TXT

Posted by philipjohn [29] on Tue, 27/11/2012 - 20:03

<p>Perhaps it would be more useful to pure text-based format, such as CSV because it's probably not unknown for someone to convert a CSV to a PDF and send that out!</p>

 Flag as offensive [30] 
[23]

This needs a better definition of machine readable

Posted by TimDavies [23] on Mon, 03/12/2012 - 19:36

The definition of re-usable needs to be expanded and clarified here. 

Points might include that a re-usable data is one for which:

  • A requester can open the data file in freely available and widely accessible software packages - this means that formats such as CSV should be preferred over, or offered in addition to formats like Excel, and proprietary formats which can only be openned with commercial or specialist software should be avoided. 
  • It is possible to process the data directly, carrying out any appropriate operations on it such as sorting columns, filtering rows, running aggregates of values - this requires well structured data. Where possible, the meaning of the data should not be contained in the layout. 
  • Common elements in the dataset are expressed in uniform ways - for example, dates are always in the same format, codes or names are always in the same case, and numbers are expressed consistently (e.g. 1,000 or 1000 but not a mixture of the two). 
  • The meaning of fields and values is clearly documented - either through clear naming of fields, or through accompanying descriptions provided along with the data.  

In addition, where possible machine readability is enhanced if:

  • The dataset uses common standards where they exist - including standard identifiers and standard field names. These might be standards like the public spending vocabulary developed for government, or third-party standards such as KML for indicating 'points of interest'

It is important to also note that it may be possible to provide data in a variety of machine readable formats, and where possible the authority should correspond with the requester to identify the best format. For example, points of interest could be provided in a CSV spreadsheet form, or KML. Ideally both would be provided: though depending on the context and the re-user one may be more appropriate than the other. 

 Flag as offensive [31] 
[23]

To back up these points, the

Posted by TimDavies [23] on Mon, 03/12/2012 - 20:12

To back up these points, the following blog posts might be useful:

  • Open Data takes more than CSV [32]
  • When Machine Readable Data Still Causes “Issues” – Wrangling Dates… [33]

I'm sure there are many others on the same theme...

 Flag as offensive [34] 
[35]

More examples needed

Posted by PeteThomson [35] on Wed, 05/12/2012 - 14:30

I agree with TimDavies that this needs a fuller definition. It would also benefit from a wider range of examples. Not all datasets can sensibly be produced in CSV - collections of documents or photographs for instance could meet the definition of a dataset. And re-usability, like openness, is a range rather than a dichotomy - for a table, PDF is more re-usable than JPEG, but less re-usable than Excel or CSV.

 Flag as offensive [36] 
[37]

Yes More Examples Please

Posted by John Kaye [37] on Mon, 07/01/2013 - 10:55

For example Spatial data. At the moment it is deemed acceptable to publish this as PDF maps, where it would be much more valuable to GIS community and others to release it as vector shapefiles or google kml files that can be reused by others. There is a wealth of this information in Local government planning departments and large projects such as The Olympics

 Flag as offensive [38] 
[37]

Yes More Examples Please

Posted by John Kaye [37] on Mon, 07/01/2013 - 10:55

For example Spatial data. At the moment it is deemed acceptable to publish this as PDF maps, where it would be much more valuable to GIS community and others to release it as vector shapefiles or google kml files that can be reused by others. There is a wealth of this information in Local government planning departments and large projects such as The Olympics

 Flag as offensive [39] 
[40]

Practical guidance

Posted by Alex_Hodge [40] on Thu, 10/01/2013 - 12:47

More detailed practical guidance needs to be provided alongside the code of practice to provide a more practical definition of datasets.  This could be developed alongside the guidance provided by the Information Commissioner’s Office.

 Flag as offensive [41] 
[42]

I agree the definition of re-usable needs more work

Posted by Owen Boswarva [42] on Thu, 10/01/2013 - 15:43

I agree with Tim that the definition of re-usable needs more work. The statement that "a re-usable format is one that is machine readable" is rather dogmatic, and not a universally held view. That is certainly the way IT developers tend to think about re-use of data, and the statement is more likely to be true for large datasets. However many datasets are re-used directly for analysis (i.e. just read and considered) and do not necessary need to be pre-structured.

The Code of Practice should encourage discussion based on the specifics of individual datasets. A single dataset may be suitable for a range of different re-uses and there will not always be an ideal format. When in doubt the public authority should try to strike a balance between making the data re-usable and preserving the data in its original context.

 Flag as offensive [43] 

Datasets are, by their nature, often created in formats that are capable of re-use. Therefore, if a public authority publishes a dataset in a non-re-usable format such as an image file, it should consider also publishing the dataset in its re-usable format before its conversion to an image file, or keeping a re-usable version of the dataset available. Where datasets are only held in non-re-usable formats, and it is impractical or too burdensome to convert the dataset into a re-usable format, the public authority is not obliged to convert the dataset before releasing it.

  • Log in to add reply [44]
[23]

Engagement?

Posted by TimDavies [23] on Mon, 03/12/2012 - 19:45

Worth a point that authorities are encouraged to respond to requests by proactively engaging with the requester and understanding how they might move towards providing more structured and regularly released open data in future? 

 Flag as offensive [45] 

Public authorities should consider best practice and any guidance on the provisions of datasets issued by the Information Commissioner.

  • Log in to add reply [46]
[23]

It may be useful to

Posted by TimDavies [23] on Mon, 03/12/2012 - 20:23

It may be useful to explicitly draw attention here to data protection guidance, and the recently released Anonymisation Code of Practice [47]. 

In addition, there is a specific risk of personal data leaking out the tracked changes or hidden fields of machine-readable files that authorities previously published only in PDF or print forms - and so in either this guidance, or the ICO guidance, it may be neccessary to address this privacy issue explicitly. 

It could be addressed here, or in the section on the costs of preparing a dataset for machine readable distribution, to note that this should include an audit of any potential privacy implications of releasing the data in the format of choice. 

 Flag as offensive [48] 

Standards applicable to public authorities in connection with the disclosure of a dataset

When releasing datasets public authorities should as far as possible adhere to the Public Data Principles (http://www.data.gov.uk/library/public-data-principles [49]). These principles are compulsory for central government departments and recommended for the wider public sector. Authorities may wish to publish or signpost to these principles on their website.

  • Log in to add reply [50]

When releasing a dataset, authorities should apply the Sir Tim Berners-Lee Five Star ranking system (http://www.w3.org/DesignIssues/LinkedData.html [51]). Whilst not a mandatory requirement this will help applicants in assessing the suitability for re-use of a dataset they have received.

  • Log in to add reply [52]
[42]

Do we need this?

Posted by Owen Boswarva [42] on Thu, 10/01/2013 - 15:46

Does this even need to be in the Code? TBL's Five Stars [53] are a useful mechanism for thinking about openness as it applies to data, but I'm not convinced they add anything to this particular process. It's important that the public authority makes clear the legal terms of re-use, but it's not the public authority's role to coach the applicant on what they can do with the data beyond that.

 Flag as offensive [54] 

Published datasets should, so long as there are no good reasons for it not to be provided, be accompanied by a sufficient amount of metadata and contextual information about how and why the dataset was compiled or created in order that users may fully comprehend the dataset they are dealing with and as part of compliance with Section 16 (duty to advise and assist) of the Act.

  • Log in to add reply [55]
[42]

Within reason

Posted by Owen Boswarva [42] on Thu, 10/01/2013 - 15:48

Well, to the extent that this is reasonably available perhaps. We need to make sure public authorities don't feel they need to write new documentation for every data release, particular as some will want to recharge for the time involved.

 Flag as offensive [56] 

When procuring new data processing systems, public authorities should reference the Government Principles for Open Standards in new government information technology specifications for software interoperability, data and document formats. The Principles are compulsory for central government departments, their agencies, non-departmental public bodies and any other bodies for which they are responsible for.

  • Log in to add reply [57]

Giving permission for datasets to be re-used

Datasets must be released with accompanying details of any licence conditions that apply to re-use of the dataset or otherwise any limitation on re-use by virtue of third party intellectual property rights.

  • Log in to add reply [58]

The public authority should ascertain whether copyright and/or database rights in the dataset are owned solely by the authority, that there is no other copyright owner with rights in the dataset. Nothing in the Act removes any rights of third parties in that dataset. If a public authority grants a licence to re-use a dataset where it is subject to intellectual property owned by a third party, the grant may constitute an infringement of the third party’s rights. Consideration should also be given to the extent to which it is appropriate to disclose such information, in particular with reference to sections 41 and 43(2) of the Act.

  • Log in to add reply [59]
[60]

Third Party Intellectual Property Rights

Posted by Ministry of Defence [60] on Mon, 07/01/2013 - 18:14

The references to third party intellectual property rights are difficult to reconcile with section 11A(1)(c) of the FOIA 2000, which excludes from the ambit of section 11A datasets other than those where the public authority is the only owner of the copyright. The scope of this Code consequently risks exceeding its statutory basis, addressing more than just the application of section 11A.

 Flag as offensive [61] 

Where the copyright or database right in a dataset is owned wholly or partly by a third party, a public authority can only give permission for re-use of the dataset if it has been authorised to do so by the relevant third party rights holder. The ‘re-use duty’ only applies where the public authority is the only owner of the copyright or database right. If the authority does not have the legal authority to make it available for re-use it should make it clear to the applicant when releasing the dataset that this is the case. Even when the public authority is not able to license re-use, it must still provide the dataset in a re-usable format, so far as reasonably practicable, if the applicant has asked for an electronic version.

  • Log in to add reply [62]
[29]

"if the applicant has asked

Posted by philipjohn [29] on Tue, 27/11/2012 - 21:30

"if the applicant has asked for an electronic version." should be removed, IMO

 Flag as offensive [63] 
[60]

Plans, Drawings and Maps

Posted by Ministry of Defence [60] on Mon, 07/01/2013 - 17:02

Notwithstanding our general comments below relating to extent that this Code should be addressing datasets that fall outside the scope of section 11A, it is worth mentioning that where the dataset comprises plans, drawings or maps, the public authority is mandated to use a particular formula of wording in order to indicate that a third party enjoys reserved rights in the data. Details can be found in the the Copyright (Material Open to Public Inspection) (Marking of Copies of Plans and Drawings) Order 1990 and The Copyright (Material Open to Public Inspection) (Marking of Copies of Maps) Order 1989.

 Flag as offensive [64] 
[60]

Unreusable Data in a Reusable Format

Posted by Ministry of Defence [60] on Mon, 07/01/2013 - 18:22

We would recommend adding some explanatory text to the following sentence, lest it be misinterpreted as meaning that the public authority must positively facilitate the unauthorised use of third party intellectual property!  (The purpose of this provision is, of course, to facilitate the re-use of the information once the required third party permission has been obtained).

Even when the public authority is not able to license re-use, it must still provide the dataset in a re-usable format... 

This leads us on to a more serious point: the Code might well put a duty on public authorities to supply datasets in electronic format: however the user will not necesarily be able to lawfully view the data in that electronic file (let alone put the data to use) if it contains third party material. This is because, by viewing data that has been recorded in electronic format, the information is temporarily stored in the memory of the user's computer, which is an act restricted by copyright.

 Flag as offensive [65] 

Authorities should consider how best to streamline the process of ascertaining the ownership of copyright and database rights in the dataset, and where relevant obtaining authority to license the dataset, ideally before any requests arrive. Identification and acknowledgement of third party rights is good practice and may prevent unnecessary applications and delay in responding to requests.

  • Log in to add reply [66]
[60]

Obtaining Authority

Posted by Ministry of Defence [60] on Tue, 08/01/2013 - 10:52

Beyond our general comments (see below) relating to extent that this Code should be addressing datasets that fall outside the scope of section 11A, we are concerned about the wording of paragraph 4. The provisions relating to "obtaining authority" could be read as meaning that public authorities should have a process in place for obtaining authority to license a dataset if so requested. To do so goes far beyond any obligation hitherto placed on public authorities, and risks being extremely burdensome. Ordinarily, the extent to which an authority has the power to permit the re-use of third party information will have been agreed contractually when the dataset was first commissioned: re-users cannot expect public authorities to go back to the data owners in order to renegotiate such agreements.

 Flag as offensive [67] 

Licensing

If the dataset that is being provided, or any part of it, is a relevant copyright work, the public authority must make that work available for re-use in accordance with the terms of one of the specified licences in this Code. Authorities are encouraged to use the UK Open Government Licence as most datasets can be re-used without a charge. It is envisaged that the other licences will only be used in exceptional circumstances.

  • Log in to add reply [68]
[60]

Crown-Owned Works

Posted by Ministry of Defence [60] on Tue, 08/01/2013 - 10:45

We believe that this section of the Code should be clearer in explaining that the provisions relating to reuse and charging do not apply to Crown-owned copyright works or Crown-owned database rights, per section 11A(8) FOIA 2000.

 Flag as offensive [69] 
[60]

Custom Licences

Posted by Ministry of Defence [60] on Tue, 08/01/2013 - 11:03

This wording "the public authority must make that work available for re-use in accordance with the terms of one of the specified licences in this Code" could be unduely onerous on public authorities who hitherto have enjoyed a wider freedom to draft terms and conditions tailored to the nature of the data that they are licensing. For example, when licensing a dataset, the public authority would generally want a custom set of indemnity and limitation clauses included in the licence contract in order to precisely define the extent of its responsibilities and liabilities should there be a problem with the data.

 Flag as offensive [70] 
[40]

Resources to provide information

Posted by Alex_Hodge [40] on Thu, 10/01/2013 - 14:04

In providing an open government license the Council will not be benefit financially from providing the information. It is recommended that the licence provided is one which the Council will benefit from providing the information. 

Further, the additional requirements proposed in the code will place a greater burden on the Council’s resources to make information available at a time when the Council is facing further significant cuts to its budget. The recently announced Local Government Finance Settlement will see the Council’s budget reduce by approximately £37 million over the next 3 years and this is on top of significant cuts already made to Council funding over the previous 3 financial years.

 Flag as offensive [71] 

UK Open Government Licence: The Open Government Licence is the main licensing model for the UK Government. Established under the UK Government Licensing Framework, the model encourages the use and re-use of a wide range of public sector information. The Open Government Licence is a non-transactional open licence which enables use and re-use with virtually no restrictions. It permits use and re-use, including for commercial purposes, at no cost to the user/re-user. The Licence can be easily used by public authorities, for example, it only requires public authorities to link to the Open Government Licence which is hosted on The National Archives website [72].

  • Log in to add reply [73]

Non- Commercial Government Licence: It is recognised, however, that the Open Government Licence will not be appropriate in all cases, for example, in circumstances where information may only be used for non-commercial purposes. The Non-Commercial Government Licence was developed to meet those situations. As with the Open Government Licence, public authorities can link to the Non-Commercial Government Licence on The National Archives website [74].

  • Log in to add reply [75]

Charged Licence (Beta): If re-use for commercial purposes which involves payment of a fee and/or royalties by the re-user is required, a transactional licence may be used. The licence uses standard licensing terms and forms part of the UK Government Licensing Framework and is available on the National Archives website [76]. [Note: The Charged Licence is currently in ‘beta’ form and the National Archives is open to receiving feedback about the licence. Specific comments on this beta licence should be made through the National Archives website [76] although this draft Code of Practice consultation welcomes general feedback on use of this licence in the final code.]

  • Log in to add reply [77]

Costs and fees

It is important to distinguish between the costs to the public authority of complying with section 1(1) for a request for a dataset, the cost of providing it in a re-usable format under section 11(1A), and the fees that can be charged to the applicant for making a dataset (where it is also a relevant copyright work) available for re-use under section 11A.

  • Log in to add reply [78]

Fees Regulations for access made under sections 9, 12 and 13 of the Act apply to the right of access to datasets as to other information. The activities for which a fee may be charged (under Regulation 6) include, if such a preference is expressed by the applicant, provision of a dataset on portable media and posting the dataset on a host facility, which might be the authority’s own website or through a third party provider.

  • Log in to add reply [79]
[29]

Doesn't this suggest a fee

Posted by philipjohn [29] on Tue, 27/11/2012 - 21:36

Doesn't this suggest a fee would be chargeable for asking the authority to host it on their own website? If so, that seems odd. Perhaps it's an acknowledgement that some authorities will be charged by their IT provider? If that's the case the cost should be absorbed by the authority - the requester should not be punished because the authority failed to choose an IT provider that doesn't have an archaic business model that charges for simple website modifications. There is a greater benefit in showing up such ridiculous charging regimes by forcing the authority to suffer for agreeing to it. Tough love, you might say.

 Flag as offensive [80] 
[81]

Disclosure Log

Posted by GKemp [81] on Wed, 28/11/2012 - 17:01

Some authorities already have a disclosure log up and running. Is this section suggesting that those authorities are now going to have to start charging to put information up on their websites? This seems strange seeing as we have been doing it for several years now and not taking any payment.

 Flag as offensive [82] 
[15]

"a fee may be charged" "may

Posted by Rick Mason [15] on Wed, 19/12/2012 - 13:45

"a fee may be charged"

"may be" means it's an option, not a requirement

 Flag as offensive [83] 

Cost of complying with the request

A request for a dataset should initially be treated in the same way as a request for any information under the Act. Under section 12(1) of the Act, a public authority is not obliged to comply with section 1(1), i.e. inform the applicant whether it holds the dataset and, if so, to communicate the dataset, if it estimates that the cost of doing so would exceed the ‘appropriate limit’ as defined in the Fees Regulations for access. The fees the public authority can charge the requester for providing the information are set out in these Regulations.

  • Log in to add reply [84]

Cost of providing the dataset in a reusable format

If the cost of complying with the request would not exceed the appropriate limit and the information is not otherwise exempt, the public authority must provide the dataset (subject to any right to charge a fee). If the requestor expresses a preference for the dataset in electronic form, the public authority must provide it in a reusable format, so far as reasonably practicable. In deciding whether it would be reasonably practicable to provide the dataset in a reusable format, the public authority can take account of all the circumstances of the case, including the costs of doing so. These costs may include, for example, the cost of converting the dataset from a proprietary format to a format such as CSV. If the cost of using an external contractor is taken into account such that it is considered not reasonably practicable to provide the dataset in a re-usable format, the need to use that contractor and the cost of doing so must be justifiable. The Act does not prescribe any cost limit for determining what is reasonably practicable. The size and the resources of the public authority may be relevant here. If the public authority concludes that, in all the circumstances of the case, it would not be reasonably practicable to provide the dataset in a reusable format, then the authority must still provide the dataset in another format (again subject to the appropriate limit and/or any right to charge a fee).

  • Log in to add reply [85]
[23]

License even when dataset not provided

Posted by TimDavies [23] on Mon, 03/12/2012 - 19:12

Even when an authority judges that a dataset cannot cost effectively be provided they should still be asked to apply an appropriate license to the non-machine readable release that they provide.

This will ensure third parties are not restricted in then turning the non-machine readable product into a machine readable product following it's publication. 

 Flag as offensive [86] 
[23]

Encouraging open data engagement

Posted by TimDavies [23] on Mon, 03/12/2012 - 19:12

The guidance may also want to encourage authorities to actively engage with re-users in working out the appropriate format for the data, and managing the costs associated with providing machine readable data: for example, consultants may charge a much higher price for something a civic hacktivist would be willing to do for no cost; or parties requesting data may be willing to provide advice and support to the authority on extracting data in an appropriate way. The guidance may not be the only place to do this - but encouraging authorities to explore collaborative, rather than antagonistic relationships, with data requesters where possible would be good. 

 Flag as offensive [87] 
[23]

Contractor costs

Posted by TimDavies [23] on Mon, 03/12/2012 - 19:14

The guidance could explicitly ask agencies to, where refusing to provide a machine readable dataset on grounds of cost, to provide details of the hourly or daily rate of the contractor and anticipated time that has led to the cost exceeding the threshold. 

This is information that, if the request was under the threshold, may be published through the public spending open data requirements, or that may be FOIable independently, and so there should be no reason for this not to be explicitly included in any refusal response to a request for machine readable data. 

 Flag as offensive [88] 
[15]

When refusing on the grounds

Posted by Rick Mason [15] on Wed, 19/12/2012 - 13:49

When refusing on the grounds of cost the costs should be stated, and there could be the option for the requester to fund either the excess above the threshold or the full cost.

 Flag as offensive [89] 
[90]

When data is released to an individual what happens to the d

Posted by lemons11 [90] on Fri, 28/12/2012 - 15:40

What happens to the data set when it is released to person A?  I haven't seen anything that tells you what to do next.  I would have thought that organisations should be then publicising the data on their own website, data.gov.uk etc, so that other people are aware the data set exists and is in the public domain to be used - This in my opinion would be good practice, but we all know good practice isn't always implemented.  I'm also assuming some sort of retent and disposal schedules would need to be applied to the data sets.

This can probably be ignored now as the next part of the consultation covers this comment.

 Flag as offensive [91] 
[42]

Suggest removing the phrase "proprietary format"

Posted by Owen Boswarva [42] on Thu, 10/01/2013 - 15:52

I would suggest removing the phrase "proprietary format". I think it is being used here as equivalent to a format that does not support re-use. However there are some file formats that remain technically proprietary but are generally considered to support re-use, because the IP owners have undertaken not to assert rights that would limit their wide use. See for example the Microsoft Open Specification Promise [92], which applies to the .xls file format.

 Flag as offensive [93] 

Fees for providing the information

Fees for providing a dataset, as for any other information, to an applicant may only be charged in accordance with sections 9 and 13 of the Act and the Fees Regulations for access.

  • Log in to add reply [94]

Fees for allowing re-use of a relevant copyright work

In exceptional cases a public authority that is the owner of a copyright work in a dataset being released may exercise the power to charge a fee for re-use of that dataset.

  • Log in to add reply [95]

Section 11B of the Act provides that the Secretary of State may make regulations about the fees for making relevant copyright works available for re-use; public authorities can charge a fee, in accordance with any regulations under section 11B, for making that copyright work available for re-use. Alternatively, if a public authority is entitled to charge a fee under any other legislation for the re-use of a relevant copyright work, then it may do so on that basis instead. [Note: Guidance will be provided here once the regulations have been drafted and approved]

  • Log in to add reply [96]

Considering publication of datasets as part of a publication scheme

Public authorities are encouraged to subject existing and newly created datasets to the same tests that would apply when considering a request for release of the dataset. If the dataset would be released on request, the public authority should consider publishing it through the authority’s publication scheme. The Information Commissioner’s Office produces guidance on publication schemes for public authorities.

  • Log in to add reply [97]
[90]

publication scheme

Posted by lemons11 [90] on Fri, 28/12/2012 - 15:34

I think this should go further than encouragement, it needs to be more mandatory.

 Flag as offensive [98] 

Public authorities should consider their long term plans and processes for the collection and storage of datasets, keeping in mind that they should be made easily accessible and in a re-usable format for requests or publication as part of their publication scheme as well as for normal business purposes. Maintaining inventories of datasets can contribute to better management of datasets as well as to compliance with the Act.

  • Log in to add reply [99]

When publishing a dataset on their website, public authorities, should, where possible, publish it in a machine reachable format, so that the data can be directly downloaded from a given URL without further human intervention. Data should not be hidden behind a login, drop down menu or pick list.

  • Log in to add reply [100]
[29]

"If a dataset has been

Posted by philipjohn [29] on Tue, 27/11/2012 - 21:40

"If a dataset has been requested from a public authority under the Act, then the authority must publish that dataset in accordance with its publication scheme unless the authority is satisfied that it would not be appropriate to publish it. It may not be appropriate to publish it if, for example, the dataset is exempt from disclosure under one of the exemptions in the Act or if there is unlikely to be general interest in the dataset. If the authority holds an updated version of the dataset it must also publish that updated version, unless it is satisfied that it is not appropriate to do so."

Should they be encouraged to publish to data.gov.uk as well/instead of their own site?

 Flag as offensive [101] 

Authorities whose websites are in scope for archiving by The National Archives should first check that the data has been captured and can be downloaded from the UK Government Web Archive before removing the data from their own websites. Following this practice will avoid relevant authorities’ websites from becoming cluttered with out of date data, whist still keeping such data available.

  • Log in to add reply [102]
[15]

Should this apply to county

Posted by Rick Mason [15] on Wed, 19/12/2012 - 13:53

Should this apply to county records offices too?

 Flag as offensive [103] 

If a dataset has been requested from a public authority under the Act, then the authority must publish that dataset in accordance with its publication scheme unless the authority is satisfied that it would not be appropriate to publish it. It may not be appropriate to publish it if, for example, the dataset is exempt from disclosure under one of the exemptions in the Act or if there is unlikely to be general interest in the dataset. If the authority holds an updated version of the dataset it must also publish that updated version, unless it is satisfied that it is not appropriate to do so.

  • Log in to add reply [104]

Furthermore, when the authority publishes the dataset under its publication scheme, it must (as for responding to a request) provide it in an electronic form that is capable of re-use, where it is reasonably practicable to do so. What is reasonably practicable will again depend on the circumstances in each case and include the same considerations when dealing with a request, e.g. the cost of doing so, the work involved in doing any conversion and whether any specialist equipment or software is required.

  • Log in to add reply [105]
[23]

Is there a need for clarity

Posted by TimDavies [23] on Mon, 03/12/2012 - 19:50

Is there a need for clarity that, when a dataset is published in non-machine readable format through a publication scheme, a requester is within their rights to ask for this in a machine readable format, and the prior presence of this document in non-machine format in the publication scheme is not a reason to refuse or close the request? 

Should authorities be encouraged to provide means for users to discuss the formats they would like to see currently non-machine readable data in, to help the authority set priorities for reasonably practicable future publication of datasets.

 Flag as offensive [106] 

Advice and assistance to persons making or intending to make requests for datasets

Public authorities are required to provide advice and assistance to people who have made, or who propose to make, requests for datasets just as they would for any other information. This is under section 16 of the Act (a public authority’s duty to provide advice and assistance to applicants and potential applicants).

  • Log in to add reply [107]

As with FOI requests for any information, applicants should provide a sufficient description of the dataset sought for the public authority to be able to identify and locate it. Public authorities should provide assistance to the applicant that will help him or her describe it more clearly. This assistance could be in the form of published inventories of datasets held by the public authority, with details of their availability, and also provision of ad hoc help.

  • Log in to add reply [108]
[35]

Derivable datasets

Posted by PeteThomson [35] on Thu, 06/12/2012 - 09:03

If an applicant requests a dataset which doesn't exist as such, but could be derived from datasets which are available, how much help is the authority required to give? Should they:

  1. deny the request because the dataset requested doesn't exist
  2. say that dataset doesn't exist but suggest other existing datasets which might be relevant
  3. identify specifically which existing datasets could be used to derive the one requested
  4. explain how to derive the one requested from the existing datasets
  5. derive the requested dataset and provide it to the applicant?
 Flag as offensive [109] 

Where specialist software is required to access and/or re-use certain datasets, authorities should advise applicants where they can obtain such software. However, care should be taken not to unnecessarily endorse any particular manufacturer’s product.

  • Log in to add reply [110]
[35]

More open formats should be preferred

Posted by PeteThomson [35] on Thu, 06/12/2012 - 08:58

A need for specialist software may be unavoidable in a few cases, but shouldn't the guidance recommend avoiding it wherever possible? Usually it will be possible to extract the data into a non-proprietary format, and this is more open. Also, advising people where to find software that can read a particular specialist format, without unnecessarily endorsing a particular product, might require a knowledge of the software market that authorities won't always have.

 Flag as offensive [111] 

Public authorities should make it clear if any copyright or database rights in a dataset are owned by a third party and, if so, the identity of that third party. This will alert potential re-users of the limitation on re-use and the need to contact the rights owner to seek permission to re-use the dataset.

  • Log in to add reply [112]

Complaints

The redress mechanisms of the Freedom of Information Act apply for datasets just as for any other information; and the Information Commissioner’s functions under Part IV apply in the same way. The Information Commissioner will have the jurisdiction to consider any complaints in respect of datasets, including any complaint in respect of the re-use duty.

  • Log in to add reply [113]
[42]

Mention OPSI also?

Posted by Owen Boswarva [42] on Thu, 10/01/2013 - 15:57

On the assumption that the Information Commissioner will not be taking over all of the responsibilities of the OPSI, the Code should also require public authorities to make applicants aware of the availability of the OPSI complaints process in respect of PSI re-use -- particularly where the public authority has charged for re-use of data.

 Flag as offensive [114] 

Source URL: https://data.gov.uk/consultation/code-of-practice

Links
[1] https://data.gov.uk/user/login?destination=reply/add/475/30/field/field_paragraph#reply-add-form
[2] https://data.gov.uk/users/johncrab
[3] https://data.gov.uk/flag/flag/spam_reply/609?destination=print/book/export/html/474&amp;token=debb7f7681deb896af0bc27b7c41ab8b
[4] https://data.gov.uk/user/login?destination=reply/add/475/30/field/field_paragraph/1#reply-add-form
[5] https://data.gov.uk/user/login?destination=reply/add/475/30/field/field_paragraph/2#reply-add-form
[6] https://data.gov.uk/users/marionoswald
[7] https://data.gov.uk/flag/flag/spam_reply/621?destination=print/book/export/html/474&amp;token=c80199d0e9ca7acce915fd8f9c80f06c
[8] https://data.gov.uk/user/login?destination=reply/add/475/30/field/field_paragraph/3#reply-add-form
[9] https://data.gov.uk/flag/flag/spam_reply/622?destination=print/book/export/html/474&amp;token=6ba96b7560746745f384f83f52bfe1d9
[10] https://data.gov.uk/user/login?destination=reply/add/475/30/field/field_paragraph/4#reply-add-form
[11] https://data.gov.uk/user/login?destination=reply/add/475/30/field/field_paragraph/5#reply-add-form
[12] https://data.gov.uk/user/login?destination=reply/add/476/30/field/field_paragraph#reply-add-form
[13] https://data.gov.uk/user/login?destination=reply/add/476/30/field/field_paragraph/1#reply-add-form
[14] https://data.gov.uk/flag/flag/spam_reply/610?destination=print/book/export/html/474&amp;token=ad9fd855b57bb97eaa47f50326413177
[15] https://data.gov.uk/users/rick-mason
[16] https://data.gov.uk/flag/flag/spam_reply/612?destination=print/book/export/html/474&amp;token=e08084ead816447afc2152a8c5a3d6bd
[17] https://data.gov.uk/users/iru
[18] https://data.gov.uk/flag/flag/spam_reply/630?destination=print/book/export/html/474&amp;token=84bbf5afb414f7931d7a010f52e2c2b7
[19] https://data.gov.uk/user/login?destination=reply/add/476/30/field/field_paragraph/2#reply-add-form
[20] https://data.gov.uk/user/login?destination=reply/add/476/30/field/field_paragraph/3#reply-add-form
[21] https://data.gov.uk/user/login?destination=reply/add/476/30/field/field_paragraph/4#reply-add-form
[22] https://data.gov.uk/user/login?destination=reply/add/476/30/field/field_paragraph/5#reply-add-form
[23] https://data.gov.uk/users/timdavies
[24] https://data.gov.uk/flag/flag/spam_reply/599?destination=print/book/export/html/474&amp;token=39c8a24e06b304d8d5049b328873078d
[25] https://data.gov.uk/flag/flag/spam_reply/623?destination=print/book/export/html/474&amp;token=c58bd7fb71c5800363a93250125401d8
[26] https://data.gov.uk/user/login?destination=reply/add/476/30/field/field_paragraph/6#reply-add-form
[27] https://data.gov.uk/user/login?destination=reply/add/476/30/field/field_paragraph/7#reply-add-form
[28] https://data.gov.uk/user/login?destination=reply/add/477/30/field/field_paragraph#reply-add-form
[29] https://data.gov.uk/users/473570952
[30] https://data.gov.uk/flag/flag/spam_reply/591?destination=print/book/export/html/474&amp;token=574eed294fb3464d44d2c913b1c525ae
[31] https://data.gov.uk/flag/flag/spam_reply/600?destination=print/book/export/html/474&amp;token=a9079aaf4b1c2f8efafe47a3a1cef110
[32] http://www.opendataimpacts.net/2012/11/more-than-csv/
[33] http://blog.ouseful.info/2012/11/27/when-machine-readable-data-still-causes-issues-wrangling-dates/
[34] https://data.gov.uk/flag/flag/spam_reply/603?destination=print/book/export/html/474&amp;token=3cecb69c7af937c13a8da8356813eddb
[35] https://data.gov.uk/users/petethomson
[36] https://data.gov.uk/flag/flag/spam_reply/605?destination=print/book/export/html/474&amp;token=f8dd7afeab2ea43f2c769e6b13064e77
[37] https://data.gov.uk/users/john-kaye
[38] https://data.gov.uk/flag/flag/spam_reply/619?destination=print/book/export/html/474&amp;token=706405e7d0cab592eb0aac152ff0c236
[39] https://data.gov.uk/flag/flag/spam_reply/620?destination=print/book/export/html/474&amp;token=b0d31c4bc84b43c71db5df6920149456
[40] https://data.gov.uk/users/alex_hodge
[41] https://data.gov.uk/flag/flag/spam_reply/633?destination=print/book/export/html/474&amp;token=c2c5f8b3c16566ee1bc84709182c579f
[42] https://data.gov.uk/users/owen-boswarva
[43] https://data.gov.uk/flag/flag/spam_reply/635?destination=print/book/export/html/474&amp;token=392ea488494c0a944d58b4c665644064
[44] https://data.gov.uk/user/login?destination=reply/add/477/30/field/field_paragraph/1#reply-add-form
[45] https://data.gov.uk/flag/flag/spam_reply/601?destination=print/book/export/html/474&amp;token=623ce322a5dabc9857f645e586d5db99
[46] https://data.gov.uk/user/login?destination=reply/add/477/30/field/field_paragraph/2#reply-add-form
[47] http://www.ico.gov.uk/news/latest_news/2012/new-anonymisation-code-sets-out-how-to-manage-privacy-risks-and-maintain-transparency-20112012.aspx
[48] https://data.gov.uk/flag/flag/spam_reply/604?destination=print/book/export/html/474&amp;token=3edc013b01f195f5c532ff92093ce2d6
[49] https://data.gov.uk/library/public-data-principles
[50] https://data.gov.uk/user/login?destination=reply/add/478/30/field/field_paragraph#reply-add-form
[51] http://www.w3.org/DesignIssues/LinkedData.html
[52] https://data.gov.uk/user/login?destination=reply/add/478/30/field/field_paragraph/1#reply-add-form
[53] http://5stardata.info/
[54] https://data.gov.uk/flag/flag/spam_reply/636?destination=print/book/export/html/474&amp;token=7853d76ba721abef889db439faf97e3c
[55] https://data.gov.uk/user/login?destination=reply/add/478/30/field/field_paragraph/2#reply-add-form
[56] https://data.gov.uk/flag/flag/spam_reply/637?destination=print/book/export/html/474&amp;token=88f5200d979b5ac5f2a16feaf6755834
[57] https://data.gov.uk/user/login?destination=reply/add/478/30/field/field_paragraph/3#reply-add-form
[58] https://data.gov.uk/user/login?destination=reply/add/479/30/field/field_paragraph#reply-add-form
[59] https://data.gov.uk/user/login?destination=reply/add/479/30/field/field_paragraph/1#reply-add-form
[60] https://data.gov.uk/users/ministry-of-defence
[61] https://data.gov.uk/flag/flag/spam_reply/625?destination=print/book/export/html/474&amp;token=4f859ff492aaa6cc5bc09662e4ed48da
[62] https://data.gov.uk/user/login?destination=reply/add/479/30/field/field_paragraph/2#reply-add-form
[63] https://data.gov.uk/flag/flag/spam_reply/592?destination=print/book/export/html/474&amp;token=5fe83ac0d7487dc6e09cf7db1beea0f9
[64] https://data.gov.uk/flag/flag/spam_reply/624?destination=print/book/export/html/474&amp;token=f05fe7371fefab5d73756a103ef3722b
[65] https://data.gov.uk/flag/flag/spam_reply/626?destination=print/book/export/html/474&amp;token=7b14127a2c3da1bbf309430b92892715
[66] https://data.gov.uk/user/login?destination=reply/add/479/30/field/field_paragraph/3#reply-add-form
[67] https://data.gov.uk/flag/flag/spam_reply/628?destination=print/book/export/html/474&amp;token=c842a5719627188d51ead895e7e00442
[68] https://data.gov.uk/user/login?destination=reply/add/479/30/field/field_paragraph/4#reply-add-form
[69] https://data.gov.uk/flag/flag/spam_reply/627?destination=print/book/export/html/474&amp;token=325d3440b3ece4a28191c65e97ddafcc
[70] https://data.gov.uk/flag/flag/spam_reply/629?destination=print/book/export/html/474&amp;token=eb1e895cac2618199b9fbeb1a89a9794
[71] https://data.gov.uk/flag/flag/spam_reply/634?destination=print/book/export/html/474&amp;token=2e6a0a189829109a72a24fea3493de88
[72] http://www.nationalarchives.gov.uk/doc/open-government-licence
[73] https://data.gov.uk/user/login?destination=reply/add/479/30/field/field_paragraph/5#reply-add-form
[74] http://www.nationalarchives.gov.uk/doc/non-commercial-government-licence
[75] https://data.gov.uk/user/login?destination=reply/add/479/30/field/field_paragraph/6#reply-add-form
[76] http://www.nationalarchives.gov.uk/information-management/government-licensing/charged-licence.htm
[77] https://data.gov.uk/user/login?destination=reply/add/479/30/field/field_paragraph/7#reply-add-form
[78] https://data.gov.uk/user/login?destination=reply/add/480/30/field/field_paragraph#reply-add-form
[79] https://data.gov.uk/user/login?destination=reply/add/480/30/field/field_paragraph/1#reply-add-form
[80] https://data.gov.uk/flag/flag/spam_reply/593?destination=print/book/export/html/474&amp;token=29b5e09c5607966c5fc248b3061b8941
[81] https://data.gov.uk/users/gkemp
[82] https://data.gov.uk/flag/flag/spam_reply/595?destination=print/book/export/html/474&amp;token=1f2652bf5ddbd88d3012fc7b99e6e6ec
[83] https://data.gov.uk/flag/flag/spam_reply/613?destination=print/book/export/html/474&amp;token=79a93f628f69d2958b47df1b94835dba
[84] https://data.gov.uk/user/login?destination=reply/add/480/30/field/field_paragraph/2#reply-add-form
[85] https://data.gov.uk/user/login?destination=reply/add/480/30/field/field_paragraph/3#reply-add-form
[86] https://data.gov.uk/flag/flag/spam_reply/596?destination=print/book/export/html/474&amp;token=d86888905c38e173f3dc85df26627127
[87] https://data.gov.uk/flag/flag/spam_reply/597?destination=print/book/export/html/474&amp;token=cd538ce08944f337032ce8c2192040f3
[88] https://data.gov.uk/flag/flag/spam_reply/598?destination=print/book/export/html/474&amp;token=00259456c026792e7c9e798ea368ae82
[89] https://data.gov.uk/flag/flag/spam_reply/614?destination=print/book/export/html/474&amp;token=5029752f51a6a44722fd15d5b52cd1f5
[90] https://data.gov.uk/users/lemons11
[91] https://data.gov.uk/flag/flag/spam_reply/617?destination=print/book/export/html/474&amp;token=903d11d454326e55c48ed254b447dd62
[92] http://en.wikipedia.org/wiki/Microsoft_Open_Specification_Promise
[93] https://data.gov.uk/flag/flag/spam_reply/638?destination=print/book/export/html/474&amp;token=90aa56a1322e9ea3a888982d1c76a606
[94] https://data.gov.uk/user/login?destination=reply/add/480/30/field/field_paragraph/4#reply-add-form
[95] https://data.gov.uk/user/login?destination=reply/add/480/30/field/field_paragraph/5#reply-add-form
[96] https://data.gov.uk/user/login?destination=reply/add/480/30/field/field_paragraph/6#reply-add-form
[97] https://data.gov.uk/user/login?destination=reply/add/481/30/field/field_paragraph#reply-add-form
[98] https://data.gov.uk/flag/flag/spam_reply/616?destination=print/book/export/html/474&amp;token=68c578abd82a4abfe2605ebff70e1a7f
[99] https://data.gov.uk/user/login?destination=reply/add/481/30/field/field_paragraph/1#reply-add-form
[100] https://data.gov.uk/user/login?destination=reply/add/481/30/field/field_paragraph/2#reply-add-form
[101] https://data.gov.uk/flag/flag/spam_reply/594?destination=print/book/export/html/474&amp;token=d54fad8ce470c4b71e893dfbbdc587a1
[102] https://data.gov.uk/user/login?destination=reply/add/481/30/field/field_paragraph/3#reply-add-form
[103] https://data.gov.uk/flag/flag/spam_reply/615?destination=print/book/export/html/474&amp;token=ad899d918649521cb1fb81d3ae659640
[104] https://data.gov.uk/user/login?destination=reply/add/481/30/field/field_paragraph/4#reply-add-form
[105] https://data.gov.uk/user/login?destination=reply/add/481/30/field/field_paragraph/5#reply-add-form
[106] https://data.gov.uk/flag/flag/spam_reply/602?destination=print/book/export/html/474&amp;token=124517ad973275c5b3e905b7535c04f9
[107] https://data.gov.uk/user/login?destination=reply/add/482/30/field/field_paragraph#reply-add-form
[108] https://data.gov.uk/user/login?destination=reply/add/482/30/field/field_paragraph/1#reply-add-form
[109] https://data.gov.uk/flag/flag/spam_reply/607?destination=print/book/export/html/474&amp;token=020a039dc4617d795f5d17da53f3a2ff
[110] https://data.gov.uk/user/login?destination=reply/add/482/30/field/field_paragraph/2#reply-add-form
[111] https://data.gov.uk/flag/flag/spam_reply/606?destination=print/book/export/html/474&amp;token=f7eb792dc7d4803882922e7a9b1a552a
[112] https://data.gov.uk/user/login?destination=reply/add/482/30/field/field_paragraph/3#reply-add-form
[113] https://data.gov.uk/user/login?destination=reply/add/483/30/field/field_paragraph#reply-add-form
[114] https://data.gov.uk/flag/flag/spam_reply/639?destination=print/book/export/html/474&amp;token=5e701aa9f684a4364e260c9463a5efba