- From: Dirk Schulze <dirk@dschulze.com>
- Date: Mon, 26 Dec 2011 19:30:29 -0800
- To: Satoru Takagi <sa-takagi@kddi.com>
- Cc: public-svg-wg@w3.org
Hello Satoru, To be honest,: I don't see the sense in this feature. I can understand that people demand more features for rendering maps, like super strokes or special dash arrays. But why does SVG need the capability to automatically calculate, clip and render real world map data to something visible on the screen? We already have GML and some other open markup languages for describing map data. And as far as I can see SVGTL is not about replacing them. But why can't other applications transform the data to visible content? And the argument that these applications are proprietary (like described in the short video[1]) doesn't really fit. I don't see a problem in writing open source applications for the transformation if they are really required. The main problem is more that the map data itself is proprietary. But you can find alternatives even in this point like the open street map project. Kind regards, Dirk [1] http://www.slideshare.net/totipalmate/proposal-of-svg-map-8157601 Am 26.12.2011 um 17:52 schrieb Satoru Takagi: > Hi group, > > We have published implementation of SVGTL for WebKit as open source. > http://sourceforge.net/projects/wwwmap/ > > In this code, some other functions for mapping are implemented, too. > > Regards, > > Satoru Takagi >
Received on Tuesday, 27 December 2011 03:31:01 UTC