0 -> <?xml version="1.0" encoding="utf-8"?>
1 ->
2 -> <rss version="2.0"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:admin="http://webns.net/mvcb/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:content="http://purl.org/rss/1.0/modules/content/">
3 ->
4 -> <channel>
5 ->
6 -> <title>
7 -> dive into mark
8 -> </title>
9 ->
10 -> <link>
11 -> http://diveintomark.org/
12 -> </link>
13 ->
14 -> <description>
15 -> A lot of effort went into making this effortless.
16 -> </description>
17 ->
18 -> <dc:language>
19 -> en-us
20 -> </dc:language>
21 ->
22 -> <dc:creator>
23 -> f8dy@diveintomark.org
24 -> </dc:creator>
25 ->
26 -> <dc:rights>
27 -> Copyright 2002
28 -> </dc:rights>
29 ->
30 -> <dc:date>
31 -> 2002-09-26T01:28:52-05:00
32 -> </dc:date>
33 ->
34 -> <admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=2.21" />
35 ->
36 -> <admin:errorReportsTo rdf:resource="mailto:f8dy@diveintomark.org"/>
37 ->
38 -> <sy:updatePeriod>
39 -> hourly
40 -> </sy:updatePeriod>
41 ->
42 -> <sy:updateFrequency>
43 -> 1
44 -> </sy:updateFrequency>
45 ->
46 -> <sy:updateBase>
47 -> 2000-01-01T12:00+00:00
48 -> </sy:updateBase>
49 ->
50 -> <item>
51 ->
52 -> <title>
53 -> RSS 2.0 template
54 -> </title>
55 ->
56 -> <link>
57 -> http://diveintomark.org/archives/2002/09/26.html#rss_20_template
58 -> </link>
59 ->
60 -> <description>
61 -> RSS 2.0 template for Movable Type, ready to copy and paste over your existing RSS 0.91 template (index.xml). There are several design decisions at work in this tempate that bear explaining.
62 -> </description>
63 ->
64 -> <guid isPermaLink="false">
65 -> 1844@http://diveintomark.org/
66 -> </guid>
67 ->
68 -> <content:encoded>
69 -> <![CDATA[<p><a href="http://diveintomark.org/public/rss2.tmpl">RSS 2.0 template for Movable Type</a>, ready to copy and paste over your existing RSS 0.91 template (<code>index.xml</code>). No modifications are required, unless your weblog is in a language other than English, in which case you'll need to change the <code>dc:language</code> tag to <a href="http://www.loc.gov/standards/iso639-2/englangn.html">your language code</a>. (Use the 2-letter language code, unless there isn't one for your language, in which case, use the 3-letter language code. And while you're at it, put the same language code <a href="http://diveintoaccessibility.org/day_7_identifying_your_language.html">in your <code>HTML</code> tag</a> in your normal page templates. But I digress.)</p>
<p><a href="http://diveintomark.org/xml/rss2.xml">Here's what the RSS 2.0 output looks like</a>.</p>
<p>There are several design decisions at work in this template that bear explaining. First of all, this template is designed to be backward-compatible with all existing aggregators, news readers, and RSS parsers, ranging from the super-smart XML parser built into .NET to the dumb, minimal, regular-expression-based parser that your downstairs neighbor banged out on a Friday night. If you upgrade your existing <code>index.xml</code> right now, none of these parsers should crash, and none of your subscribers should scream bloody murder. This is a good thing.</p>
<p>Now then, if you look at the template, you'll notice a whole slew of lines at the top like <code>xmlns:dc="..."</code>. These are namespaces. Keven Hemenway has written an excellent primer on <a href="http://www.disobey.com/detergent/2002/extendingrss2/">extending RSS 2.0 with namespaces</a>, so I won't explain them here except to say that we use them, and you should get used to seeing them. Most RSS 2.0 documents you see will use namespaces in some way, because they are the primary way of adding functionality beyond the basic title-link-description combination. If all you want is title-link-description, stick with your existing RSS 0.91 template and stop reading now.</p>
<p>Still here? OK. Now, the <a href="http://backend.userland.com/rss">RSS 2.0 specification</a> says nothing about how to actually use namespaces in RSS, just that you're allowed to. So where did these particular namespaces come from? Well, I didn't make them up. They have been developed over the past two years by some smart people, most of whom hang out on the <a href="http://groups.yahoo.com/group/rss-dev/">RSS-DEV mailing list</a>. The namespaces were originally developed for RSS 1.0, and most of them can be used without modification in RSS 2.0. (There's a lot of stuff I'm skipping over here on purpose. There will be a lot more documentation forthcoming in the next few months on exactly how to use various namespaces in RSS 2.0. Some of it still needs to be worked out, but most of it just needs to be written down. Please be patient.)</p>
<p>So anyway, we use namespaces for a lot of stuff. Most stuff, in fact. In the template, you'll see title-link-description for <code>channel</code>, and title-link-description-guid for <code>item</code>. <code>guid</code> is new in RSS 2.0, and it is used to uniquely identify an item, so even if the title or description changes, aggregators know that it's the same item; the end user can choose whether to re-display changed items, but first programs need to be able to track which items are which. (<a href="http://radio.userland.com/">Radio Userland</a> already supports this.) To create the <code>guid</code>, I've combined <code>MTEntryID</code> with <code>MTBlogURL</code> to generate a unique string for each item, and I've arranged them so there's no confusion about it possibly being a URL. It's not a URL; it's just a unique string. (Other systems have stricter format requirements for guids, but RSS 2.0 does not. A guid is a unique string, and that's all.)</p>
<p>Pretty much everything beyond title-link-description (and guid) uses namespaces. This template makes use of all 3 of the <a href="http://purl.org/rss/1.0/modules/standard.html">standard RSS 1.0 namespaces</a>, but there are many other <a href="http://purl.org/rss/1.0/modules/proposed.html">proposed namespaces</a> that have a lot of good design behind them. We use one (<code>admin</code>), which is already widely used; the rest may be useful to you, depending on your niche. (If you think you need to design your own namespace, look through that list and make sure you're not re-inventing the wheel.)</p>
<p>Back to the template. Other than guid, the most important thing to note about this template is that the <code>title</code>, <code>link</code>, and <code>description</code> are all plain text. (<code>description</code> is an excerpt; if you do not enter an excerpt manually for a post, Movable Type will auto-generate one. You can control how long this auto-generated excerpt is by going to Blog Config, then Preferences, then <q>Number of words in excerpt</q>.) <code>title</code> was always supposed to be plain text, but sticking to plain text in the <code>description</code> tag is an intentional compromise, to support parsers that can not handle HTML, or handle it improperly. Never fear, the full HTML text of your post is still included; it's stored in the <code>content:encoded</code> element. (<a href="http://bitworking.org/Aggie.html">Aggie</a> already supports this.) This allows more robust news readers -- that can handle either text or HTML -- to offer the end user the choice of whether to see excerpts or full posts. Some people use news aggregators to find things to read, others like reading everything directly in their aggregator. RSS 0.9x made you (the author) choose one or the other; RSS 2.0 allows you to offer both, and pass the choice along to the end user. This is a good thing.</p>
<p>There's more good stuff in there, but the explanations will have to wait for another day. If you're interested in learning how to extend RSS to suit your needs, your best bet is to read through the documentation of the existing RSS 1.0 namespaces. If you have questions, your best bet is the <a href="http://groups.yahoo.com/group/rss-dev/">RSS-DEV mailing list</a>, where Kevin is currently <a href="http://groups.yahoo.com/group/rss-dev/message/4046">discussing his namespace primer</a>. Archives are public and free, so no subscription is required, and lurking is encouraged.</p>
<p>And watch this space.</p>]]>
70 -> </content:encoded>
71 ->
72 -> <dc:subject>
73 -> Weblogging
74 -> </dc:subject>
75 ->
76 -> <dc:date>
77 -> 2002-09-26T01:28:52-05:00
78 -> </dc:date>
79 ->
80 -> </item>
81 ->
82 -> <item>
83 ->
84 -> <title>
85 -> FOAF explorer
86 -> </title>
87 ->
88 -> <link>
89 -> http://diveintomark.org/archives/2002/09/25.html#foaf_explorer
90 -> </link>
91 ->
92 -> <description>
93 -> Morten Frederiksen has taken a first stab at a real-time social network explorer based on FOAF files. It's heavy on tech details, but you can easily see the potential here.
94 -> </description>
95 ->
96 -> <guid isPermaLink="false">
97 -> 1843@http://diveintomark.org/
98 -> </guid>
99 ->
100 -> <content:encoded>
101 -> <![CDATA[<p>Morten Frederiksen has taken a first stab at a real-time social network explorer based on FOAF files. You could <a href="http://xml.mfd-consult.dk/foaf/?foaf=http%3A%2F%2Fdiveintomark.org%2Fpublic%2Ffoaf.rdf">start on my profile</a> and explore from there, or enter the URL of your own FOAF file (at the bottom of the page). It's heavy on tech details, but you can easily see the potential here. (It's also a great way to debug your FOAF file, if you added anything manually.) Now we need somebody to build a spider that follows <code>foaf:knows</code> links and draws pretty social network diagrams, so we can see the forest for the trees.</p>]]>
102 -> </content:encoded>
103 ->
104 -> <dc:subject>
105 -> </dc:subject>
106 ->
107 -> <dc:date>
108 -> 2002-09-25T18:18:53-05:00
109 -> </dc:date>
110 ->
111 -> </item>
112 ->
113 -> <item>
114 ->
115 -> <title>
116 -> Maps
117 -> </title>
118 ->
119 -> <link>
120 -> http://diveintomark.org/archives/2002/09/25.html#maps
121 -> </link>
122 ->
123 -> <description>
124 -> Mark Tosczak @ Wired: A New Way to Read, Not See, Maps.
125 -> </description>
126 ->
127 -> <guid isPermaLink="false">
128 -> 1842@http://diveintomark.org/
129 -> </guid>
130 ->
131 -> <content:encoded>
132 -> <![CDATA[<p><cite title="Wired News">Mark Tosczak</cite>: <a href="http://www.wired.com/news/school/0,1383,54916,00.html">A New Way to Read, Not See, Maps</a>. <q>The map-navigation software, dubbed Blind Audio Tactile Mapping System ... takes digital map information and provides nonvisual feedback as a user moves a cursor across the map.</q></p>]]>
133 -> </content:encoded>
134 ->
135 -> <dc:subject>
136 -> Accessibility
137 -> </dc:subject>
138 ->
139 -> <dc:date>
140 -> 2002-09-25T10:45:15-05:00
141 -> </dc:date>
142 ->
143 -> </item>
144 ->
145 -> <item>
146 ->
147 -> <title>
148 -> Plan
149 -> </title>
150 ->
151 -> <link>
152 -> http://diveintomark.org/archives/2002/09/25.html#plan
153 -> </link>
154 ->
155 -> <description>
156 -> Paul Ford: Falling Off a Truck. "In the last 4 days I fell off a truck and was dragged for 30 feet, and was interviewed by an NPR show. Those two facts are not related except that they both happened to me and made me queasy. I also wrote a short plan outlining the rest of my life."
157 -> </description>
158 ->
159 -> <guid isPermaLink="false">
160 -> 1841@http://diveintomark.org/
161 -> </guid>
162 ->
163 -> <content:encoded>
164 -> <![CDATA[<p><cite>Paul Ford</cite>: <a href="http://ftrain.com/recent_update_etc.html">Falling Off a Truck</a>. <q>In the last 4 days I fell off a truck and was dragged for 30 feet, and was interviewed by an NPR show. Those two facts are not related except that they both happened to me and made me queasy. I also wrote a short plan outlining the rest of my life.</q></p>]]>
165 -> </content:encoded>
166 ->
167 -> <dc:subject>
168 -> Writers
169 -> </dc:subject>
170 ->
171 -> <dc:date>
172 -> 2002-09-25T10:43:06-05:00
173 -> </dc:date>
174 ->
175 -> </item>
176 ->
177 -> <item>
178 ->
179 -> <title>
180 -> RSS revolt
181 -> </title>
182 ->
183 -> <link>
184 -> http://diveintomark.org/archives/2002/09/25.html#rss_revolt
185 -> </link>
186 ->
187 -> <description>
188 -> People appear to be sick of the syndication format wars. Some are protesting, some are creating new formats with new names, others are simply boycotting.
189 -> </description>
190 ->
191 -> <guid isPermaLink="false">
192 -> 1840@http://diveintomark.org/
193 -> </guid>
194 ->
195 -> <content:encoded>
196 -> <![CDATA[<p><cite>Anil Dash</cite>: <a href="http://www.dashes.com/anil/index.php?archives/003183.php">XML version 1.0</a>. <q>Why isn't there a way to syndicate my words without butchering the way they look?</q> Several people protested last week by changing their weblog templates to <a href="http://www.dashes.com/anil/xmlindex.php">something like this</a>. <a href="http://q.queso.com/index.php?archives/001000.php">Jason Levine has more links</a> to those involved. I spoke with one of the people who implemented it, and she claims it wasn't a protest as such, more of an inside joke. Point taken: the entire point of an aggregator (and syndication in general) is to make everyone's words look the same. Counterpoint: the default in most weblog systems is to only publish excerpts in RSS feeds; nobody's forcing you to publish full posts. This would probably be a good place to insert a Zen quote about attachment, but my mind is too fuzzy to find it.</p>
<p><cite>Timothy Appnel</cite>: <a href="http://www.mplode.com/tima/archives/000107.html">More FFKAR, RDF, and FOAF</a>. FFKAR is <q>the format formerly known as RSS</q>. <a href="http://www.intertwingly.net/blog/840.html">Sam has already implemented it</a>.</p>
<p><cite>Nicholas Avenell</cite>: <a href="http://www.aquarionics.com/nodes/view.php?name=esf">ESF</a>. <q>Are you also fed up with the continuing war between RSS 0.9* and 1.0 and 2.0 and whatever else they invent today? Me too. So today I invented the Epistula Syndication Format. ESF. It isn't XML. It isn't RDF. It's just data.</q> <a href="http://www.intertwingly.net/blog/">Sam</a> would love it, then. But <a href="http://www.movabletype.org/docs/mtmanual_tags.html#date tag formats">Movable Type doesn't support outputting dates in Unix timestamp format</a>, which could be an impediment to mainstream acceptance.</p>
<p><cite>Shelley Powers</cite>: <a href="http://weblog.burningbird.net/archives/000544.php">Consumer Rights and RSS</a>. <q>I'm not buying into RSS 0.9x. I'm not buying into RSS 2.0. I'm not buying into RSS 1.0. I changed my RSS 0.91 and RSS 1.0 templates to read the following:</q></p>
<blockquote>
<p><strong>RSS not supported here</strong></p>
<p>This weblog does not support RSS 0.9x, RSS 2.0, or RSS 1.0. If you wish to view entries, may I suggest that you visit the weblog, and save your fast skimming for the New York Times and Wall Street Journal.</p>
</blockquote>
<p>I'm sure this is some sort of DMCA violation or something, but here goes:</p>
<blockquote>
<p><code>import urllib, re; print "<rss><channel>\n <title>Burningbird</title>\n <link>http://weblog.burningbird.net/</link>\n <language>en-us</language>\n </channel>\n" + "\n".join(["<item><title>%s</title><link>%s</link></item>" % t for t in re.compile(r'dc:title="(.*?)"\s*dc:identifier="(.*?)"', re.DOTALL).findall(urllib.urlopen('http://weblog.burningbird.net/').read())]) + "</rss>"</code></p>
</blockquote>
<p></p>]]>
197 -> </content:encoded>
198 ->
199 -> <dc:subject>
200 -> </dc:subject>
201 ->
202 -> <dc:date>
203 -> 2002-09-25T00:38:31-05:00
204 -> </dc:date>
205 ->
206 -> </item>
207 ->
208 -> <item>
209 ->
210 -> <title>
211 -> Stark raving sane
212 -> </title>
213 ->
214 -> <link>
215 -> http://diveintomark.org/archives/2002/09/24.html#stark_raving_sane
216 -> </link>
217 ->
218 -> <description>
219 -> Sam Ruby is stark raving mad.
220 -> </description>
221 ->
222 -> <guid isPermaLink="false">
223 -> 1839@http://diveintomark.org/
224 -> </guid>
225 ->
226 -> <content:encoded>
227 -> <![CDATA[<p><cite>Sam Ruby</cite>: <a href="http://www.intertwingly.net/blog/844.html">Stark raving mad</a>.</p>
<blockquote>
<p>This post was entered in Radio, extracted using a batch file via some UserTalk, parsed using Perl, cleaned up by tidy and a C program of my own design, transferred to intertwingly using scp, and then ssh triggers unpacking on the destination site, where a shell script takes over: invokes indexing using Jakarta's Lucene, and then a python script pings weblogs.com and blo.gs.</p>
</blockquote>
<p>Tom Stoppard (<cite>Rosencrantz and Guildenstern are Dead</cite>):</p>
<blockquote>
<p>Guildenstern: <q>A man talking sense to himself is no madder than a man talking nonsense not to himself.</q><br />
Rosencrantz: <q>Or just as mad.</q><br />
Guildenstern: <q>Or just as mad.</q><br />
Rosencrantz: <q>And he does both.</q><br />
Guildenstern: <q>So there you are.</q><br />
Rosencrantz: <q>Stark raving sane.</q></p>
</blockquote>
<p></p>]]>
228 -> </content:encoded>
229 ->
230 -> <dc:subject>
231 -> </dc:subject>
232 ->
233 -> <dc:date>
234 -> 2002-09-24T22:05:32-05:00
235 -> </dc:date>
236 ->
237 -> </item>
238 ->
239 -> <item>
240 ->
241 -> <title>
242 -> Parallels
243 -> </title>
244 ->
245 -> <link>
246 -> http://diveintomark.org/archives/2002/09/24.html#parallels
247 -> </link>
248 ->
249 -> <description>
250 -> Jeffrey Zeldman: "A couple of intellectuals have pointed out parallels between the rigidity of OS X, which derives its power from Unix and XML, and the rules of standards-based web development, which also compels you to do things the right way instead of using five different non-standard hacks."
251 -> </description>
252 ->
253 -> <guid isPermaLink="false">
254 -> 1838@http://diveintomark.org/
255 -> </guid>
256 ->
257 -> <content:encoded>
258 -> <![CDATA[<p><cite>Jeffrey Zeldman</cite>: <a href="http://www.zeldman.com/daily/0902a.html#osxbluesupdate">OS X Blues update</a>.</p>
<blockquote>
<p>A couple of intellectuals have pointed out parallels between the rigidity of OS X, which derives its power from Unix and XML, and the rules of standards-based web development, which also compels you to do things the right way instead of using five different non-standard hacks. The parallel is not without merit. Building web pages the right way is hard at first, but once you get it, you never want to go back. Regardless, we miss OS 9's flexibility and ease of use, and a metric ton of logic doesn't offset that feeling of loss.</p>
</blockquote>
<p></p>]]>
259 -> </content:encoded>
260 ->
261 -> <dc:subject>
262 -> </dc:subject>
263 ->
264 -> <dc:date>
265 -> 2002-09-24T20:38:57-05:00
266 -> </dc:date>
267 ->
268 -> </item>
269 ->
270 -> <item>
271 ->
272 -> <title>
273 -> DVD stills
274 -> </title>
275 ->
276 -> <link>
277 -> http://diveintomark.org/archives/2002/09/24.html#dvd_stills
278 -> </link>
279 ->
280 -> <description>
281 -> DVD Capture 1.0 is a helper application for the Apple DVD Player. It enables the user to take screen captures of the DVD Player Viewer in window and full screen mode. The captures can be saved to a file or placed on the clipboard.
282 -> </description>
283 ->
284 -> <guid isPermaLink="false">
285 -> 1837@http://diveintomark.org/
286 -> </guid>
287 ->
288 -> <content:encoded>
289 -> <![CDATA[<p><a href="http://www.versiontracker.com/dyn/moreinfo/macosx/16324">DVD Capture 1.0</a> <q>is a helper application for the Apple DVD Player. It enables the user to take screen captures of the DVD Player Viewer in window and full screen mode. The captures can be saved to a file or placed on the clipboard.</q></p>]]>
290 -> </content:encoded>
291 ->
292 -> <dc:subject>
293 -> Apple
294 -> </dc:subject>
295 ->
296 -> <dc:date>
297 -> 2002-09-24T13:49:41-05:00
298 -> </dc:date>
299 ->
300 -> </item>
301 ->
302 -> <item>
303 ->
304 -> <title>
305 -> Light reading
306 -> </title>
307 ->
308 -> <link>
309 -> http://diveintomark.org/archives/2002/09/24.html#light_reading
310 -> </link>
311 ->
312 -> <description>
313 -> Phil Ringnalda: "Putting on the brakes". Aaron Swartz: "TRAMP: Makes RDF look like Python data structures". Dan Connolly: "HyperRDF: Using XHTML Authoring Tools with XSLT to produce RDF schemas".
314 -> </description>
315 ->
316 -> <guid isPermaLink="false">
317 -> 1836@http://diveintomark.org/
318 -> </guid>
319 ->
320 -> <content:encoded>
321 -> <![CDATA[<p></p>
<ul>
<li><cite>Phil Ringnalda</cite>: <a href="http://philringnalda.com/archives/002330.php">Putting on the brakes</a>. <q>So, the answer to the question that started this whole project, "what is the RDF in RSS 1.0 good for?" is two things: it's good for someone who has an infinitely large database that can be queried infinitely fast by a schema-aware program, or it's good for writing a schema-aware aggregator that can try to figure out what it should do with new elements that it hasn't seen before. That's actually an interesting project with some potential for success, but at this point I'm sick of the whole thing, so I'll leave that project for someone else.</q></li>
<li><cite>Aaron Swartz</cite>: <a href="http://www.aaronsw.com/2002/tramp">TRAMP: Makes RDF look like Python data structures</a>. <q>RDF/XML got you down? Tired of having to go through contortions to deal with data? Want to write Python and be standards-compatible at the same time? Need a module to implement the psuedo-code you had on your slides? TRAMP may or may not be the answer to these problems!</q> Complete with an example of parsing FOAF files.</li>
<li><cite>Dan Connolly</cite>: <a href="http://www.w3.org/2000/07/hs78/">HyperRDF: Using XHTML Authoring Tools with XSLT to produce RDF schemas</a>. <q>XML syntax is a little tedious, but lots of people are evidently willing and able of editing it by hand. RDF adds another layer of tedium, but there are still a few folks willing to write it by hand. I make heavy use of reification/quoting in my representation of logical formulas in RDF. This adds another layer of tedium that I find unmanageable, and I have been writing XML/SGML/HTML by hand for 10 years.</q> Also includes a cogent explanation of the obscure <code>profile</code> attribute in HTML.</li>
</ul>
<p></p>]]>
322 -> </content:encoded>
323 ->
324 -> <dc:subject>
325 -> </dc:subject>
326 ->
327 -> <dc:date>
328 -> 2002-09-24T10:46:15-05:00
329 -> </dc:date>
330 ->
331 -> </item>
332 ->
333 -> <item>
334 ->
335 -> <title>
336 -> New toys
337 -> </title>
338 ->
339 -> <link>
340 -> http://diveintomark.org/archives/2002/09/23.html#new_toys
341 -> </link>
342 ->
343 -> <description>
344 -> Shelley Powers: "I thought the stuff this weekend on FOAF was a joke -- a bunch of people playing with new toys."
345 -> </description>
346 ->
347 -> <guid isPermaLink="false">
348 -> 1834@http://diveintomark.org/
349 -> </guid>
350 ->
351 -> <content:encoded>
352 -> <![CDATA[<p><cite>Shelley Powers</cite>: <q><a href="http://groups.yahoo.com/group/rss-dev/message/3981">I thought the stuff this weekend on FOAF was a joke</a> -- a bunch of people playing with new toys. ... How does FOAF aid aggregation? The author is included with each bit. Why do we need extraneous material such as college, and who the author knows?</q></p>
<p><cite>Seth Russell</cite>: <q><a href="http://groups.yahoo.com/group/rss-dev/message/3982">For example I wanted to know who <em>you</em> were</a>. Only thing I had was your posts to this list. So i found "burningbird.net" in your email address ... then i did a lot of reading over there. Still don't really know who your are and what you are into, what projects you are working on, who you know, and why you came here to run your mouth. But if there were a foaf button on the feed from this channel, well I just click on that and i'm totally into your stuff.</q></p>]]>
353 -> </content:encoded>
354 ->
355 -> <dc:subject>
356 -> </dc:subject>
357 ->
358 -> <dc:date>
359 -> 2002-09-23T16:50:42-05:00
360 -> </dc:date>
361 ->
362 -> </item>
363 ->
364 -> <item>
365 ->
366 -> <title>
367 -> Now heavily medicated
368 -> </title>
369 ->
370 -> <link>
371 -> http://diveintomark.org/archives/2002/09/23.html#now_heavily_medicated
372 -> </link>
373 ->
374 -> <description>
375 -> Trust me when I tell you that heavy medication and RDF do not mix. Here is a list of things I intend to re-read once the fog lifts.
376 -> </description>
377 ->
378 -> <guid isPermaLink="false">
379 -> 1833@http://diveintomark.org/
380 -> </guid>
381 ->
382 -> <content:encoded>
383 -> <![CDATA[<p>Trust me when I tell you that heavy medication and RDF do not mix. Here is a list of things I intend to re-read once the fog lifts:</p>
<ul>
<li><cite>Phil Ringnalda</cite>: <a href="http://philringnalda.com/archives/002324.php">Using FOAF relationships</a> and <a href="http://philringnalda.com/archives/002329.php">Just say no to Trackback in <code>index.html</code></a>.</li>
<li><cite>Les Orchard</cite>: <a href="http://www.decafbad.com/news_archives/000290.phtml">Per-post comment RSS feed</a>.</li>
<li><cite>Phil Wainewright</cite>: <a href="http://howto.looselycoupled.com/blog/2002_09_15_dy.htm">The bare necessities of RSS</a> and <a href="http://howto.looselycoupled.com/blog/2002_09_22_dy.htm#85480973">What to do about RDF</a>. The beginning of an RSS 2.0 best practices document.</li>
<li><cite>Jonathon Delacour</cite>: <a href="http://weblog.delacour.net/archives/000707.html">Trying to score a goal</a>. <q>As the best and the brightest focus on the possibilities of FOAF, I turned my attention to yesterday's news: RSS.</q> No, RSS will always be today's news. Get it? Today's newzzz... Never mind.</li>
<li>Comments on <a href="http://rss.benhammersley.com/archives/001387.html">Ben Hammersley's Friend of a Friend</a>. Various ways to link to a FOAF file from an RSS feed.</li>
<li><cite title="IBM developerWorks">Nicholas Chase</cite>: <a href="http://www-106.ibm.com/developerworks/library/wa-xhtml/?n-wa-9192">The Web's future: XHTML 2.0</a>. We're losing backward compatibility, isn't that great? Well, he seems to think so.</li>
<li><a href="http://web.resource.org/rss/1.0/modules/cc/">mod_cc</a>, a module for including copyright information in RDF documents such as RSS 1.0 feeds, and, I hope, FOAF files.</li>
<li><cite>Shelley Powers</cite>: <a href="http://weblog.burningbird.net/archives/000541.php">Who is your audience, and what are you trying to accomplish?</a> Addressing the growing identity crisis on the <a href="http://groups.yahoo.com/group/rss-dev/">RSS-DEV mailing list</a>. Also the <a href="http://burningbird.net/cgi-bin/mt-comments.cgi?entry_id=541">comments on Shelley's article</a>.</li>
<li><cite>Ian Hickson</cite>: <a href="http://ln.hixie.ch/?start=1032794857&count=1">Pingback 1.0</a>. <q>The best thing about this idea is that unlike similar schemes like TrackBack, it is totally transparent to both users.</q></li>
<li><a href="http://maccentral.macworld.com/news/0209/23.usable.php">New software helps in building of accessible web sites</a>. A press release for a new edition of <a href="http://www.usablenet.com/">LIFT</a>, which I have never used.</li>
<li><a href="http://www.globeandmail.com/servlet/ArticleNews/PEstory/TGAM/20020923/UFATTN/Headlines/headdex/headdexInternational_temp/13/13/22/">Forget Mars bars, Twinkies now the deep-fried treat</a>. <q>The secret to making a deep-fried Twinkie, he says, is to place it in the fridge first to give it more stability. He then rolls it in flour, covers it with batter ... and plunks it into the oil.</q></li>
</ul>
<p></p>]]>
384 -> </content:encoded>
385 ->
386 -> <dc:subject>
387 -> </dc:subject>
388 ->
389 -> <dc:date>
390 -> 2002-09-23T16:11:02-05:00
391 -> </dc:date>
392 ->
393 -> </item>
394 ->
395 -> <item>
396 ->
397 -> <title>
398 -> The Semantic Web makes me sick
399 -> </title>
400 ->
401 -> <link>
402 -> http://diveintomark.org/archives/2002/09/23.html#the_semantic_web_makes_me_sick
403 -> </link>
404 ->
405 -> <description>
406 -> No, really. My sinus infection, which appeared to be gone, flared up again over the weekend in the nastiest way.
407 -> </description>
408 ->
409 -> <guid isPermaLink="false">
410 -> 1832@http://diveintomark.org/
411 -> </guid>
412 ->
413 -> <content:encoded>
414 -> <![CDATA[<p>No, really. My sinus infection, which appeared to be gone, flared up again over the weekend in the nastiest way, and I am now coughing up dark mucus and doing other things that probably don't bear repeating in a public forum. I have the 10:15 doctor's appointment that I should have made last round, had I not convinced myself that <q>it's not that bad</q> and trudged through it all without prescription drugs. I'm not making the same mistake this time. I'll be back this afternoon.</p>
<p>My email problems of yesterday have been resolved. You can once again reach me at my normal address, f8dy@diveintomark.org.</p>
<p><a href="http://www.peerfear.org/">Kevin Burton</a> emailed me with another way to link to a FOAF file from my RSS feed. It looks easier than previous suggestions, and it has the advantage of being able to use it from an RSS 1.0 or 2.0 feed, but I worry about all these variations. Just as in real life, where people can use different words that mean essentially the same thing, in the Semantic Web programs can use different vocabularies to express the same statements. That's great for producers, not so great for consumers who have to make sense of it all.</p>
<p>For each domain (RSS feeds, FOAF files, whatever), somebody (or some group) needs to come along and document best practices. We need better <em>goal-oriented</em> documentation. We have a lot of reference documentation, task-oriented documentation, but very little that documents that larger picture and answers questions written in English. <q>How do I include personal information in my RSS feed?</q> is a goal-oriented question. <q>Create a FOAF file using this tool and then insert this line at this location in your RSS feed</q> (with as many examples as necessary) is a goal-oriented answer. Anything less is like trying to master a foreign language by reading a dictionary.</p>]]>
415 -> </content:encoded>
416 ->
417 -> <dc:subject>
418 -> </dc:subject>
419 ->
420 -> <dc:date>
421 -> 2002-09-23T09:27:30-05:00
422 -> </dc:date>
423 ->
424 -> </item>
425 ->
426 -> <item>
427 ->
428 -> <title>
429 -> Advanced FOAF
430 -> </title>
431 ->
432 -> <link>
433 -> http://diveintomark.org/archives/2002/09/22.html#advanced_foaf
434 -> </link>
435 ->
436 -> <description>
437 -> Ben Hammersley: FOAF to vCard converter. Also, some thoughts on what additional information would be useful to include in a FOAF profile, and what we could do with it.
438 -> </description>
439 ->
440 -> <guid isPermaLink="false">
441 -> 1831@http://diveintomark.org/
442 -> </guid>
443 ->
444 -> <content:encoded>
445 -> <![CDATA[<p><cite>Ben Hammersley</cite>: <a href="http://rss.benhammersley.com/archives/001393.html">FOAF to vCard</a>. <q>It's so alpha as to be almost pitiful, but this widget may well give you a vCard file from a FOAF file. You can then import the vCard into Outlook, OSX AddressBook and any other vCard compatible app.</q></p>
<p>Meanwhile, <a href="http://www.kungfugrippe.com/">Merlin Mann</a>, in email, states <q>Most folks' eyes (understandably) glaze over when I start rhapsodizing about
RSS self-discovery and Amazon APIs. But it's pretty cool if you say, "People
who visit your home page can instantly know you went to college together and
now live in the same town." That's transparently pretty neat.</q></p>
<p>To that end, I've put some more information into <a href="http://diveintomark.org/public/foaf.rdf">my FOAF profile</a>, including <code>foaf:schoolHomepage</code> (<a href="http://www.earlham.edu/">Earlham</a>), and <code>foaf:currentProject</code> for information about my current projects (<a href="http://diveintopython.org/">Dive Into Python</a>, <a href="http://diveintoosx.org/">Dive Into OS X</a>, <a href="http://diveintoaccessibility.org/">Dive Into Accessibility</a>). I'd like to use the <a href="http://www.creativecommons.org/">Creative Commons</a> framework to specify the copyright information for each of these projects, but I can't quite figure out how to specify that a project is governed by the <a href="http://www.gnu.org/copyleft/fdl.html">GNU Free Documentation License</a>. Let's see, who's the guru with this stuff? <a href="http://www.aaronsw.com/weblog/">Aaron</a>, I think. Must ask Aaron.</p>]]>
446 -> </content:encoded>
447 ->
448 -> <dc:subject>
449 -> </dc:subject>
450 ->
451 -> <dc:date>
452 -> 2002-09-22T21:00:57-05:00
453 -> </dc:date>
454 ->
455 -> </item>
456 ->
457 -> <item>
458 ->
459 -> <title>
460 -> FOAF, FOAF, FOAF
461 -> </title>
462 ->
463 -> <link>
464 -> http://diveintomark.org/archives/2002/09/22.html#foaf_foaf_foaf
465 -> </link>
466 ->
467 -> <description>
468 -> I want a FOAF-aware RSS aggregator that gives me a rick-click "about the author" option that shows me their FOAF data and all the people they know -- and then offers to subscribe to their RSS feeds.
469 -> </description>
470 ->
471 -> <guid isPermaLink="false">
472 -> 1830@http://diveintomark.org/
473 -> </guid>
474 ->
475 -> <content:encoded>
476 -> <![CDATA[<p><cite>Timothy Appnel</cite>: <a href="http://www.mplode.com/tima/archives/000107.html">More FFKAR, RDF, and FOAF</a>.</p>
<p><a href="http://tesugen.com/foaf.rdf">Peter Lindberg's FOAF</a>. (See also: Peter's thoughts on a <a href="http://tesugen.com/2002/09/20.html#smartrssreeder">Smart RSS Reader</a>.)</p>
<p><a href="http://www.pocketsoap.com/weblog/foaf.rdf">Simon Fell's FOAF</a>.</p>
<p><a href="http://www.praytothemachine.com/evil/foaf-tyler-weir.rdf">Tyler Weir's FOAF</a>.</p>
<p><a href="http://www.kungfugrippe.com/foaf.rdf">Merlin Mann's FOAF</a>. Merlin calls it a <a href="http://www.kungfugrippe.com/archives/2002/09/22/index.php#001685">FOAF Bandwagon</a>, which probably overstates the case somewhat. ;-) As for the possibilities of what we could build if we all had FOAF files: <q>Imagine international, real-time popularity contests. It'd be like middle school with 4 billion people.</q> We already have that; it's called <a href="http://www.google.com/search?q=merlin+mann">Google</a>.</p>
<p>Hmm, on second thought, maybe it is a bandwagon. We already have <a href="http://jogin.com/world/archives/000116.php">the inevitable backlash</a>. <q>Spammers might not even give two cents about what your interests are, but they will care about a vast free network of email-addresses and URLs. Even if the email-address is encoded (it is), it's only a slight disturbance to the Darth Vaders of marketing if you share what URL to scan for email-addresses.</q> Um, no. Spammers are not discriminating enough to care about <q>webs of trust</q>, and they already have lots of non-Semantic-Web ways of finding email addresses. And more sophisticated direct marketers are much too sophisticated to trust self-reported data.</p>
<p>Over at <a href="http://rss.benhammersley.com/">Ben Hammersley's pad</a>, we're discussing <a href="http://rss.benhammersley.com/archives/001387.html">how to link FOAF and RSS</a> in both directions (pointing to your RSS feed from your FOAF file, and pointing to your FOAF file from your RSS feed), plus how to link FOAF and HTML (ala <a href="http://diveintomark.org/archives/2002/06/02.html#important_change_to_the_link_tag">RSS autodiscovery</a>). A couple of ideas in all directions, although for linking <em>from</em> RSS <em>to</em> FOAF, I would prefer a simple syntax that is valid RDF but would also work in an RSS 2.0 feed. Then I want a FOAF-aware RSS aggregator that gives me a right-click <q>about the author</q> option that shows me their FOAF data and all the people they know -- and then offers to subscribe to <em>their</em> RSS feeds. I get all <a href="http://www.intertwingly.net/blog/">intertwingly</a> just thinking about it.</p>
<p>Meanwhile, over at <a href="http://philringnalda.com/">Phil Ringnalda's pad</a>, we're discussing <a href="http://philringnalda.com/archives/002323.php">how to list your enemies</a> in a FOAF file, using Eric Vitiello's <a href="http://www.perceive.net/schemas/20020729/relationship/">FOAF relationship module</a>. The syntax seems simple enough (replace <code>foaf:knows</code> with <code>rel:enemyOf</code>), but it raises interesting questions about adding too much complexity for implementors, leaving it up to the developer of the consuming application to understand the semantic relationships between all of these related vocabularies. I'm pretty sure I'm still missing several pieces of this puzzle.</p>]]>
477 -> </content:encoded>
478 ->
479 -> <dc:subject>
480 -> </dc:subject>
481 ->
482 -> <dc:date>
483 -> 2002-09-22T14:11:27-05:00
484 -> </dc:date>
485 ->
486 -> </item>
487 ->
488 -> <item>
489 ->
490 -> <title>
491 -> Email issues
492 -> </title>
493 ->
494 -> <link>
495 -> http://diveintomark.org/archives/2002/09/22.html#email_issues
496 -> </link>
497 ->
498 -> <description>
499 -> I am having email issues. Please use f8dy@yahoo.com if you want to reach me today.
500 -> </description>
501 ->
502 -> <guid isPermaLink="false">
503 -> 1829@http://diveintomark.org/
504 -> </guid>
505 ->
506 -> <content:encoded>
507 -> <![CDATA[<p>I am having email issues. Please use f8dy@yahoo.com if you want to reach me today.</p>]]>
508 -> </content:encoded>
509 ->
510 -> <dc:subject>
511 -> </dc:subject>
512 ->
513 -> <dc:date>
514 -> 2002-09-22T13:08:29-05:00
515 -> </dc:date>
516 ->
517 -> </item>
518 ->
519 -> </channel>
520 ->
521 -> </rss>
522 ->