Too many hard-working Virginians can’t seem to get ahead, despite working full-time. Turns out, there’s a reason for that.
Median wages in Virginia are actually lower now in real terms than they were five years ago, even as wages for those at the top have grown sharply. This means that even as a few Virginians get more and more, everyone else is left farther behind. One in five Virginia workers now makes less than $10.33. That’s less than $21,500 a year for someone working 40 hours a week, 52 weeks a year.
Virginia is now the most unequal state in the country, and is more unequal than at any time on record. As of 2015, high-wage Virginia workers are being paid 6.2 times what low-wage workers make per hour, and 2.8 times what typical Virginians make.
Everyone wants their children to do better than they did, yet when wages for most people are stagnant or even falling that becomes more and more difficult. Many of us are proud of the hard work that helped us climb the ladder of opportunity and provide a better life for our families, whether it’s our own work, our parents’, or our grandparents’ But it’s harder to climb that ladder when the rungs keep getting further apart or are actually missing altogether.
We need to make sure everyone can make ends meet – we’re all better off when all families are financially stable and secure. And, beyond that, access to the American dream – being able to get ahead through hard work and sacrifice – should be for everyone, not just a few who have gotten more and more of the rewards of economic growth in recent years.
We need to grow the economy, and in ways that benefit all of us, not just some.
According to the Open Definition, open data “must“ be available under an open licence.*
But what about datasets that are also effectively free to access and reuse because the producer does not assert any intellectual property rights over the data? Are those datasets “open data”, and if not why not?
An example: Companies House’s Free Company Data Product, which contains basic data about all live companies on the public register. This dataset is released monthly, but without licensing information.
I can confirm there are no restrictions on the use of the data provided within the Free Company Data Product … As public information, you are free to use it however you wish.
CH does not make public information, including the Free Data Product, available under the Open Government Licence (OGL)….
Most of the material on the companies register, with the exception of a small category of material which is exempt from statutory disclosure requirements, is “public information” that the Registrar of Companies is under a statutory obligation to make available to the public. Where information on the register is supplied by a company or someone acting on its behalf, any copyright in that information belongs to that company (or its agents). It does not belong to the Registrar. The Registrar supplies this third party copyright information to customers under authorities given to him under s47 and s50 of the Copyright, Designs and Patents Act 1988 and Schedule 1 of the Database Regulations (SI 1997/3032).
CH places no restriction on how the information is used, but advises all customers to take their own legal advice regarding possible breach of third party copyright.
A second example: data on business costs and expenses claimed by MPs, available as downloads from the IPSA website. Availability for reuse is covered by a single sentence in a FAQ document:
The information is released publicly and without restriction.
In both examples there is no specified licence. But does there need to be one?
The public domain
The Open Data Institute’s guide to open data goes somewhat further than the Open Definition, by saying that “without a licence, the data can’t be reused.”
Technically that statement is wrong. There is an alternative case: the data can be in the public domain, because IP rights do not apply or have expired or been forfeited.
In principle, if a dataset is in the public domain then reuse is unfettered. Even the few restrictions normally imposed by an open licence, such as the requirement to attribute the data to its source, do not apply.
But ‘public domain’ is a tricky concept. In the United States, where works of the federal government are excluded from copyright protection, this term has a recognised status in copyright law. However in the UK it is mainly a colloquialism. There is no statutory process for waiving IP rights and placing a work into the commons.
In practice, in order to reuse a dataset openly we either have to establish permission or establish that no permission is required. The usual approach is for the publisher to apply an open licence to the dataset. But in order to make data available under licence the publisher must actually believe they have IP rights in that data. Otherwise they have no standing to give anyone permission to use the data (or to restrict its use).
A licence provides clarity
The approach taken by Companies House and IPSA is unsatisfactory because it is ambiguous. On the face of it, blanket statements that the data may be used “without restriction” have the virtue of simplicity. But does that mean Companies House and IPSA have no IP claims on the data, or do those statements actually operative as ad hoc licences? It’s not clear.
Although the records of individual companies are third-party information, Companies House could assert database rights over the register of companies as a whole, and possibly also copyright over the system of uniform resource identifiers (URIs) assigned to each company. That would give CH the necessary IP ownership to apply the Open Government Licence to the Free Company Data Product.
The OGL does not override any other copyright or database right exceptions, so (as far as I can see) this approach would not conflict with the statutory status of the register of companies as a public register.
Another option is the Creative Commons Zero (CC0) licence, which is designed specifically for IP owners who want to dedicate copyrighted works as nearly as possible to the public domain.
This change of approach would provide greater clarity to reusers by bringing the CH and IPSA datasets into a recognised open data framework.
Where producers genuinely believe they cannot assert IP rights over the data they make public, but want to encourage open reuse, it would be good practice to provide as clear as possible a statement to that effect. This would give reusers an assurance that the data is okay to use (subject to due diligence on third party rights and other issues) and that the producer commits not to apply restrictions on reuse retroactively at a later date.
* Update 28 February 2016: the latest version of the Open Definition clarifies that open data may also be in the public domain, i.e. not subject to a licence.
An award-winning front-end framework for building websites that are accessible, usable, interoperable, mobile friendly and multilingual
A collection of flexible and themeable templates and reusable components
A collaborative open source project led by the Government of Canada
Resources for implementing accessibility are a huge benefit to developers, since they can demystify some of the more challenging aspects: how do I use ARIA correctly–do I really need to start with the ARIA spec?What does an accessible widget look like?Is there an example to help me get started?
This open source toolkit from the Government of Canada offers a robust set of features. Modern coded demos such as an accessible input date picker polyfill, charts, theme starters and plugins can help jump start your efforts (see the whole list). It also has multi-language support, something that is often forgotten as we develop for ourselves without realizing it.
There are mulitple reasons to participate in a project like the Web Experience Toolkit, but one of the most significant is that many people are testing and contributing back to the open source library, strengthening it as a collective group. You can benefit from this effort by utlizing the resources and also contribute back through testing, reporting issues, and submitting pull requests on Github. It’s a win-win for everyone.
In the last six months I was fortunate enough to be able to push forward one of my side projects, with the help of a prototype grant from the Knight Foundation. The mission of the project, is to help move forward existing open federal government data projects, by adopting them, and helping clean up the data, publish simple APIs, generate more meta data, while also telling stories around the project. Something I originally called Federal Agency Dataset Adoption, but then shortened to simply Adopta.Agency. When I was doing my final presentation in Pittsburgh last month, for the Knight Foundation, someone from the University of Miami was present, and when they got home, contacted me about helping move forward the database available at ClinicalTrials.gov. I do not know much about the data present in the collection, but immediately recognized it as a viable Adopta.Agency project. To summarize their request, it went something…
Responsive design is in. Everybody’s talking about it and diligently putting together responsive websites. Yet it’s no easy task to design and build good, fast, and flexible responsive pages. How do you achieve your goal faster? Which front-end techniques should you use to build flexible components? What design patterns should you use and how do you deal with complicated tables, maps, forms, and interactive elements? Vitaly Friedman, editor-in-chief of Smashing magazine, will present practical techniques and ideas developed in actual practice, and use many examples and pieces of code to illustrate more effective and efficient ways of RWD.
