<?xml version="1.0"?>
<!-- RSS generated by Radio UserLand v8.0.5 on Mon, 16 Sep 2002 13:39:39 GMT -->
<rss version="0.92">
	<channel>
		<title>Eric Scoles: Meta Blogging</title>
		<link>http://www.antikoan.net/blog/categories/metaBlogging/</link>
		<description>On the larger ramifications of blogging, in the sense of a &quot;movement&quot; and in the sense of the act, itself.</description>
		<copyright>Copyright 2002 Eric Scoles</copyright>
		<lastBuildDate>Mon, 16 Sep 2002 13:39:39 GMT</lastBuildDate>
		<docs>http://backend.userland.com/rss092</docs>
		<managingEditor>escoles@antikoan.net</managingEditor>
		<webMaster>escoles@antikoan.net</webMaster>
		<item>
			<description>&lt;p&gt;Haven&apos;t done a geek-post in a while. From &lt;a href=&quot;http://www.scripting.com/&quot;&gt;Scripting News&lt;/a&gt;: &lt;blockquote&gt;&lt;a href=&quot;http://www.oscom.org/conferences/berkeley2002/&quot;&gt;The Second Open Source Content Management Conference&lt;/a&gt; will take place &quot;at the Lawrence Hall of Science, University of California, Berkeley, CA 94720, from Wednesday, 25 September to Friday, 27 September 2002.&quot;&lt;/blockquote&gt;
