Home

check-test-article

10 May 2016

First, without a data context you must define helpers for your data, which is a bit more verbose.

Second, this limits the reusability of templates. Data context is how you create reusable "components" in Blaze (whether you like it or not). Using the same template with a different data context allows you to use that template in different places in your app, being passed data and not hard-coding itself to things like the route.

First, without a data context you must define helpers for your data, which is a bit more verbose.

Second, this limits the reusability of templates. Data context is how you create reusable "components" in Blaze (whether you like it or not). Using the same template with a different data context allows you to use that template in different places in your app, being passed data and not hard-coding itself to things like the route.

First, without a data context you must define helpers for your data, which is a bit more verbose.

Second, this limits the reusability of templates. Data context is how you create reusable "components" in Blaze (whether you like it or not). Using the same template with a different data context allows you to use that template in different places in your app, being passed data and not hard-coding itself to things like the route.

First, without a data context you must define helpers for your data, which is a bit more verbose.

Second, this limits the reusability of templates. Data context is how you create reusable "components" in Blaze (whether you like it or not). Using the same template with a different data context allows you to use that template in different places in your app, being passed data and not hard-coding itself to things like the route.

First, without a data context you must define helpers for your data, which is a bit more verbose.

Second, this limits the reusability of templates. Data context is how you create reusable "components" in Blaze (whether you like it or not). Using the same template with a different data context allows you to use that template in different places in your app, being passed data and not hard-coding itself to things like the route.

First, without a data context you must define helpers for your data, which is a bit more verbose.

Second, this limits the reusability of templates. Data context is how you create reusable "components" in Blaze (whether you like it or not). Using the same template with a different data context allows you to use that template in different places in your app, being passed data and not hard-coding itself to things like the route.

First, without a data context you must define helpers for your data, which is a bit more verbose.

Second, this limits the reusability of templates. Data context is how you create reusable "components" in Blaze (whether you like it or not). Using the same template with a different data context allows you to use that template in different places in your app, being passed data and not hard-coding itself to things like the route.

First, without a data context you must define helpers for your data, which is a bit more verbose.

Second, this limits the reusability of templates. Data context is how you create reusable "components" in Blaze (whether you like it or not). Using the same template with a different data context allows you to use that template in different places in your app, being passed data and not hard-coding itself to things like the route.

First, without a data context you must define helpers for your data, which is a bit more verbose.

Second, this limits the reusability of templates. Data context is how you create reusable "components" in Blaze (whether you like it or not). Using the same template with a different data context allows you to use that template in different places in your app, being passed data and not hard-coding itself to things like the route.

Stop the secrecy: Publish the NHS COVID data deals

To: Matt Hancock, Secretary of State for Health and Social Care

We’re calling on you to immediately release details of the secret NHS data deals struck with private companies, to deliver the NHS COVID-19 datastore.

We, the public, deserve to know exactly how our personal information has been traded in this ‘unprecedented’ deal with US tech giants like Google, and firms linked to Donald Trump (Palantir) and Vote Leave (Faculty AI).

The COVID-19 datastore will hold private, personal information about every single one of us who relies on the NHS. We don’t want our personal data falling into the wrong hands.

And we don’t want private companies – many with poor reputations for protecting privacy – using it for their own commercial purposes, or to undermine the NHS.

The datastore could be an important tool in tackling the pandemic. But for it to be a success, the public has to be able to trust it.

Today, we urgently call on you to publish all the data-sharing agreements, data-impact assessments, and details of how the private companies stand to profit from their involvement.

The NHS is a precious public institution. Any involvement from private companies should be open to public scrutiny and debate. We need more transparency during this pandemic – not less.

By adding my name to this campaign, I authorise openDemocracy and Foxglove to keep me updated about their important work.

Comments

We encourage anyone to comment, please consult the oD commenting guidelines if you have any questions.

Creative Commons Attribution-NonCommercial 4.0

This article is published under a Creative Commons Attribution-NonCommercial 4.0 International licence. If you have any queries about republishing please contact us. Please check individual images for licensing details.