<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: KML 3 Kick-off, Module: Styling</title>
	<atom:link href="http://highearthorbit.com/kml-3-kick-off-module-styling/feed/" rel="self" type="application/rss+xml" />
	<link>http://highearthorbit.com/kml-3-kick-off-module-styling/</link>
	<description>Transmitting ideas, observations, and images from 42,000 km.</description>
	<pubDate>Thu, 24 Jul 2008 05:30:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: High Earth Orbit &#187; Blog Archive &#187; EPA KML a great step, but both forward and backward</title>
		<link>http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-129965</link>
		<dc:creator>High Earth Orbit &#187; Blog Archive &#187; EPA KML a great step, but both forward and backward</dc:creator>
		<pubDate>Sun, 02 Dec 2007 14:55:45 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-129965</guid>
		<description>[...] tell once you&#8217;ve exported. Unfortunately KML doesn&#8217;t currently support the ability to style based on ExtendedData, other than for the Balloon text. But it would still be useful to put this data [...]</description>
		<content:encoded><![CDATA[<p>[...] tell once you&#8217;ve exported. Unfortunately KML doesn&#8217;t currently support the ability to style based on ExtendedData, other than for the Balloon text. But it would still be useful to put this data [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-99159</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Sat, 04 Aug 2007 13:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-99159</guid>
		<description>@Jason Birch &#038; @Brian Flood - KML 3 will probably only support 4326, and so would not require (or support) specifying it anywhere in the actual markup. So you're safe. :)

I'm writing up the Metadata module post this weekend and will post it on Monday. </description>
		<content:encoded><![CDATA[<p>@Jason Birch &#038; @Brian Flood - KML 3 will probably only support 4326, and so would not require (or support) specifying it anywhere in the actual markup. So you&#8217;re safe. <img src='http://highearthorbit.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I&#8217;m writing up the Metadata module post this weekend and will post it on Monday.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Flood</title>
		<link>http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-99157</link>
		<dc:creator>Brian Flood</dc:creator>
		<pubDate>Sat, 04 Aug 2007 13:45:47 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-99157</guid>
		<description>good stuff, different but intersting none the less.

i have to agree with Jason on the CRS support, not only will it confuse a great deal of user creating content, ti will also make it that much harder for those integrating KML into their applications.

CSS in KML might be a very natural replacement for the existing styling, a "class" attribute seems right. The CSS3 attribute evaluator would also eliminate the need to use Update tags to change styling of placemarks at runtime.

Was there any talk about how the attributes will be stored? KML Schema? Microformat? somethign else?

cheers
brian</description>
		<content:encoded><![CDATA[<p>good stuff, different but intersting none the less.</p>
<p>i have to agree with Jason on the CRS support, not only will it confuse a great deal of user creating content, ti will also make it that much harder for those integrating KML into their applications.</p>
<p>CSS in KML might be a very natural replacement for the existing styling, a &#8220;class&#8221; attribute seems right. The CSS3 attribute evaluator would also eliminate the need to use Update tags to change styling of placemarks at runtime.</p>
<p>Was there any talk about how the attributes will be stored? KML Schema? Microformat? somethign else?</p>
<p>cheers<br />
brian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Birch</title>
		<link>http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-99078</link>
		<dc:creator>Jason Birch</dc:creator>
		<pubDate>Sat, 04 Aug 2007 02:50:43 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-99078</guid>
		<description>I'm not sure about the value of CRS support in KML.  It should definitely be just an optional module, or at least an optional element with a default value of 4326, as many traditional KML users have no understanding of anything other than lat/lon.

Whatever you do, make sure that KML doesn't get as open-ended as GML.  The minute you require users to do something other than simple markup like HTML, you lose a large chunk of your audience.

-J</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure about the value of CRS support in KML.  It should definitely be just an optional module, or at least an optional element with a default value of 4326, as many traditional KML users have no understanding of anything other than lat/lon.</p>
<p>Whatever you do, make sure that KML doesn&#8217;t get as open-ended as GML.  The minute you require users to do something other than simple markup like HTML, you lose a large chunk of your audience.</p>
<p>-J</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Birch</title>
		<link>http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-99075</link>
		<dc:creator>Jason Birch</dc:creator>
		<pubDate>Sat, 04 Aug 2007 02:42:05 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-99075</guid>
		<description>Andrew,

I'm wondering about the use of  tags inside the .kss document.  I can see that these would need to be used inside the KML document

&#60;kstyle src="http://example.com/style.kss" /&#62;

or

&#60;kstyle&#62;
    Placemark {
      font-size: 8px;
    }
&#60;/kstyle&#62;

but in the .kss file itself I'd prefer not to see tags.  

Let's see if those tags make it...

-J</description>
		<content:encoded><![CDATA[<p>Andrew,</p>
<p>I&#8217;m wondering about the use of  tags inside the .kss document.  I can see that these would need to be used inside the KML document</p>
<p>&lt;kstyle src=&#8221;http://example.com/style.kss&#8221; /&gt;</p>
<p>or</p>
<p>&lt;kstyle&gt;<br />
    Placemark {<br />
      font-size: 8px;<br />
    }<br />
&lt;/kstyle&gt;</p>
<p>but in the .kss file itself I&#8217;d prefer not to see tags.  </p>
<p>Let&#8217;s see if those tags make it&#8230;</p>
<p>-J</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl</title>
		<link>http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-99017</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Fri, 03 Aug 2007 19:36:11 +0000</pubDate>
		<guid isPermaLink="false">http://highearthorbit.com/kml-3-kick-off-module-styling/#comment-99017</guid>
		<description>Having KML being related to WMS is news to me. I am the one who put KML 2.1 into the OGC document template. Other than OWS-5, I have also been in on most of the discussions related to KML and the OGC.  In none of these discussions has there ever been any reference to working KML with WMS. There has been considerable discussion about how a WFS could provide KML instead of just GML.  Even the OGC Architecture Board has been in on these discussions. 

Maybe I am off base, but I believe that KML should eventually be a standalone OGC standard that can be referenced and used by other OGC standards (much as SLD is used by WMS). Further, KML 3.0 - again from my understanding - will be aligned and harmonized as appropriate with existing OGC/ISO standards, specifically CRS and GML 3.2.1 geometry.

Just had to jump in!

Carl</description>
		<content:encoded><![CDATA[<p>Having KML being related to WMS is news to me. I am the one who put KML 2.1 into the OGC document template. Other than OWS-5, I have also been in on most of the discussions related to KML and the OGC.  In none of these discussions has there ever been any reference to working KML with WMS. There has been considerable discussion about how a WFS could provide KML instead of just GML.  Even the OGC Architecture Board has been in on these discussions. </p>
<p>Maybe I am off base, but I believe that KML should eventually be a standalone OGC standard that can be referenced and used by other OGC standards (much as SLD is used by WMS). Further, KML 3.0 - again from my understanding - will be aligned and harmonized as appropriate with existing OGC/ISO standards, specifically CRS and GML 3.2.1 geometry.</p>
<p>Just had to jump in!</p>
<p>Carl</p>
]]></content:encoded>
	</item>
</channel>
</rss>
