<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.1.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml"
>

<channel>
	<title>rajsingh.org blog</title>
	<link>http://www.rajsingh.org/blog</link>
	<description>the geoweb, OGC, and other interests</description>
	<pubDate>Tue, 15 Apr 2008 06:09:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>
	<language>en</language>
			<item>
		<title>KML now an OGC Open Standard</title>
		<link>http://www.rajsingh.org/blog/2008/04/15/kml-now-an-ogc-open-standard/</link>
		<comments>http://www.rajsingh.org/blog/2008/04/15/kml-now-an-ogc-open-standard/#comments</comments>
		<pubDate>Tue, 15 Apr 2008 05:57:20 +0000</pubDate>
		<dc:creator>rajsingh</dc:creator>
		
		<category><![CDATA[ogc]]></category>

		<category><![CDATA[ogckml]]></category>

		<guid isPermaLink="false">http://www.rajsingh.org/blog/2008/04/15/kml-now-an-ogc-open-standard/</guid>
		<description><![CDATA[After a little less than a year of great work by the KML SWG, we have a standard! The OGC press release gives some facts and a link to the OGC KML 2.2 Standard, and John Timmer at ars technica has a nice piece on the significance of this step. His article won&#8217;t offer anything [...]]]></description>
			<content:encoded><![CDATA[<p>After a little less than a year of great work by the KML SWG, we have a standard! The OGC <a href="http://www.opengeospatial.org/pressroom/pressreleases/857">press release</a> gives some facts and a <a href="http://www.opengeospatial.org/standards/kml/">link to the OGC KML 2.2 Standard</a>, and John Timmer at <em>ars technica</em> has a <a href="http://arstechnica.com/news.ars/post/20080414-googles-kml-map-markup-language-now-an-official-standard.html">nice piece</a> on the significance of this step. His article won&#8217;t offer anything new for geo industry veterans, but it&#8217;s great to see the mainstream IT media &#8220;get it&#8221; when it comes to our technologies and markets.</p>
<p>This is hopefully a big win for individuals who contribute data to one site, and would like to use it in many others &#8212; not to mention the companies whose business model revolves around these altruistic, bottom-up data providers. One small step for OGC, and one big step towards breaking down data silos!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rajsingh.org/blog/2008/04/15/kml-now-an-ogc-open-standard/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Roll Your Own KML App</title>
		<link>http://www.rajsingh.org/blog/2008/03/27/roll-your-own-kml-app/</link>
		<comments>http://www.rajsingh.org/blog/2008/03/27/roll-your-own-kml-app/#comments</comments>
		<pubDate>Thu, 27 Mar 2008 18:50:37 +0000</pubDate>
		<dc:creator>rajsingh</dc:creator>
		
		<category><![CDATA[mass market]]></category>

		<category><![CDATA[programming]]></category>

		<category><![CDATA[ogckml]]></category>

		<guid isPermaLink="false">http://www.rajsingh.org/blog/2008/03/27/roll-your-own-kml-app/</guid>
		<description><![CDATA[This morning at the OGC Technical Committee meeting, the Google Earth &#38; Maps team announced an alpha of libkml, an open source (BSD) library for reading/parsing/writing KML 2.2. It&#8217;s a C++ library, but includes SWIG bindings for Java, Python, Ruby, Perl and PHP. The hope is that this piece of code will help developers build [...]]]></description>
			<content:encoded><![CDATA[<p>This morning at the <a href="http://www.opengeospatial.org/event/0803tc">OGC Technical Committee meeting</a>, the Google Earth &#38; Maps team announced an alpha of <a href="http://libkml.googlecode.com">libkml</a>, an open source (BSD) library for reading/parsing/writing KML 2.2. It&#8217;s a C++ library, but includes SWIG bindings for Java, Python, Ruby, Perl and PHP. The hope is that this piece of code will help developers build comprehensive, robust KML support into their applications. But note, this is NOT a mini-Google Earth. You just get KML support &#8211;&#160;there&#8217;s no way to get that streaming earth imagery goodness that you see in GE, although I suppose you can combine this with a map access API (from Google, Virtual Earth, Yahoo!, etc.) to get nice base maps in your app. Enjoy!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rajsingh.org/blog/2008/03/27/roll-your-own-kml-app/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Are Pigs Flying? Microsoft&#8217;s Big Interoperability News</title>
		<link>http://www.rajsingh.org/blog/2008/02/25/can-pigs-fly-microsofts-big-interoperability-news/</link>
		<comments>http://www.rajsingh.org/blog/2008/02/25/can-pigs-fly-microsofts-big-interoperability-news/#comments</comments>
		<pubDate>Mon, 25 Feb 2008 04:13:20 +0000</pubDate>
		<dc:creator>rajsingh</dc:creator>
		
		<category><![CDATA[ogc]]></category>

		<category><![CDATA[mass market]]></category>

		<category><![CDATA[programming]]></category>

		<guid isPermaLink="false">http://www.rajsingh.org/blog/2008/02/25/can-pigs-fly-microsofts-big-interoperability-news/</guid>
		<description><![CDATA[Needless to say, I was shocked and amazed when I saw this statement on Microsoft&#8217;s new Interoperability Principles this weekend. To summarize, they are committing to make open and public the protocols and APIs for their major products, including Vista, Exchange, SQL Server, and Office. And, wait for this, access to those documents will be [...]]]></description>
			<content:encoded><![CDATA[<p>Needless to say, I was shocked and amazed when I saw <a href="http://www.microsoft.com/interop/principles/default.mspx">this statement on Microsoft&#8217;s new Interoperability Principles</a> this weekend. To summarize, they are committing to make open and public the protocols and APIs for their major products, including Vista, Exchange, SQL Server, and Office. And, wait for this, access to those documents will be free. Is your mind blown yet? How about reading on and seeing that they plan to embrace non-Microsoft standards, and &#8220;increase interoperability with open source solutions&#8221;? I&#8217;m going to take all this at face value and say, &#8220;Bravo Microsoft!&#8221; I hope it all plays out according to this plan. The IT world will be a much better place if it does.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rajsingh.org/blog/2008/02/25/can-pigs-fly-microsofts-big-interoperability-news/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Mapping is the new spreadsheet</title>
		<link>http://www.rajsingh.org/blog/2008/02/15/mapping-is-the-new-spreadsheet/</link>
		<comments>http://www.rajsingh.org/blog/2008/02/15/mapping-is-the-new-spreadsheet/#comments</comments>
		<pubDate>Fri, 15 Feb 2008 17:48:45 +0000</pubDate>
		<dc:creator>rajsingh</dc:creator>
		
		<category><![CDATA[ogc]]></category>

		<category><![CDATA[mass market]]></category>

		<category><![CDATA[ogckml]]></category>

		<guid isPermaLink="false">http://www.rajsingh.org/blog/2008/02/15/mapping-is-the-new-spreadsheet/</guid>
		<description><![CDATA[I was over at Harvard yesterday talking to people from the GSD, the Herbarium, the Library, the new Center for Geographic Analysis, and MassGIS. It was great to see some old friends and make some new ones. One topic that came up was why you don&#8217;t see OGC standards in widespread usage. I argued that [...]]]></description>
			<content:encoded><![CDATA[<p>I was over at <a href="http://www.gsd.harvard.edu/">Harvard</a> yesterday talking to people from the GSD, the Herbarium, the Library, the new <a href="http://www.gis.harvard.edu/icb/icb.do">Center for Geographic Analysis</a>, and MassGIS. It was great to see some old friends and make some new ones. One topic that came up was why you don&#8217;t see OGC standards in widespread usage. I argued that the geospatial Web is where the regular Web was in 1996, when the tech industry thought that HTML was so easy and powerful that everyone would build their own Web sites – not by writing HTML but by using tools like Dreamweaver. As it turns out, that was still way too high a barrier to entry. People didn&#8217;t want the hassle of designing a site from scratch. They wanted to post a blog entry or a MySpace page. That&#8217;s when the Web saw a real quantum leap in content.</p>
<p>So in my mind, there&#8217;s a continuum of tech diffusion, where the first stage is raw HTML/XML/KML/URL coding by alpha techies. The second stage is using software tools that automate that raw coding. And the real diffusion comes when companies offer tools that automate 90% of the content creation busywork, and let users compete that last 10% that is unique to their interests. OGC is just moving into the second stage, and we don&#8217;t even know what that last stage will look like.</p>
<p>The discussion reminded some of us of an idea we had late in the 1990s that mapping should be as commonplace as spreadsheets. We were wondering whether that type of revolutionary leap could come from the GIS industry or would come from mainstream Web hackers. So it was very timely to wake up today and see this <a href="http://blog.wired.com/monkeybites/2008/02/google-makes-it.html">Wired article today about using Google Spreadsheets to create KML</a>. Is this the way most geographic content creation will happen in the future?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rajsingh.org/blog/2008/02/15/mapping-is-the-new-spreadsheet/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Always use the en-dash</title>
		<link>http://www.rajsingh.org/blog/2008/02/06/always-use-the-en-dash/</link>
		<comments>http://www.rajsingh.org/blog/2008/02/06/always-use-the-en-dash/#comments</comments>
		<pubDate>Wed, 06 Feb 2008 05:29:50 +0000</pubDate>
		<dc:creator>rajsingh</dc:creator>
		
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.rajsingh.org/blog/2008/02/06/always-use-the-en-dash/</guid>
		<description><![CDATA[I think my college newspaper experience has made me a little obsessive about writing – style, format, and clarity. My job requires reading a ton of writing done by programmers, and this group, to put it gently, is the writing equivalent of a bull in a china shop. So I post this in hopes that [...]]]></description>
			<content:encoded><![CDATA[<p>I think my college newspaper experience has made me a little obsessive about writing – style, format, and clarity. My job requires reading a ton of writing done by programmers, and this group, to put it gently, is the writing equivalent of a bull in a china shop. So I post this in hopes that I can fix at least one technical writing problem with this simple rule. Always use the en-dash.<br />
One issue I&#8217;ve been obsessing about lately is the use of dashes. Specifically, when to just hit the &#8216;-&#8217; key, or (on Mac) hold down option as well to get an &#8216;en-dash&#8217;, or do the option-shift-dash dance to get the &#8216;em-dash&#8217; (by the way I have no idea how these work on the PC, but I remember something about F-keys, aagh!). I finally decided to research the issue, and found out it&#8217;s actually very simple. At least according to <a href="http://en.wikipedia.org/wiki/Em-dash#Em_dash">Wikipedia</a>.</p>
<blockquote><p>The em dash, or m dash, m-rule, etc., (—), indicates a parenthetical thought—like this one—or some similar interpolation. Its name derives from its defined width of one em (originally the width of the letter m), which is the length, expressed in points, by which font sizes are typically specified.</p>
<p>Traditionally an em dash—like so—or a spaced em dash — like so — has been used for a dash in running text. The Elements of Typographic Style recommends the more concise spaced en dash – like so – and argues that the length and visual magnitude of an em dash &#8220;belongs to the padded and corseted aesthetic of Victorian typography&#8221;. The spaced en dash is also the house style for certain major publishers (Penguin, Cambridge University Press, and Routledge among them).</p>
<p>The en dash (always with spaces, in running text) and the spaced em dash both have a certain technical advantage over the unspaced em dash. In most typesetting and most word processing, the spacing between words is expected to be variable, so there can be full justification. Alone among punctuation that marks pauses or logical relations in text, the unspaced em dash disables this for the words between which it falls. The effect can be uneven spacing in the text.</p></blockquote>
<p>So programmers, the dash is for hyphenation or a minus sign. Only use it as such. For a parenthetical thought, use the en-dash – option-dash on the Mac. See how nice that en-dash is?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rajsingh.org/blog/2008/02/06/always-use-the-en-dash/feed/</wfw:commentRss>
		</item>
		<item>
		<title>It&#8217;s too hard to find and share the coolness of Live Maps</title>
		<link>http://www.rajsingh.org/blog/2008/02/03/its-too-hard-to-find-and-share-the-coolness-of-live-maps/</link>
		<comments>http://www.rajsingh.org/blog/2008/02/03/its-too-hard-to-find-and-share-the-coolness-of-live-maps/#comments</comments>
		<pubDate>Sun, 03 Feb 2008 19:50:37 +0000</pubDate>
		<dc:creator>rajsingh</dc:creator>
		
		<category><![CDATA[mass market]]></category>

		<category><![CDATA[ogckml]]></category>

		<guid isPermaLink="false">http://www.rajsingh.org/blog/2008/02/03/its-too-hard-to-find-and-share-the-coolness-of-live-maps/</guid>
		<description><![CDATA[Investigating the location of the WUMB transmitter, Doc Searls notes that while the Live Maps birdseye view is awesome, it&#8217;s way too hard to find and share. John Udell picks up the thread and suggests a workaround, but that&#8217;s not the point of my mentioning this. 
Personally, I haven&#8217;t had much of a problem navigating [...]]]></description>
			<content:encoded><![CDATA[<div class="'snap_preview'">Investigating the location of the WUMB transmitter, <a href="http://blogs.law.harvard.edu/doc/2008/01/25/how-microsoft-could-kick-some-google-ass/">Doc Searls notes</a> that while the Live Maps birdseye view is awesome, it&#8217;s way too hard to find and share. John Udell <a href="http://blog.jonudell.net/2008/01/25/doc-searls-its-too-hard-to-find-and-share-the-coolness-of-live-maps/">picks up the thread</a> and suggests a workaround, but that&#8217;s not the point of my mentioning this. </p>
<p>Personally, I haven&#8217;t had much of a problem navigating in Live Maps, but I <em>have </em>had no end of problems figuring out how to work with &#8220;collections&#8221;, and get GeoRSS and/or KML streams of the collections I create. I always have to go back to the blog entries I&#8217;ve bookmarked to remember how to make the site do what I want it to do, and I&#8217;m probably a more savvy user than their target audience. It&#8217;s a shame because the Virtual Earth group has been coming up with some terrific stuff in the last year or so. </p>
<p>So to paraphrase <a href="http://en.wikipedia.org/wiki/Godspell">Godspell</a> &#8212; via the Bible &#8212; my message to the Virtual Earth team is, stop hiding your light under a bushel and re-think that UI my friends.</div>
]]></content:encoded>
			<wfw:commentRss>http://www.rajsingh.org/blog/2008/02/03/its-too-hard-to-find-and-share-the-coolness-of-live-maps/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Android, Locate me!</title>
		<link>http://www.rajsingh.org/blog/2007/11/15/android-locate-me/</link>
		<comments>http://www.rajsingh.org/blog/2007/11/15/android-locate-me/#comments</comments>
		<pubDate>Thu, 15 Nov 2007 07:29:20 +0000</pubDate>
		<dc:creator>rajsingh</dc:creator>
		
		<category><![CDATA[geo]]></category>

		<category><![CDATA[mass market]]></category>

		<guid isPermaLink="false">http://www.rajsingh.org/blog/2007/11/15/android-locate-me/</guid>
		<description><![CDATA[Check out Ed Parsons&#8217;, Android and LBS - in the stack at last…. I agree with him that &#8220;LBS would only really make sense as an underlining infrastructure that is available to all applications, therefore allowing much higher levels of integration.&#8221; Congrats on the release Google, and good luck, Android.
]]></description>
			<content:encoded><![CDATA[<p>Check out Ed Parsons&#8217;,<em><a href="http://www.edparsons.com/?p=574"> Android and LBS - in the stack at last…</a></em>. I agree with him that &#8220;LBS would only really make sense as an underlining infrastructure that is available to all applications, therefore allowing much higher levels of integration.&#8221; Congrats on the release Google, and good luck, Android.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rajsingh.org/blog/2007/11/15/android-locate-me/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Can Neogeography save mapping?</title>
		<link>http://www.rajsingh.org/blog/2007/11/11/can-neogeography-save-mapping/</link>
		<comments>http://www.rajsingh.org/blog/2007/11/11/can-neogeography-save-mapping/#comments</comments>
		<pubDate>Sun, 11 Nov 2007 04:24:06 +0000</pubDate>
		<dc:creator>rajsingh</dc:creator>
		
		<category><![CDATA[geo]]></category>

		<category><![CDATA[mass market]]></category>

		<guid isPermaLink="false">http://www.rajsingh.org/blog/2007/11/11/can-neogeography-save-mapping/</guid>
		<description><![CDATA[Michael Goodchild makes a good point in &#8220;Citizens as Voluntary Sensors: Spatial Data Infrastructure in the World of Web 2.0&#8221; as he argues that there is a &#8220;dramatic decline in the supply of geographic information worldwide&#8221;, due in large part to the reduction in funding for national mapping efforts over the last few decades. With [...]]]></description>
			<content:encoded><![CDATA[<p>Michael Goodchild makes a good point in &#8220;<a href="http://ijsdir.jrc.it/vol2.cfm">Citizens as Voluntary Sensors: Spatial Data Infrastructure in the World of Web 2.0</a>&#8221; as he argues that there is a &#8220;dramatic decline in the supply of geographic information worldwide&#8221;, due in large part to the reduction in funding for national mapping efforts over the last few decades. With no change in government policy on the horizon, it&#8217;s natural to look to voluntary mapping efforts like <a href="http://www.openstreetmap.org/">OpenStreetMap</a> and the <a href="http://bbs.keyhole.com">KML community</a> to fill the gap. Hopefully these &#8220;citizen scientist&#8221; communities can mature to far surpass what government agencies provided in the past. Not a lot of answers here, but some good questions, and it&#8217;s only 9 pages!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rajsingh.org/blog/2007/11/11/can-neogeography-save-mapping/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Atom is Fully-Baked</title>
		<link>http://www.rajsingh.org/blog/2007/11/05/atom-is-fully-baked/</link>
		<comments>http://www.rajsingh.org/blog/2007/11/05/atom-is-fully-baked/#comments</comments>
		<pubDate>Mon, 05 Nov 2007 06:50:13 +0000</pubDate>
		<dc:creator>rajsingh</dc:creator>
		
		<category><![CDATA[georss]]></category>

		<category><![CDATA[mass market]]></category>

		<category><![CDATA[georest]]></category>

		<guid isPermaLink="false">http://www.rajsingh.org/blog/2007/11/05/atom-is-fully-baked/</guid>
		<description><![CDATA[Joe Gregorio notes in The end of the AtomPub WG that the Atom Publishing Format and Protocol WG (atompub) in the Application Area has concluded. Developers can go into full programming mode knowing that the encodings and interfaces aren&#8217;t changing any time soon. Thanks AtomPub WG for a great standard.
]]></description>
			<content:encoded><![CDATA[<p>Joe Gregorio notes in <a href="http://bitworking.org/news/258/The-end-of-the-AtomPub-WG">The end of the AtomPub WG</a> that the Atom Publishing Format and Protocol WG (atompub) in the Application Area has concluded. Developers can go into full programming mode knowing that the encodings and interfaces aren&#8217;t changing any time soon. Thanks AtomPub WG for a great standard.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rajsingh.org/blog/2007/11/05/atom-is-fully-baked/feed/</wfw:commentRss>
		</item>
		<item>
		<title>KML, GeoRSS Everywhere</title>
		<link>http://www.rajsingh.org/blog/2007/10/31/kml-georss-everywhere/</link>
		<comments>http://www.rajsingh.org/blog/2007/10/31/kml-georss-everywhere/#comments</comments>
		<pubDate>Wed, 31 Oct 2007 00:39:10 +0000</pubDate>
		<dc:creator>rajsingh</dc:creator>
		
		<category><![CDATA[georss]]></category>

		<category><![CDATA[mass market]]></category>

		<category><![CDATA[ogckml]]></category>

		<guid isPermaLink="false">http://www.rajsingh.org/blog/2007/10/31/kml-georss-everywhere/</guid>
		<description><![CDATA[I was working on a Yahoo Pipe last night, and I noticed that Pipes will automatically figure out if you have created a geospatial pipe, and show it on a map without you having to do anything! And to top it off, you can get KML output of your pipe! Now if they drop the [...]]]></description>
			<content:encoded><![CDATA[<p>I was working on a <a href="http://pipes.yahoo.com/pipes/pipe.info?_id=qqD8rKuG3BGaDtdKjknRlg">Yahoo Pipe</a> last night, and I noticed that Pipes will automatically figure out if you have created a geospatial pipe, and show it on a map without you having to do anything! And to top it off, you can get KML output of your pipe! Now if they drop the old-fashioned <a href="http://georss.org/w3c">W3C Geo</a> point-only format and support <a href="http://georss.org/simple">real</a> <a href="http://georss.org/gml">GeoRSS</a> they&#8217;ll really have something (<em>hint, hint</em>).</p>
<p>What this means is that you can create and export KML content from Google, Microsoft and Yahoo! now. The mind bubbles at the possibilities&#8230;</p>
<p>By the way, if you&#8217;re actually interested the content of my <a href="http://pipes.yahoo.com/pipes/pipe.info?_id=qqD8rKuG3BGaDtdKjknRlg">Cambridge, MA Happenings pipe</a> and not just the technology, you should know that there are a lot of good events that aren&#8217;t getting properly geo-located, so read the feed, not just the map.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rajsingh.org/blog/2007/10/31/kml-georss-everywhere/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
