New standard and platform for city maps

Maps are important for many users these days and a new open data standard and platform aims to bring all the street data together:

Using giant GIS databases, cities from Boston to San Diego maintain master street maps to guide their transportation and safety decisions. But there’s no standard format for that data. Where are the intersections? How long are the curbs? Where’s the median? It varies from city to city, and map to map.

That’s a problem as more private transportation services flood the roads. If a city needs to communicate street closures or parking regulations to Uber drivers, or Google Maps users, or new dockless bikesharing services—which all use proprietary digital maps of their own—any confusion could mean the difference between smooth traffic and carpocalypse.

And, perhaps more importantly, it goes the other way too: Cities struggle to obtain and translate the trip data they get from private companies (if they can get their hands on it, which isn’t always the case) when their map formats don’t match up.

A team of street design and transportation data experts believes it has a solution. On Thursday, the National Association of City Transportation Officials and the nonprofit Open Transport Partnership launched a new open data standard and digital platform for mapping and sharing city streets. It might sound wonky, but the implications are big: SharedStreets brings public agencies, private companies, and civic hackers onto the same page, with the collective goal of creating safer, more efficient, and democratic transportation networks.

It will be interesting whether this step forward simply makes what is currently happening easier to manage or whether this will be a catalyst for new opportunities. In a number of domains, having access to data is necessary before creative ideas and new collaborations can emerge.

This also highlights how more of our infrastructure is entering a digital realm. I assume there are at least a few people who are worried about this. For example, what happens if the computers go down or all the data is lost? Does the digital distance from physical realities – streets are tangible things, not just manipulable objects on a screen – remove us from authentic streetlife? Data like this may no be no substitute for a Jane Jacobs-esque immersion in vibrant blocks.

Secondary liability, approaching the limit

The Seattle Times reported a few weeks ago that Microsoft “is pushing Washington legislators to pass a law making it illegal for manufacturers that use pirated software to sell goods in the state”:

The proposed legislation would create a legal cause of action by making manufacturing companies liable for damages, and it would give the state attorney general and companies the right to pursue injunctions in civil court to stop the manufacturers’ goods from being sold.

For example, if a large Washington store sold T-shirts made from a company in China and the Chinese company uses pirated copies of Excel at an office in Shenzhen, Microsoft could seek an injunction to prevent the manufacturer from supplying T-shirts to be sold in Washington state.

This represents a sweeping change to current intellectual property law. It is one thing to grant monopolies via copyright for “limited Times” in order “To promote the Progress of Science and useful Arts”. It is another thing entirely to extend copyright’s monopoly over physical objects alleged to have been manufactured in another country with the help of pirated software and thus to hold the buyers of those physical objects legally responsible.

To put it concretely:  this isn’t holding the buyers of obviously stolen TV’s out of the back of a pickup truck legally responsible for their purchases.  This is holding GM, maker of that pickup truck, legally responsible because the Chinese manufacturer of one of the parts in the truck’s engine used a pirated copy of Microsoft Outlook to receive emailed purchase orders from GM.

Now that’s secondary liability.

Hat tip to Groklaw, where I ran across this story earlier today.  If you’d like to read more about this, Pamela Jones has written rather extensive commentary, including a hypothesis Microsoft is pushing for this and similar laws in other U.S. states in order to unleash a “litigation storm against Linux” — including derivatives like Android:

The law would make it possible for Microsoft to block Android sales in whatever state passed such laws if it could find some tie between the Android product and some manufacturer of a contracted part in China or wherever who happened to use a pirated version of Microsoft Word — not to make the part but to write up an ad for it. Ephemeral, much? But can you imagine how much litigation could spring from a law like this? How little it would take to keep litigation in the air forevermore? And you don’t have to even prove infringement in China, just allege it to initiate proceedings.

Of course, Jones is quick to note that the state of Washington’s “protections” do not extend to companies like Red Hat that profit from selling open source support and services.  Under the law, software companies with proprietary licenses like Microsoft

can sue in civil court and the Attorney General can go after the “wrongdoer” US company, if a notice is sent and no amelioration occurs. But if the violation is of an *open source license*, the victim can’t sue anyone under the bill, and the Attorney General does nothing for you. It’s an exception to the law.