Geotags.org > Validating against the OGC KML Schema in jEdit « Random Nodes

[Random Nodes] Once you have loaded your KML file, replace the root kml entity with the following instead of the older Google schemas, and you will be able to validate against the OGC’s KML and partial Atom schemas as you work:

Previous [Previous] zyrax » Blog Archive » Mapking G12 POI to KML...

Next [Next] Review: The KML Handbook | geo2web.com...

Some related posts from Technorati and Google.

[Random Nodes] KML Spec Bizarro? « Random Nodes: These resources will be single-feature, and will each be related to exactly one HTML representation of the same feature.  Now, it seems logical to me that I would specify an atom:link with rel="alternate"

[Entries for Sean Gillies Blog] Sean Gillies Blog: I believe it was probably the intention of the KML spec writers to import all of atom:link and that the language in the OGC KML spec is just erroneous. If developers go to the Atom syntax spec to understand atom:link, they'll be fine.

[Adsense blog] Adsense blog » New KML Interactive Sampler: The sample list on the left contains a variety of predefined KML samples, organized hierarchically by topic (i.e. ‘Lines and Paths’, ‘Polygons’, etc.) Clicking a sample in the list will load the KML contents into the editor and display the KML in the Earth preview window (see below).

[Galdos Systems Inc] KML, GML and REST: The origins of GML belong with the early days of the “new web”, meaning the suite of specifications including XML, XLink, XPointer, XSLT, RDF that sought to extend what one might think of as the conventional web, by abstracting the web’s basic notions like resources (from web pages, web sites), resource identifiers, and linking (href). In this generalization of the web of documents, generalized resources (often in XML) would replace web pages (XHTML), and XLinks would link or associate these resources much as href and anchor tags connected web pages. 

[OGC News Feed] OGC Reference Model (ORM) | OGC®: also shows sensor-observation value chains as the lifecycle of sensor-produced observations, from raw unprocessed data granules to information products and services delivered to applications and consumers. Depending on the requirements, sensor data may be delivered to the user in its most elemental unprocessed form, processed into an observation object complete with the metadata and processes used to estimate a value describing a phenomenon, or processed further, for example, into single-valued geographic feature or multi-valued coverage representations.

[High Earth Orbit] KML 3 Kick-off, Module: Metadata :: High Earth Orbit: KML’s earlier version Metadata tag was more oriented towards simple attribute style (no hierarchical nesting of elements) and while that might be sufficient for some applications, the basics which I needed to support my work was the ability to associate a list/collection of observations with an associated KML Placemark/TimeStamp. I’m not a member or participant in OGC specifications processes, but do hope that OGC is able to incorporate simpler document-centric approaches and recommendations for popular data/metadata formats in addition to the earlier/ongoing service-centric, query based approaches.

[OGC News Feed] The OGC Seeks Comment on OGC Candidate KML 2.2 Standard | OGC®: The submission of KML into the OGC consensus process by the RFC Submission team led by Google and Galdos Systems Inc. ensures that KML will be aligned with international best practices and standards, thereby enabling greater uptake and interoperability of Earth browser implementations.

[All Points Blog] Get your comments in on OGC KML - All Points Blog: I've wondered a lot about why they bothered to join, and why they want to submit to a process that has a high degree of risk in terms of KML being mutated beyond recognition. Google's line has unwaveringly been that they want KML to be 'owned' by someone other than Google so that more people would be able to use it.

[The MetaCarta Blog] Adoption of KML as a standard sets a precedent « The MetaCarta Blog: According to Lake, most OGC members, responding to a survey, said that the fact that KML became an OGC standard would encourage them to adopt it. They may have done so anyway due to Google’s commercial clout, he hastens to add, but now they have the “warm feeling” that KML is no longer controlled by one company that can change it at will.

[O'Reilly XML Blog] KML and glue - O'Reilly XML Blog: OGC provides fast-paced specification development and promotion of standards adoption, similar to other industry standards consortia such as W3C, IETF, and OMG. ISO is the dominant de jure international standards development organization (SDO), providing international government authority important to institutions and stockholders.

[Comments for Off the Map - Official Blog of FortiusOne] Structured Feature Data in KML, part one | Off the Map - Official ...: There are other things that are not completely ideal with the Schema tag solution.  For one thing, as far as I know, GeoCommons is the only application around that is actively using it and publishing Schema-based KML (if there are others, I would love to know about them, please comment).  This makes getting data that is already in this form a bit more difficult, but one of the things I would like to achieve here is trying to convince people that something along the lines that I’ve just been talking about is valuable right now, and is worth using more extensively either because of the sorts of things it allows you to do with your data in GeoCommons, or in other applications that I hope will spring up independently or around GeoCommons.

[Geo-Web] GML and KML Syntax « Geo-Web: KML provides a basic geometric objects including Point, LineString, Polygon.  Its geometry model is identical to GML v1.0 and 2.0.  Note that GML 3.0 is an extended version of the GML 2. geometry model.  Here is a comparison for a Polygon in KML and GML.

[Off the Map - Official Blog of FortiusOne] GeoData Format wars: GML vs KML vs ? | Off the Map - Official Blog ...: The main thing KML brings to the table, besides the fact that it’s built into every version of Google Earth, and will be an integral part of the ArcGIS 9.2 product line, is markup specific to things like styling, placemarks, and the like.  Most of this ties directly in to Google Earth features, but it’s still useful in other applications, and is the sort of thing that would need to be defined in a application-specific GML schema.

Reflected tags on Technorati: Blog, , ,