<?xml version='1.0' encoding='utf-8'?>
<?xml-stylesheet href="/style/browser.xsl" type="text/xsl"?>
<essay xmlns="http://docbook.org/ns/docbook"
       xmlns:xlink="http://www.w3.org/1999/xlink"
       xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'
       xmlns:dc='http://purl.org/dc/elements/1.1/'
       xmlns:dcterms="http://purl.org/dc/terms/"
       xmlns:gal='http://norman.walsh.name/rdf/gallery#'
       version="pto">
<info>
<title>Static in the Echo</title>
<volumenum>6</volumenum>
<issuenum>46</issuenum>
<pubdate>2003-06-26</pubdate>
<date>$Date: 2005-09-11 10:27:02 -0400 (Sun, 11 Sep 2005) $</date>
<author><personname>
<firstname>Norman</firstname><surname>Walsh</surname>
</personname></author>
<copyright><year>2003</year><holder>Norman Walsh</holder></copyright>
<abstract>
<para>I've been following the Echo Project as best I can.
Conceptually, it seems like a good idea: the current state
of affairs with respect to RSS is pretty messy and this effort would
give us a fresh start. I've already voiced support for the idea.
But I'm really startled to see how complex things have gotten.
</para>
</abstract>
</info>
<epigraph>
<attribution>B. Reid</attribution>
<para xml:id='p1'><indexterm><primary>Reid</primary>
<secondary>B.</secondary></indexterm>Computer Science is the first
engineering discipline in which the complexity of the objects created
is limited solely by the skill of the creator, and not by the strength
of raw materials.</para>
</epigraph>

<para xml:id='p2'>I've been following the
<link xlink:href="http://intertwingly.net/wiki/pie/RoadMap">Echo
Project</link><footnote><para xml:id='p3'>This essay contains a number of links
to a Wiki. The dynamic nature of a Wiki means you may not see what I
saw. <foreignphrase>Caveat lector</foreignphrase>.
Oh, and the name of the project may change, too.</para>
<para xml:id='p4'>(And thanks to
<!--
FIXME: Dorothea's name should be a link, but that makes the PDF stylesheet choke.
It's easier to fix it here now, but I really should fix the stylesheets.
<link xlink:href="http://www.yarinareth.net/caveatlector/">
-->
<personname>
<firstname>Dorothea</firstname><surname>Salo</surname></personname>
for pointing me to the proper latin phrase.)
</para>
</footnote> as best I can. Conceptually, it seems like a good idea: the current state
of affairs with respect to RSS is pretty messy and this effort would
give us a fresh start. I've already
<link xlink:href="../25/slice">voiced support</link> for the idea.</para>

<para xml:id='p5'>But I'm really startled to see that what started with a pretty
simple <link xlink:href="http://intertwingly.net/wiki/pie/ConceptualModel">conceptual
model</link> consisting of author, date, link, and some content has
blossomed into
<link xlink:href="http://intertwingly.net/wiki/pie/EchoExample">something deeply
complex</link> with titles, subtitles, links, multiple dates, multiple authors,
contributors, and content variations with explicit MIME types.</para>

<para xml:id='p6'>Huh?!</para>

<para xml:id='p7'>Some of
<link xlink:href="http://intertwingly.net/wiki/pie/EscapedHtmlDiscussion">these
discussions</link> have actually gotten tangled up in the
differences between CDATA and other forms of escaping markup in XML.
It's tick season, folks, if you're that deep in the weeds make sure
you check yourselves carefully. :-) (That's a smiley folks. You know, humor.
No flames, please; no disrespect intended.)</para>

<para xml:id='p8'>Perhaps I completely misunderstood the goal of this exercise, but I was
expecting the Echo core to consist of about five elements:</para>

<programlisting><![CDATA[<entry xmlns="some/appropriate/uri">
  <publisher>Norman Walsh</publisher>
  <link>some/permalink/uri</link>
  <date>2003-06-26</date>
  <description>Well-formed XML.</description>
</entry>]]></programlisting>

<para xml:id='p9'>End of story. (More or less, anyway.)</para>

<para xml:id='p10'>Now, make no mistake, I want other stuff in there,
but I thought that extension modules were for that purpose. Some people
have a deep aversion to namespaces and that perhaps drives them to put
<quote>everything that might reasonably be needed</quote> in the core.
Uhm. No, thank you.</para>

<para xml:id='p11'>I would expect some small amount of standardization around each
of the extension modules, but I'm happy to let a thousand flowers
bloom there.</para>

<para xml:id='p12'>Let's standardize the core today. We can come back and
standardize the extensions later, after we know which ones are really
useful.</para>

</essay>
