�ݺ�ߣ

Editor's Notes

• #3: Bear in mind that mapping is also quite big in Japan. A lot of government agencies make detailed map data freely available and there has been a lot of interest in exchange formats.
• #4: You can already realise mapping applications in script, the Web platform supports it, so what’s the problem?The main problem is that current systems are closed.You’re at the mercy of the mapping service for offline access.It’s impossible to do ad-hoc sharing of map data unless the service provides what you need.And you can’t mash up data from different sources freely except within the bounds of what the provider allows (e.g. KML limits you to POI). e.g. Base map from MapFanWeb, route from Navitime, shop search from Yahoo Maps, POI from Google MapsBasically, the user is not in control
• #5: My experienceITU Telecommunication Standardization Sector (ITU-T), 25 Oct 2011, focus on standards-based disaster relief solutions:"(5) to consider scalable vector graphics (SVG) as a key technology for graphical maps on mobile devices"http://www.itu.int/en/ITU-T/tsbdir/cto/Documents/111025/Communique-final.pdf
• #6: So that’s just one down side of relying on closed technology for maps.You’re really dependent on the mapping service, the user has no control, no flexibility.Takagi-san says the Web should be…- Anyone use systems without depending on anyone- Anyone easily publish diverse contents- Anyone easily mash-up any contents
• #9: * The key thing is that tiles are connected via "hyperlinks" - Webby* Links go from low-res containers to high-res containers* Containers contain a series of links to tiles with coord info
• #10: Of course, containers can be cascaded
• #11: * Links currently by <animation> should become <tile>- Layer file gives x/y/width/height for viewport only (and, presumably, so UA knows which need to be loaded/pre-fetched)- Actual transformation between coordinate spaces is achieved through the <gCS>
• #12: * Specifies transformation from local coords to global coordsData from tiles transformed to global coords, then from global coords to tile spaceBoth the container files and tiles have this on themWhy not just specify in global coords to begin with? - precision - ability to look at the file independently- This information is somewhat redundant with the info in the layer file but supports mashup? i.e. you don't need the containing layer - the coords in the layer is mostly just for establishing the viewport and tell what to loadconcern about the 'matrix' notation being confusingsrsName, Tab suggests ("this-is-a-map")
• #13: same facility, but overlay the data (how to know which data is to be overlayed and which is to be replaced?)
• #14: do with media queries?
• #16: Shared paths -- this is when you have shapes which share an edge. For example, boundaries of countries, esp. when the boundary is dashed. A requirement for SVG2 (http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Input#Shared_paths) but no commitment, at riskFixed-size objects -- e.g. map markers, UI controls i.e. SVG 1.2 Tiny's transform-ref SVG 2 has a requirement for this (http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Input#Constrained_Transformations) but no commitment, at risk Concern about whether this addresses needs, e.g. rotation without scalingNon-linear transformations Not in SVG 2.
• #17: Built-in UI controls for mapping (e.g. controls on <video>)--rejected from SVG 2Programming-less geolocation--rejected from SVG 2 i.e. say "center on current location" w/o using scriptSVG views with geographic coords -- e.g. map.svg#svgView(global(lng,lat,w,h))w and h are in degrees -- like another media fragment identifier (basically xywh=degree:lng,lat,w,h) -- would also be useful to just have x,y (e.g. center the map on my restaurant) -- resolved to add to svgView syntax if tiling and layering supported
• #18: API for smooth transition action of zooing,panning,rotating -- e.g. ability to suspend redraw whilst panning / zooming ? turn off fine detail while panning?Transformation functions between global/geospatial coordinate systems and user/viewport coordinate systems -- accepted for SVG 2 but not listed in requirementsDOM access API for cascading SVG documents -- i.e. <tile> elements need .contentDocument/contentWindow