<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="mid:4E55285D.7070704@obviously.com" type="cite">On
08/18/2011 03:23 AM, Jaak Laineste wrote:<br>
See <a href="http://wiki.openstreetmap.org/wiki/OpenMetaMap">http://wiki.openstreetmap.org/wiki/OpenMetaMap</a><br>
</blockquote>
<br>
When I look at statement "I put my dataset online using OpenMetaMap
API" I immediately react "why invent a new standard?". The linkable
datasets could have a variety of APIs drawn from existing standards
(e.g. shapefiles, kml, web feature servers (WFS)). You'll get a
more robust system if you leverage an existing feed rather than
requiring data providers to invent one just for osm.<br>
<br>
The proposal needs to address the end-user editing experience. When
user sees a feature on a map that is "wrong", how do they identify
where the data came from, and understand the chain of actions needed
to apply a correction? You're talking about rather major additions
to every single osm editing tool.<br>
<br>
-----<br>
<br>
I see the huge advantage of this approach is the licensing. As you
write "<i>OSM would not become derivate from any external databases,
only the rendering would be</i>". There are many many good
datasets that are free to use, but not compatible with OSM's
licenses.<br>
</body>
</html>