-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated README to reflect new project direction #5
base: master
Are you sure you want to change the base?
Conversation
👍 Thanks! Was just about to do a similar PR. 😺 |
have we come to a point where we have outlined the file standard? in the meantime, Civic.JSON describes what BetaNYC is using to power our projects.betaNYC.us. |
No, we need to start the convo by creating a few issues- Juan-Pablo Velez On Thu, Feb 20, 2014 at 2:44 PM, Noel Hidalgo [email protected]
|
@noneck -- The working version of the file standard that is being implemented in CfA's "civic-json-worker" cross-municipality app is outlined by @ondrae here: I do think Juan's pull request is on-point. My understanding was that this repo would be the place for discussion of the data standard, and that repo would be discussing implementation of an "aggregator" API. But if you're thinking this BetaNYC repo should preserve what yous guys are doing, we could potentially:
Bottom line, though, to me is that right now the proliferation of things here makes understanding the state of play kinda difficult. So if Juan's PR isn't cool at this point, I'd still minimally like to see a ref in the README pointing at CfA's civic-json-worker page as the place to contribute and hash out the inter-municipality data standard. |
Why is there a |
Dave, I'm sorry. Does that standard comply to schema.org standards? Maybe you can propose better language? N Sent from my TI–85
|
@noneck -- civic-json-worker isn't my project. Could you bring up this issue over on that repo if you think it merits changing the implementation? I opened an issue for that here: codeforamerica/cfapi#21 |
Commented on #6 to show an example with all of our various attributes included. Lets start pruning them down there. |
@jpmckinney, |
Update @jpvelez's patch to syntax-highlight JSON
Sorry to bump a dead issue, but is the format documented in the PR the recommended format for |
Hey @jszwedko. The most up to date civic.json stuff is either Code for DC's at http://open.dc.gov/civic.json/builder.html or Code for America's at https://github.com/codeforamerica/brigade/blob/master/README-Project-Search.md#civicjson. The Code for America Project Search uses the status and tags attributes from the civic.json. |
@ondrae thanks for the pointers 👏 |
No description provided.