Skip to content

Instantly share code, notes, and snippets.

@drj11
Last active April 19, 2016 20:56
Show Gist options
  • Save drj11/d30f4c5a14e06dd8756145f192a064cc to your computer and use it in GitHub Desktop.
Save drj11/d30f4c5a14e06dd8756145f192a064cc to your computer and use it in GitHub Desktop.
Land Registry Consultation Response

consultation document https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/510987/BIS-16-165-consultation-on-moving-land-registry-operations-to-the-private-sector.pdf

the consultation makes references to "Autumn Statement" and "the Chancellor" (executive summary, para 2, page 5) without further explanation or reference to these documents and roles. That detracts from the clarity of the consultation document.

executive summary, para 3, page 5, asserts that the Land Registry underpins a valuable property market, without qualifying that by explaining that not all land (or even owned land) is in the registry.

execute summary para 4, page 5, use of "customer" unclear. Is it government (as the statutory customer of the outsourced register); is it currently fee-paying individuals (many of whom couldn't care less); or, we the people?

para 16 on copyright and ownership, this is useful background, but there are much more radical alternativesv possible.

para 18, 24e6 titles (=5e9 bytes at 200 bytes per title?)

para 23, government's open data agenda

para 26, going digital

para 29, weak at providing digital products (that could be provided by 3rd parties; given open data)

para 34, "believes" blah blah blah

para 39, "customer", again without explicitly saying who the customer is.

para 41 (and earler); re debt. I don't know if the government has noticed; but debt is really cheap at the moment.

para 41, clause 2. utter garbage; what went on there?

para 45, customers

para 51, privatise profit, bear the loss publicly

para 60, open open open

para 66, fee set by parliament; so only opportunity for private company to make profit is to cut corners.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment