http://highearthorbit.com/kml-3-kick-off-module-metadata/ Transmitting ideas, observations, and images from 42,000 km. Thu, 11 Mar 2010 18:26:25 -0800 http://wordpress.org/?v=2.9-rare hourly 1 http://highearthorbit.com/kml-3-kick-off-module-metadata/comment-page-1/#comment-204252 GeoCommons Maker! launches :: High Earth Orbit Wed, 01 Oct 2008 11:46:15 +0000 http://highearthorbit.com/kml-3-kick-off-module-metadata/#comment-204252 [...] the future, it would be quite nice to have better handling of rules or cascading styling that also linked to attributes in [...] [...] the future, it would be quite nice to have better handling of rules or cascading styling that also linked to attributes in [...]

]]> http://highearthorbit.com/kml-3-kick-off-module-metadata/comment-page-1/#comment-100306 Jeremy Cothran Fri, 10 Aug 2007 14:51:04 +0000 http://highearthorbit.com/kml-3-kick-off-module-metadata/#comment-100306 Thanks for the article and attention to metadata in regards to KML. ObsKML is what I developed and used as an xml staging format for my own work and support as a possible simple metadata schema for community adoption. 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. Thanks for the article and attention to metadata in regards to KML. ObsKML is what I developed and used as an xml staging format for my own work and support as a possible simple metadata schema for community adoption. 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.

]]> http://highearthorbit.com/kml-3-kick-off-module-metadata/comment-page-1/#comment-99560 Sean Gillies Mon, 06 Aug 2007 14:47:35 +0000 http://highearthorbit.com/kml-3-kick-off-module-metadata/#comment-99560 Don't confuse feature attributes, which are data, with metadata. Don’t confuse feature attributes, which are data, with metadata.

]]>