<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Web Archeology: XML Binding Language (XBL)</title>
	<atom:link href="http://almaer.com/blog/web-archeology-xml-binding-language-xbl/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog/web-archeology-xml-binding-language-xbl</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Sat, 08 Sep 2012 07:06:53 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Emily</title>
		<link>http://almaer.com/blog/web-archeology-xml-binding-language-xbl/comment-page-1#comment-39672</link>
		<dc:creator>Emily</dc:creator>
		<pubDate>Tue, 30 Sep 2008 05:11:58 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/web-archeology-xml-binding-language-xbl#comment-39672</guid>
		<description>XML is potentially the answer for data interchange in all sorts of transactions, as long as both sides agree on the markup to use. (For example, should an email program expect to see tags named  and , or  and ?) The need for common standards will generate a lot of industry-specific standardization efforts in the years ahead. In the meantime, mechanisms that let you &quot;translate&quot; the tags in an XML document will be important. Such mechanisms include projects such as the Resource Description Framework initiative (RDF), which defines meta tags, and the Extensible Stylesheet Language specification (XSL), which lets you translate XML tags into other XML tags.</description>
		<content:encoded><![CDATA[<p>XML is potentially the answer for data interchange in all sorts of transactions, as long as both sides agree on the markup to use. (For example, should an email program expect to see tags named  and , or  and ?) The need for common standards will generate a lot of industry-specific standardization efforts in the years ahead. In the meantime, mechanisms that let you &#8220;translate&#8221; the tags in an XML document will be important. Such mechanisms include projects such as the Resource Description Framework initiative (RDF), which defines meta tags, and the Extensible Stylesheet Language specification (XSL), which lets you translate XML tags into other XML tags.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tavs</title>
		<link>http://almaer.com/blog/web-archeology-xml-binding-language-xbl/comment-page-1#comment-39244</link>
		<dc:creator>Tavs</dc:creator>
		<pubDate>Tue, 15 Jul 2008 14:32:51 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/web-archeology-xml-binding-language-xbl#comment-39244</guid>
		<description>You might want to see Sergey Ilinksys XBL 2.0 cross browser implementation in JavaScript. You can find it here: http://code.google.com/p/xbl/</description>
		<content:encoded><![CDATA[<p>You might want to see Sergey Ilinksys XBL 2.0 cross browser implementation in JavaScript. You can find it here: <a href="http://code.google.com/p/xbl/" rel="nofollow">http://code.google.com/p/xbl/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray Cromwell</title>
		<link>http://almaer.com/blog/web-archeology-xml-binding-language-xbl/comment-page-1#comment-38289</link>
		<dc:creator>Ray Cromwell</dc:creator>
		<pubDate>Sat, 12 Apr 2008 03:56:20 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/web-archeology-xml-binding-language-xbl#comment-38289</guid>
		<description>Brad,
  Sounds interesting. I think it might be instructive to go back and look at Netscape&#039;s push Desktop, and compare it to Active Desktop, vs today&#039;s RSS infrastructure and widgets, to find out what they did right, and what they did wrong.

-Ray</description>
		<content:encoded><![CDATA[<p>Brad,<br />
  Sounds interesting. I think it might be instructive to go back and look at Netscape&#8217;s push Desktop, and compare it to Active Desktop, vs today&#8217;s RSS infrastructure and widgets, to find out what they did right, and what they did wrong.</p>
<p>-Ray</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Arvidsson</title>
		<link>http://almaer.com/blog/web-archeology-xml-binding-language-xbl/comment-page-1#comment-38281</link>
		<dc:creator>Erik Arvidsson</dc:creator>
		<pubDate>Fri, 11 Apr 2008 16:24:14 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/web-archeology-xml-binding-language-xbl#comment-38281</guid>
		<description>One of the main benefits XBL (1 and 2) has over behaviors is anonymous content.  One could implement most of the things from XBL using HTCs but without anonymous content the end DOM would be polluted and very confusing.

BTW, XBL2 is a the top of my wishlist for improving web browsers as a platform.</description>
		<content:encoded><![CDATA[<p>One of the main benefits XBL (1 and 2) has over behaviors is anonymous content.  One could implement most of the things from XBL using HTCs but without anonymous content the end DOM would be polluted and very confusing.</p>
<p>BTW, XBL2 is a the top of my wishlist for improving web browsers as a platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Neuberg</title>
		<link>http://almaer.com/blog/web-archeology-xml-binding-language-xbl/comment-page-1#comment-38277</link>
		<dc:creator>Brad Neuberg</dc:creator>
		<pubDate>Thu, 10 Apr 2008 19:39:14 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/web-archeology-xml-binding-language-xbl#comment-38277</guid>
		<description>Don&#039;t forget Internet Explorer&#039;s data binding facilities; XUL&#039;s RDF templates; the Netscape Communicator suite that had a webtop; and desktop.com, a DHTML based webtop!</description>
		<content:encoded><![CDATA[<p>Don&#8217;t forget Internet Explorer&#8217;s data binding facilities; XUL&#8217;s RDF templates; the Netscape Communicator suite that had a webtop; and desktop.com, a DHTML based webtop!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad Neuberg</title>
		<link>http://almaer.com/blog/web-archeology-xml-binding-language-xbl/comment-page-1#comment-38276</link>
		<dc:creator>Brad Neuberg</dc:creator>
		<pubDate>Thu, 10 Apr 2008 19:36:43 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/web-archeology-xml-binding-language-xbl#comment-38276</guid>
		<description>Great examples Ray. Alot of this web archaelogy has come up as Dion and I plumb the historical record for web extension points, to chart out new ones for the future. I&#039;m a computer history geek so I eat this stuff up (and yes you can be a computer history geek AND have a life :)

Dion, are you up for guest posts? Ray, want to write a guest post on one of the things you bring up? One of the angles is to study not just the history but the actual mechanism as well as prior art, to act as a jumping off point as we explore new web extension mechanisms such as what Gears offers.

Brad Neuberg</description>
		<content:encoded><![CDATA[<p>Great examples Ray. Alot of this web archaelogy has come up as Dion and I plumb the historical record for web extension points, to chart out new ones for the future. I&#8217;m a computer history geek so I eat this stuff up (and yes you can be a computer history geek AND have a life :)</p>
<p>Dion, are you up for guest posts? Ray, want to write a guest post on one of the things you bring up? One of the angles is to study not just the history but the actual mechanism as well as prior art, to act as a jumping off point as we explore new web extension mechanisms such as what Gears offers.</p>
<p>Brad Neuberg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray Cromwell</title>
		<link>http://almaer.com/blog/web-archeology-xml-binding-language-xbl/comment-page-1#comment-38271</link>
		<dc:creator>Ray Cromwell</dc:creator>
		<pubDate>Wed, 09 Apr 2008 18:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/web-archeology-xml-binding-language-xbl#comment-38271</guid>
		<description>Hey Dion, 
  Great series. I have some suggestions for future archeological &quot;digs&quot;.

1) Remember the Push Bubble in 1997? Pre-RSS, we had Microsoft Channel Definition Format, Netscape&#039;s Javascript based Channel defs, Marimba, Pointcast, BackWeb, etc. Take That Davie Whiner, Microsoft invented XML syndicated content feeds!

2) AppletJavascript bridge, Common DOM API, etc

3) Netscape 4 JSSS :)

4) &quot;XML Data Islands&quot;

5) Oh, and while not much relevance tech wise, there was the PR battle of Netscape ONE vs Microsoft DNA

6) Old Java geezers will remember AFC vs IFC before JFC

7) Some Pulitzer prize would could be done investigating what ever happened to Netscape&#039;s &quot;Apollo&quot; follow-on to Netscape Enterprise Server.

8) In the years before OpenID and OAuth, before MS Passport and Sun Liberty Alliance, there was Netscape&#039;s proposal that everyone use SSL client certificates, and Netscape Certificate Server. Oh, how the wheel turns!</description>
		<content:encoded><![CDATA[<p>Hey Dion,<br />
  Great series. I have some suggestions for future archeological &#8220;digs&#8221;.</p>
<p>1) Remember the Push Bubble in 1997? Pre-RSS, we had Microsoft Channel Definition Format, Netscape&#8217;s Javascript based Channel defs, Marimba, Pointcast, BackWeb, etc. Take That Davie Whiner, Microsoft invented XML syndicated content feeds!</p>
<p>2) AppletJavascript bridge, Common DOM API, etc</p>
<p>3) Netscape 4 JSSS :)</p>
<p>4) &#8220;XML Data Islands&#8221;</p>
<p>5) Oh, and while not much relevance tech wise, there was the PR battle of Netscape ONE vs Microsoft DNA</p>
<p>6) Old Java geezers will remember AFC vs IFC before JFC</p>
<p>7) Some Pulitzer prize would could be done investigating what ever happened to Netscape&#8217;s &#8220;Apollo&#8221; follow-on to Netscape Enterprise Server.</p>
<p>8) In the years before OpenID and OAuth, before MS Passport and Sun Liberty Alliance, there was Netscape&#8217;s proposal that everyone use SSL client certificates, and Netscape Certificate Server. Oh, how the wheel turns!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
