{"action":"opened","issue":{"url":"https://api.github.com/repos/BetaNYC/civic.json/issues/21","labels_url":"https://api.github.com/repos/BetaNYC/civic.json/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/BetaNYC/civic.json/issues/21/comments","events_url":"https://api.github.com/repos/BetaNYC/civic.json/issues/21/events","html_url":"https://github.com/BetaNYC/civic.json/issues/21","id":128038503,"number":21,"title":"Updating civic.json to be more widely usable","user":{"login":"emanuelfeld","id":4269640,"avatar_url":"https://avatars.githubusercontent.com/u/4269640?v=3","gravatar_id":"","url":"https://api.github.com/users/emanuelfeld","html_url":"https://github.com/emanuelfeld","followers_url":"https://api.github.com/users/emanuelfeld/followers","following_url":"https://api.github.com/users/emanuelfeld/following{/other_user}","gists_url":"https://api.github.com/users/emanuelfeld/gists{/gist_id}","starred_url":"https://api.github.com/users/emanuelfeld/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/emanuelfeld/subscriptions","organizations_url":"https://api.github.com/users/emanuelfeld/orgs","repos_url":"https://api.github.com/users/emanuelfeld/repos","events_url":"https://api.github.com/users/emanuelfeld/events{/privacy}","received_events_url":"https://api.github.com/users/emanuelfeld/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-01-21T22:41:02Z","updated_at":"2016-01-21T22:41:02Z","closed_at":null,"body":"@stvnrlly (Code for DC co-captain) and I (civic tech fellow in DC government) have been working on an reworking of civic.json. The idea behind it is that existing spec is:\r\n\r\n1. Geared toward projects created outside of government  (politicalEntity is not the creator)\r\n2. Is not comprehensive enough that it could be hosted elsewhere (i.e. a registry) and made more easily discoverable\r\n3. Certain other fields, like license and repository, would help with reuse and are required in other package standards (e.g. package.json and setup.py)\r\n\r\nOur proposed schema is here: https://github.com/DCgov/civic.json/blob/master/schema.json\r\nWith a builder and validator here: http://open.dc.gov/civic.json/\r\n\r\nJSON files filled out according to this schema are backwards compatible with BetaNYC's civic.json standard in that all of your required fields are also required in all (with the same naming).\r\n\r\nI see #14 is still open, but wondering at your thoughts @chriswhong, @seanluciotolentino, and others on a PR?"}}