Geotags.org > Defending KML against the proprietary police

Spatially Adjusted with James Feehttp://www.spatiallyadjusted.com [Spatially Adjusted with James Fee] It would appear that the only salient difference in proprietary-ness is that KML was developed by a single company (albeit with input from others), whereas GML was developed by a standards committee. The salient difference in the marketplace is that KML is usable and hand-editable, whereas GML is rather too complex for use without tools.

Some related posts from Technorati and Google.

Spatiallyadjusted.comhttp://www.spatiallyadjusted.com [Spatiallyadjusted.com] Spatially Adjusted with James Fee » ArcGIS Desktop: It would appear that the only salient difference in proprietary-ness is that KML was developed by a single company (albeit with input from others), whereas GML was developed by a standards committee. The salient difference in the marketplace is that KML is usable and hand-editable, whereas GML is rather […]

http://technology.slashgisrs.org [Technology.slashgisrs.org] SlashGISRS | Property: KML vs GML: Spatially Adjusted discuss KML and GML in relation to this lptf blog entry. One of the arguments from the lptf blog: "The salient difference in the marketplace is that KML is usable and hand-editable, whereas GML is rather too complex for use without tools."

http://lptf.blogspot.com [Lptf.blogspot.com] Let's Push Things Forward: "Proprietary" Formats: KML and GML: It is useful how GML is broken into numerous sub-schemas, and I think there is room in there for some alternate approaches. But right now you end up with some referential dependency complexity, where you have to look up where the various items are defined, you can't just peek under the covers and easily use the bits (like the geometry model) and still be called GML.

Reflected tags on Technorati: Blog, ,