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
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)
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.
Words and expressions used in this Code have the same meaning as the same words and expressions used in the Act.
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.
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.
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.
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
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.
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
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.
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.
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.
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.
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).
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).
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.
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.
Public authorities should consider best practice and any guidance on the provisions of datasets issued by the Information Commissioner.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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].
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].
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.]
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.
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.
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.
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).
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.
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.
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]
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
Links
[1] https://data.gov.uk/user/login?destination=reply/add/475/30/field/field_paragraph#reply-add-form
[2] https://data.gov.uk/user/131301
[3] https://data.gov.uk/flag/flag/spam_reply/609?destination=print/book/export/html/474&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/user/136301
[7] https://data.gov.uk/flag/flag/spam_reply/621?destination=print/book/export/html/474&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&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&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&token=e08084ead816447afc2152a8c5a3d6bd
[17] https://data.gov.uk/user/136961
[18] https://data.gov.uk/flag/flag/spam_reply/630?destination=print/book/export/html/474&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/user/3455
[24] https://data.gov.uk/flag/flag/spam_reply/599?destination=print/book/export/html/474&token=39c8a24e06b304d8d5049b328873078d
[25] https://data.gov.uk/flag/flag/spam_reply/623?destination=print/book/export/html/474&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/user/187
[30] https://data.gov.uk/flag/flag/spam_reply/591?destination=print/book/export/html/474&token=574eed294fb3464d44d2c913b1c525ae
[31] https://data.gov.uk/flag/flag/spam_reply/600?destination=print/book/export/html/474&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&token=3cecb69c7af937c13a8da8356813eddb
[35] https://data.gov.uk/user/127531
[36] https://data.gov.uk/flag/flag/spam_reply/605?destination=print/book/export/html/474&token=f8dd7afeab2ea43f2c769e6b13064e77
[37] https://data.gov.uk/user/136251
[38] https://data.gov.uk/flag/flag/spam_reply/619?destination=print/book/export/html/474&token=706405e7d0cab592eb0aac152ff0c236
[39] https://data.gov.uk/flag/flag/spam_reply/620?destination=print/book/export/html/474&token=b0d31c4bc84b43c71db5df6920149456
[40] https://data.gov.uk/user/137831
[41] https://data.gov.uk/flag/flag/spam_reply/633?destination=print/book/export/html/474&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&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&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&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&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&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/user/136381
[61] https://data.gov.uk/flag/flag/spam_reply/625?destination=print/book/export/html/474&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&token=5fe83ac0d7487dc6e09cf7db1beea0f9
[64] https://data.gov.uk/flag/flag/spam_reply/624?destination=print/book/export/html/474&token=f05fe7371fefab5d73756a103ef3722b
[65] https://data.gov.uk/flag/flag/spam_reply/626?destination=print/book/export/html/474&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&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&token=325d3440b3ece4a28191c65e97ddafcc
[70] https://data.gov.uk/flag/flag/spam_reply/629?destination=print/book/export/html/474&token=eb1e895cac2618199b9fbeb1a89a9794
[71] https://data.gov.uk/flag/flag/spam_reply/634?destination=print/book/export/html/474&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&token=29b5e09c5607966c5fc248b3061b8941
[81] https://data.gov.uk/user/125831
[82] https://data.gov.uk/flag/flag/spam_reply/595?destination=print/book/export/html/474&token=1f2652bf5ddbd88d3012fc7b99e6e6ec
[83] https://data.gov.uk/flag/flag/spam_reply/613?destination=print/book/export/html/474&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&token=d86888905c38e173f3dc85df26627127
[87] https://data.gov.uk/flag/flag/spam_reply/597?destination=print/book/export/html/474&token=cd538ce08944f337032ce8c2192040f3
[88] https://data.gov.uk/flag/flag/spam_reply/598?destination=print/book/export/html/474&token=00259456c026792e7c9e798ea368ae82
[89] https://data.gov.uk/flag/flag/spam_reply/614?destination=print/book/export/html/474&token=5029752f51a6a44722fd15d5b52cd1f5
[90] https://data.gov.uk/user/124161
[91] https://data.gov.uk/flag/flag/spam_reply/617?destination=print/book/export/html/474&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&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&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&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&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&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&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&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&token=5e701aa9f684a4364e260c9463a5efba
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.