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.
It is that way by design. It's difficult to control a law abiding populace, so pass enough laws to make everyone a criminal. Some one gets uppity or steps out of line, you've already got 'em.
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.