&lt;/p&gt;
&lt;p&gt;Here are some interesting links from the &lt;a href=&quot;http://www.oscom.org/conferences/berkeley2002/program.php&quot; class=&quot;&quot;&gt;program&lt;/a&gt;:
&lt;dl&gt;
	&lt;dt&gt;Bitflux &lt;/dt&gt;
	&lt;dd&gt;WYSIWYG, cross-platform, browser-based XML editor, said to be used in the &lt;a href=&quot;http://www.wyona.org/&quot; class=&quot;&quot;&gt;Wyona&lt;/a&gt; content management system (see below). Apparently, this is built entirely in JavaScript (and, presumably, XSL). This is very much like something that I spec&apos;d out a few months ago, but never got moving on. I was behind the curve already, of course, but it&apos;s nice to know that I wasn&apos;t insane. (NOTE: Xopus [see below] also claims to be used in Wyona, and is also cross-platform and browser-based. Is Xopus a Java version of BitFlux?)&lt;/dd&gt;
	&lt;dd&gt;[&lt;a href=&quot;http://www.oscom.org/conferences/berkeley2002/abstracts/bitfluxeditor.php&quot; class=&quot;aBody&quot;&gt;abstract&lt;/a&gt;] [&lt;a href=&quot;http://www.bitfluxeditor.org/&quot; class=&quot;aBody&quot;&gt;BitFluxEditor.org&lt;/a&gt;] [&lt;a href=&quot;http://www.bitflux.com/&quot; class=&quot;&quot;&gt;BitFlux.com&lt;/a&gt;] [&lt;a href=&quot;http://www.bitflux.ch/&quot; class=&quot;&quot;&gt;BitFlux.ch&lt;/a&gt;]&lt;/dd&gt;

	&lt;dt&gt;Xopus&lt;/dt&gt;
	&lt;dd&gt;WYSIWYG, cross-platform, browser-based XML editor; when I looked at this the other day, I&apos;d swear the site page said it was used in the &lt;a href=&quot;http://www.wyona.org/&quot; class=&quot;&quot;&gt;Wyona&lt;/a&gt; content management system (see below), but I don&apos;t see that now. &lt;/dd&gt;
	&lt;dd&gt;[&lt;a href=&quot;http://www.oscom.org/conferences/berkeley2002/abstracts/xopus.php&quot; class=&quot;aBody&quot;&gt;abstract&lt;/a&gt;] [&lt;a href=&quot;&quot; class=&quot;aBody&quot;&gt;link&lt;/a&gt;] [&lt;a href=&quot;http://www.q42.nl/&quot; class=&quot;aBody&quot;&gt;Q42.NL&lt;/a&gt;] [&lt;a href=&quot;http://xopus.org/&quot; class=&quot;aBody&quot;&gt;Xopus.org&lt;/a&gt;] [&lt;a href=&quot;http://groups.yahoo.com/group/xopus/&quot; class=&quot;aBody&quot;&gt;Xopus Group on Yahoo&lt;/a&gt;]&lt;/dd&gt;

	&lt;dt&gt;Wyona&lt;/dt&gt;
	&lt;dd&gt;This must have been where I got the impression that Xopus is part of Wyona -- there&apos;s an item on the front page to the effect that Xopus2 is shipped with Wyona. This looks like a very interesting product indeed. Built around Coccoon and Apache, it seems as though it may in face be a sort of meta-CMS. From the Wyona.org site:
	&lt;blockquote&gt;
	Wyona is an interpreter of various XMLs, not just user&apos;s data, such as for instance articles, press-releases or addresses, but also regarding functionalities, such as for instance access controlling (IML and PML resp. XACML), revision controlling (RCML) or workflow management (WFML). The concept is similar to the one of a &quot;HTML Browser&quot;. You should be able to switch the Content Management System at any time. The network is the CMS. 
	&lt;/blockquote&gt;
	Based on their &lt;a href=&quot;http://www.wyona.org/docs/index.html&quot; class=&quot;&quot;&gt;documentation&lt;/a&gt;, they seem to support several editors, including both BitFlux and Xopus.
	&lt;/dd&gt;
	&lt;dd&gt;[&lt;a href=&quot;http://www.wyona.org/&quot; class=&quot;&quot;&gt;Wyona&lt;/a&gt;] [&lt;a href=&quot;&quot; class=&quot;aBody&quot;&gt;link&lt;/a&gt;] [&lt;a href=&quot;&quot; class=&quot;aBody&quot;&gt;link&lt;/a&gt;] [&lt;a href=&quot;&quot; class=&quot;aBody&quot;&gt;link&lt;/a&gt;]&lt;/dd&gt;

	&lt;dt&gt;OpenCms&lt;/dt&gt;
	&lt;dd&gt;Java-based, of course, and apparently JSP-centric.&lt;/dd&gt;
	&lt;dd&gt;[&lt;a href=&quot;http://www.oscom.org/conferences/berkeley2002/abstracts/kandzior.php&quot; class=&quot;aBody&quot;&gt;abstract&lt;/a&gt;] [&lt;a href=&quot;http://www.alkacon.com/&quot; class=&quot;aBody&quot;&gt;Alkacon Software&lt;/a&gt;] [&lt;a href=&quot;http://www.alkacon.com/download/Slides_Wyona_Kandzior_OpenCms.pdf&quot; class=&quot;aBody&quot;&gt;&quot;An introduction to OpenCms, Version 4.6&quot; [pdf]&lt;/a&gt;] [&lt;a href=&quot;http://www.opencms.org&quot; class=&quot;aBody&quot;&gt;OpenCms.org&lt;/a&gt;] [&lt;a href=&quot;&quot; class=&quot;aBody&quot;&gt;link&lt;/a&gt;]&lt;/dd&gt;

	&lt;dt&gt;ZOPE, Nuke&lt;/dt&gt;
	&lt;dd&gt;Also mentioned are the ZOPE CMF and Plone, a particular implementation thereof that seems like it&apos;s worth looking into. Xoops and PostNuke are mentioned -- PostNuke in particular will be an important thing to at least look at with regard to the upcoming August Group project.&lt;/dd&gt;
	&lt;dd&gt;[&lt;a href=&quot;http://www.oscom.org/conferences/berkeley2002/abstracts/CommunityCMSInterop.php&quot; class=&quot;aBody&quot;&gt;abstract: Plone&lt;/a&gt;] [&lt;a href=&quot;&quot; class=&quot;aBody&quot;&gt;abstract: Xoop, PostNuke&lt;/a&gt;] &lt;/dd&gt;

	&lt;dt&gt;OS Search Engines&lt;/dt&gt;
	&lt;dd&gt;This would be a good session to go to, especially since I don&apos;t really understand why you&apos;d need a search engine if you have a CMS. Drops names of several OS search engines: SWISH-E, &lt;a href=&quot;ht://Dig&quot;&gt;ht://Dig&lt;/a&gt;, ASPSeek, mnoGoSearch and Lucene.&lt;/dd&gt;
	&lt;dd&gt;[&lt;a href=&quot;http://www.oscom.org/conferences/berkeley2002/abstracts/rappoport.php&quot; class=&quot;aBody&quot;&gt;abstract&lt;/a&gt;] &lt;/dd&gt;

	&lt;dt&gt;The Red Hat CCM Content Management System&lt;/dt&gt;
	&lt;dd&gt;Java/JSP oriented CMS system which seems to be based on earlier, possibly proprietary products. The supporting documentation could be educations. &lt;/dd&gt;
	&lt;dd&gt;[&lt;a href=&quot;http://www.oscom.org/conferences/berkeley2002/abstracts/lutterkort.php&quot; class=&quot;aBody&quot;&gt;abstract&lt;/a&gt;] [&lt;a href=&quot;http://www.redhat.com/software/ccm/cms/&quot; class=&quot;aBody&quot;&gt;link&lt;/a&gt;]&lt;/dd&gt;

	&lt;dt&gt;Miscellaneous&lt;/dt&gt;
	&lt;dd&gt;Other names dropped in the program that I need to check out:
	&lt;ul&gt;
		&lt;li&gt; WebDAV
		&lt;li&gt; Midgard
	&lt;/ul&gt;
	
	&lt;/dd&gt;
&lt;/dl&gt;

&lt;/p&gt;</description>
			<source url="http://www.scripting.com/rss.xml">Scripting News</source>
			</item>
		<item>
			<description>&lt;p&gt;In &lt;a href=&quot;http://oblivio.com/road/02082801.shtml&quot; class=&quot;aBody&quot;&gt;five&lt;/a&gt; &lt;a href=&quot;http://diveintomark.org/archives/2002/08/29.html#proven_true&quot; class=&quot;aBody&quot;&gt;words&lt;/a&gt; &lt;a href=&quot;http://www.paradox1x.org/archives/000237.shtml#000237&quot; class=&quot;aBody&quot;&gt;or&lt;/a&gt; &lt;a href=&quot;http://scriptingnews.userland.com/backissues/2002/08/31#When:8:43:21AM&quot; class=&quot;aBody&quot;&gt;less&lt;/a&gt;: &quot;We don&apos;t realize we&apos;re lost.&quot;&lt;/p&gt;
&lt;p&gt;(...as well evidenced by the progression, above, from grim to positivistic. Wake up and sniff the koolaid: Can&apos;t you smell the bitter almonds?)</description>
			</item>
		<item>
			<title>Belated Thoughts on the Killer App of Blogging</title>
			<description>&lt;p&gt;Dave Winer seems &lt;em&gt;de facto&lt;/em&gt; to want to tie the concept of a blog to a specific format, or form factor. The truth of it, though, stares him in the face: It&apos;s not the software, it&apos;s the modality. Lotus didn&apos;t triumph by inventing the spreadhseet; it triumphed by &lt;em&gt;modeling&lt;/em&gt; it.&lt;/p&gt;
&lt;p&gt;The early electronic spreadsheets were imperfect analogs of the paper ones in much the same way that Radio or Blogger weblogs are imperfect analogs of paper notebooks, and BBS systems were imperfect analogs of common cork boards.&lt;/p&gt;
&lt;p&gt;To communicate the real relationship, Dave should look at is own fascination with the outliner, and especially with OPML and &quot;instant outlining.&quot; Radio&apos;s &quot;instant outlining&quot; feature comes closer to being the &quot;platform&quot; that will revolutionize blogging than Blogger/Radio/Manila/MT standard layout templates do. They are merely standard layouts; they don&apos;t let people reshape their work dynamically. Sure, if you&apos;re good with DHTML you can do all kinds of fun stuff; but where&apos;s the capability (just for example) to reverse the chronology so that you don&apos;t have to read backward through every weblog?&lt;/p&gt;
&lt;p&gt;The real breakthrough in spreadsheets wasn&apos;t calculation -- it was &lt;em&gt;presentation&lt;/em&gt;. Making the graphs; sorting the data. Back in the day, people would commit enormous amounts of time and effort to proprietary branches like Enable and Trapeze just to get presentation features that those programs could offer. It was Excel&apos;s outstanding (by the standard of the time) graphing features that gave it the crucial edge it needed to break in. I&apos;d argue that, given WordPerfect&apos;s utter dominance in word processing at the time and Word 1.x&apos;s generally poor showing against it, that it was Excel that was responsible for Windows&apos;s early inroads on the corporate side.&lt;/p&gt;
&lt;p&gt;So the real breakthrough in blogging is yet to come. FWIW, I think that breakthrough will come as some kind of a combination of centralized, network-based storage, and a more full realization of Dave Winer &lt;em&gt;et al.&apos;s&lt;/em&gt; idea of linking Instant Outlining to Jabber/Gabber. But they&apos;ve got to ditch OPML for a more general-purpose and less-fragile format, first.&lt;/p&gt;
</description>
			</item>
		<item>
			<description>&lt;p&gt;From DayPop, a tutorial on accessibility techniques for Radio/MT: &lt;a href=&quot;http://www.daypop.com/redirect?id=29621022&quot;&gt;&quot;Day 19: Using real table headers&quot;&lt;/a&gt; [&lt;a href=&quot;http://www.daypop.com/top.htm&quot;&gt;Daypop Top 40&lt;/a&gt;]&lt;/p&gt;
</description>
			<source url="http://www.daypop.com/top.rss">Daypop Top 40</source>
			</item>
		<item>
			<title>Verisign -- Because You Didn&apos;t Need That Good Night&apos;s Sleep, Anyway...</title>
			<link>http://www.textism.com/article/494/</link>
			<description>&lt;p&gt;Dean Allen @ &lt;A HREF=&quot;http://www.textism.com/&quot; class=&quot;aBody&quot;&gt;Textism&lt;/A&gt; has asked help to &lt;A HREF=&quot;http://www.textism.com/article/505/&quot; class=&quot;aBody&quot;&gt;set us up the Google bomb&lt;/A&gt; on &lt;A HREF=&quot;http://www.textism.com/article/494/&quot; class=&quot;aBody&quot;&gt;Verisign&lt;/A&gt;, in response to some of their latest acts of gross incompetence with regard to managing domains. (&lt;a href=&quot;http://www.daypop.com/search?q=link%3Awww.textism.com/article/494&amp;t=w&amp;max=672&quot; class=&quot;aBody&quot;&gt;Other citations&lt;/a&gt; on Daypop  / &lt;a href=&quot;http://www.google.com/search?hl=en&amp;q=verisign&quot; class=&quot;aBody&quot;&gt;Verisign Googled&lt;/a&gt; -- not much action so far, I fear, though I wouldn&apos;t be terribly surprised to find the results a little skewed....)&lt;/p&gt;
&lt;p&gt;It&apos;s a quintessentially libertarian tactic, and for Leslie&apos;s sake (and mine) I hope it works, but the real fix has to be Verisign fixing their broken practices -- or simply being driven out of business and their registrations turned over to more responsible vendors. Instead, I fear this will expose the weakness of a system driven by popular action. Verisign may be made up of arrogant putzes, but they&apos;ve got tremendous resources and a history of dirty-dealings, so I won&apos;t be at all surprised to see them come out of it smelling like a rose. Governing from below is a great idea; unfortunately, the fact that there &lt;em&gt;is&lt;/em&gt; an &quot;above&quot; will probably always subvert that ideal.
&lt;/p&gt;
&lt;p&gt;This story hits me on so many levels. On the one hand, as a domain registrant, I live in (mild, for me) fear that someone will hijack my domain and start getting all my email. On another hand, there&apos;s just the rich irony of it all: anyone who&apos;s been watching the playoffs (hockey or basketball) has seen the continuous loop Verisign commercial that&apos;s supposed to make you feel secure by flashing their brand on the screen. &lt;/p&gt;
&lt;p&gt;Yeah, right. Anybody in the business has known for years that Network Solutions has always been not merely incompetent, but also arrogant. I&apos;m just now learning, though (not having had to buy certificates before) that Verisign was always just about as bad. Which, I suppose, made it a marriage made in heaven. So I get a certain ironic paranoia from those ads, especially after reading about &lt;a href=&quot;http://leslie.harpold.com/&quot; class=&quot;aBody&quot;&gt;Leslie Harpold&lt;/a&gt;&apos;s &lt;a href=&quot;http://leslie.harpold.com/links.html&quot; class=&quot;aBody&quot;&gt;troubles&lt;/a&gt;, knowing that, should I make a clever enough (and &lt;EM&gt;just&lt;/EM&gt; clever enough would be clever enough, it seems) enemy, I can lose my domain thanks to their incompetence. &lt;/p&gt;&lt;p&gt;What does this do for Verisign&apos;s relations with their customers? Well, oddly enough, I think most CIOs (who are mostly finance guys used to letting the size of their assets get them ahead) won&apos;t bat an eyelash. Their Verisign reps will nudge-nudge, wink-wink and hint strongly that it&apos;s exactly what an artsy little anarchist deserves. (Hey, I&apos;m not describing, just predicting.)&lt;/p&gt;
&lt;p&gt;On the other hand, non-finance CIOs, and CTOs, and IT Directors (since IT&apos;s climb to C-level seems to have slowed with The Market) will smile and nod, all the while wondering how quickly they can migrate away from all their Verisign dependencies.&lt;/p&gt;
&lt;p&gt;Or so I can hope. Much as I don&apos;t want to see more people lose their jobs, it would do my heart good to see Verisign fail.&lt;/p&gt;</description>
			<source url="http://www.daypop.com/top/rss.xml">Daypop Top 40</source>
			</item>
		<item>
			<description>&lt;p&gt;From &lt;a href=&quot;http://www.metafilter.com/&quot;&gt;MetaFilter&lt;/a&gt;:
&lt;blockquote&gt;
&lt;a href=&quot;http://www.metafilter.com/comments.mefi/16730&quot;&gt;16730 &amp;raquo; April 29 11:10 AM&lt;/a&gt;. Alexa, the internet depository that lead to things like the wayback machine was acquired by Amazon some time ago. A new service, Alexa Web Search joins the power of Alexa&apos;s archive with Amazon&apos;s proven interface and feature set with Google&apos;s killer-app level searching power. The results are fairly impressive, adding a related sites layer that may actually help folks browsing the web (as opposed to direct searching). [via anil]&lt;/blockquote&gt;
TRANSLATION: Somebody has figured out a way to pour information about a site, gleaned from several different sources (using Alexa&apos;s dB), into an Amazon-style interface. I concur with one of the posters: It looks really &lt;strong&gt;weird&lt;/strong&gt;. And it &lt;em&gt;feels&lt;/em&gt; really weird, for that matter...&lt;/p&gt;</description>
			<source url="http://xml.metafilter.com/rss.xml">MetaFilter</source>
			</item>
		<item>
			<title>On the un-centeredness of edge services</title>
			<link>http://radio.weblogs.com/0107057/2002/04/27.html</link>
			<description>&lt;p&gt;John Burkhardt writes:
&lt;blockquote&gt;Most Web Services models are an extension of Client/Server architectures.  The service lives in the center, and you call it from the edge.  At Groove we are all about decentralization which leaves the power with the user.  So I can have my information accessible from anywhere, but it is always under my control and on my devices.  Of course, I do have to have a device connected somewhere to access it.  But hopefully you get the concept.&lt;/blockquote&gt;&lt;/p&gt;
&lt;p&gt;Alas, I fear I don&apos;t. This strikes me as a manifestation of the same fundamental error of both Notes (which Lotus never acknowledged, except tacitly, through only the initial introduction of Domino) and Radio (which Userland and the legions of Radio zealots all present as a virtue): &lt;strong&gt;You can only use it from one machine.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Here&apos;s a paradox: &lt;strong&gt;The truly de-centralized groupware will be server-based.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Put another way: &lt;strong&gt;To live at the edge, you must live at the center.&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
		</channel>
	</rss>
