Don't Tie a Horse To a Tree and Other Open Data Lessons
itwbennett writes "Baltimore this week became the first city to hop on the open data bandwagon with the launch of the Baltimore Decoded website. The site makes the city's charter and codes more accessible to the public and will eventually include information on court decisions, legislative tracking and city technical standards (e.g., building regulations, zoning restrictions, fire codes). The site also offers a RESTful, JSON-based API for accessing the data. ITworld's Phil Johnson dug in and found these lesser-known Baltimore codes: You can't hold more than 1 yard sale every 6 months, you can't tie a horse to a tree, and you can't have fruit on a wharf. What you do with this information is up to you."
What kind of place is Baltimore if their "openness" doesn't allow horse/tree connectivity? I realize it's probably IP/patent related, but geez folks, can't we work this out?
XML may be an over engineered piece of crap, but while JSON isn't perfect, its pretty darn simple and "just works", with very few gotchas... REST is just "use http the way it was designed to be used and not one bit more".
Not too sure where the problem is.
Finally, A cit where you can figure out what it legal under the city's laws. Now only if you could access the county, state and federal regulations it might be possible to obey the millions of pages of laws that you are subject to. That would be nice, but under common law, you also need all the historical records! Some of those may or may not have existing documentation, and it may be privately held.
We have a legal system that accumulates laws. I'd prefer one that actively put in some re-factoring and simplification work instead of implicitly including all historical laws and decisions, overriding what is changed. How much law can we possible need? It has to be less that what we have.
Laws should be tracked, with dependencies, by an apt-like system. Anyone should be able to query what is illegal, without a lawyer. Automated systems can flag unfairness, conflicting laws, and obsolescence.
Lawyers and judges' jobs would be reduced to addressing bugs.
The whole lot should be committed to a git repository (git-blame anyone?). New laws should take the form of pull requests.
WTF? Maryland law (both statutes and COMAR) has been on-line for years.
And Baltimore City code has also been on-line for a while.
Maybe this is a nicer interface or something, but pretending that putting laws on-line is some kind of breakthrough is counterfactual.
Tom Swiss | the infamous tms | my blog
You cannot wash away blood with blood
If there were no limit on yard sales, then people could just set up a shop in a residential zone.
The ordinance does not preclude fruit from being on a wharf, just allocates the responsibility for its removal to the Harbour Master if it becomes a nuisance. Given the submission looks like a selfie for ITWorld I'm not surprised there was no fact check.
If a law isn't enforced in 10 years (maybe 20), it should automatically expire. If the city/county/state/federal government wants to keep an unenforced law on the books, it should have to be passed again like any other new law.
And I hate to be the bearer of bad news, but JSON isn't usually RESTful (there's no hypertext).
REST is a perfectly fine network architecture, it's designed to support forward-comparability and be self-documenting. But most people have no clue what it means.
Like Twitter. Their website is more RESTful than their so-called REST API, it's despicable.
Wonder what the public key field is for?
I know the phone companies don't like tethering, but this is ridiculous.
systemd is Roko's Basilisk.