Curiouser and Curiouser!

Curiouser and Curiouser! on ent http://matt.blogs.it/ RSS feed for topic ent Copyright 2006 Matt Mower Squib/0.1 self@mattmower.com self@mattmower.com en-gb PURL's and the ENT URL Sat, 12 Apr 2003 09:11:22 +0100 I've noticed quite a few people publishing the ENT 1.0 spec url as: <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <A href="http://matt.blogs.it/specs/ENT/1.0/">http://matt.blogs.it/specs/ENT/1.0/</A></BLOCKQUOTE> which is quite understandable because that is, for now, where the document lives.  It's, probably, also the URL your browser shows when you view the spec.  However the proper URL for the spec is: <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <A href="http://www.purl.org/NET/ENT/1.0/">http://www.purl.org/NET/ENT/1.0/</A></BLOCKQUOTE> This is a <A href="http://purl.oclc.org/docs/new_purl_summary.html">PURL</A> or permanent url. A PURL is like a regular URL except that it is managed by a redirection server.  When you create a PURL you decide what it should be called & where it should point.  Whenever a browser tries to load the PURL the PURL server automatically redirects the browser to the actual target URL. This means that when, for example, we move the ENT spec to a more permanent home we can change where it's PURL points and the link doesn't break.  It still points to the right place.  PURLs are a powerful way to use redirection in advance. Oh by the way.  Anybody can create them.  Just go to <A href="http://www.purl.org">www.purl.org</A>, register and away you go. However, for this reason, it is important that the spec is always referred to by it's PURL and not by any particular URL at which it is found.  We would be grateful if you could check and see which URL you have used. http://matt.blogs.it/entries/00001382.html How ENT could come to the rescue of mySubscriptions.opml Sat, 12 Apr 2003 10:23:56 +0100 Chris Pirillo <A href="http://chris.pirillo.com/archives/2003_04.html#000906">commented</A> on the <A href="http://www.purl.org/NET/ENT/1.0/">ENT</A> announcement.  At the same time he talked about a better facility for categorizing his RSS subscription list (held in an OPML document). While ENT is doing something different (it's categorizing individual items within a feed) I can see how ENT might help to solve Chris' problem too.  An ENT enabled feed holds topics about the items it contains.  Over time it would be possible to analyze the topics and come to some conclusions about what the feed is about. It would then be possible for software to automatically categorize each feed in the subscription list, based upon their content. Does that sound like a solution to your problem Chris? I'm not saying this would be a trivial problem... but it would be a big step closer to solving it.  Of course it requires that lots of people use ENT and, hence, that lots of tools support it.  We're working on that ;-)   http://matt.blogs.it/entries/00001383.html liveTopics 1.1.3 now supports ENT Tue, 15 Apr 2003 11:38:34 +0100 Pretty soon I will be displaying the new <A href="http://www.purl.org/NET/ENT/1.0/">ENT 1.0</A> logo <%radio.macros.imageRef( "/images/rssent.gif" )%> (courtesy of <A href="http://paolo.evectors.it/">Paolo</A>) on this page as my <A href="http://matt.blogs.it/rss.xml">feed</A> is now compliant. http://matt.blogs.it/entries/00001385.html Getting ready for the 2nd public ENT draft Tue, 15 Apr 2003 12:06:42 +0100 I'd like to publish the 2nd public draft of the ENT1.0 specification soon.  Today if I can.  There have been a couple of clarifications, a fix to the examples (thanks to Phil Pearson) and a couple of issues to be cleared up. <UL> <LI>The spec says that a topic ID must look like an XML NAME.  XML NAME is quite a restrictive set of characters and it looks like it wasn't such a good choice.  For example <A href="http://www.tbray.org/ongoing/">Tim Bray</A> wants to use topic names like sports/baseball/NYMets and XML NAME won't let him do that (I personally don't agree with him about his topic, but that's okay).  He suggests using something from the <A href="http://www.w3.org/International/iri-edit/">Internationized Resource Identifer (IRI)</A> specification because topic ID's are likely to end up as parts of URI's.  Good thinking Tim!  So, on this note, I propose changing the XML NAME defintion to IRI ifragment.  Does anyone have any comment about this? </LI> <LI>I have some concern that the use of namespaced attributes, e.g. <ent:cloud ent:href=""> instead of <ent:cloud href=""> may cause some people problems.  It's perfectly valid XML but people aren't used to seeing attributes in namespaces and it may prove to be confusing.  Since we are trying to keep ENT simple and since I don't think it will matter too much either way, I am considering dropping the namespace on the attributes.  Does anyone have any comment about this?</LI></UL> We look forward to your comments. http://matt.blogs.it/entries/00001387.html I mean, do people want fire that can be fitted nasally? Tue, 15 Apr 2003 12:17:48 +0100 I've been having an agreeable chat with, among others, <A href="http://dannyayers.com/">Danny Ayers</A> about <A href="http://www.purl.org/NET/ENT/1.0/">ENT</A>, <A href="http://www.w3.org/TR/rdf-primer">RDF</A>, and ThreadsML.  Danny expressed some concerns about the dangers of re-inventing wheels.  I share his concern although our viewpoints are perhaps a little different. I want to share part of one my messages: <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> My view is that RDF is a great way of doing things as long as it is wrapped with 1st rate tool support and matched with applications that warrant it. So far as I can tell both of those are near to non-existant right now and RDF remains primarily the domain of "those people who are interested in RDF and think it is a good idea," with a few exceptions. Back when Paolo and I were tossing this idea around we carefully thought over "are we re-inventing RDF" and came to the answer: "no." ENT is, by comparison, pretty simple/limited compared to RDF. But right now I think simplicity is more valuable thanpower. We are still in the early stages of building the semantic web and, really, the applications we have don't *need* RDF's power right now. We think ENT is "just good enough" to launch a raft of exciting applications. I fully expect though, that those applications will grow too big for ENT and simple "hard-wired" standards like it. But this demand will, perhaps, lead to an awakening about RDF. It's time will have come because there will be applications that justify it's complexity & the perceived benefits of those applications will be enough to overcome the inertia involved in getting started with it. And, hopefully, by that time the RDF folks will have delivered much more solidly on the tools front ;) In short my belief is that simple, focused, standards now will pave the way for the adoption of more powerful standards later. Also, as I have stated before, I don't think that RDF will really hit a home run until OWL is ready for prime-time. </BLOCKQUOTE> http://matt.blogs.it/entries/00001389.html Yahoo and ENT? Wed, 16 Apr 2003 10:04:04 +0100 <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <BLOCKQUOTE> <IMG src="http://www.radwin.org/michael/blog/archives/ask1.gif" align=left><A href="http://www.radwin.org/michael/blog/archives/000198.html">ask.yahoo.com RSS beta</A>. Ask Yahoo!, a daily column that features Q&A with Yahoo!'s expert team of Surfers, is now syndicating its content via RSS. Here's the link to the RSS file: <A href="http://ask.yahoo.com/ask/index.xml"><IMG src="http://www.radwin.org/images/xml.gif" border=0></A> [<A href="http://www.radwin.org/michael/blog/">Michael J. Radwin's blog</A>] </BLOCKQUOTE> Hey hey -- some RSS action from Yahoo -- subscribe now so they know we're out here! [<A href="http://radio.weblogs.com/0100875/">Brain Off</A>]</BLOCKQUOTE> I've subscribed, sight unseen.  Now wouldn't this be a great feed to have topics?  So you could see the Q&A that really mattered to you.  And Yahoo! already have a taxonomy. http://matt.blogs.it/entries/00001392.html TopicExchange does ENT Wed, 16 Apr 2003 17:25:04 +0100 <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <A href="http://www.myelin.co.nz/post/2003/4/16/#200304161">New RSS features on topicexchange.com</A>. A minor (but very handy) change to the <A href="http://topicexchange.com/">Internet Topic Exchange</A> today: it now supports <A href="http://matt.blogs.it/2003/04/11.html#a862">ENT</A> (<A href="http://www.purl.org/NET/ENT/1.0/">spec</A>), which means suitably equipped aggregators will be able to pull topic information straight out of the RSS feeds. Making this actually useful is a new RSS feed: <A href="http://topicexchange.com/rss">all posts on the site</A>. If you want to keep track of everything, subscribe to that one (traffic on the Exchange is still not awfully high, so you won't find yourself overwhelmed). An aggregator which understands topics will be able to just pull down this one RSS feed instead of heaps of individual topic channel feeds. The most interesting bit is yet to come: I've been contacted by <A href="http://www.feedster.com/">Scott Johnston</A> and <A href="http://www.blogdigger.com/index.html">Greg Gershman</A>, who both seem interested in using Topic Exchange information to do some sort of classification of search results. Sort of like the way <A href="http://www.google.com/">Google</A> uses <A href="http://dmoz.org/">dmoz</A> to give you links to relevant categories when you search. This functionality is yet to come, but the hooks are there in the Topic Exchange, so any developers are welcome to start using them from now on! For people who are interested in using this, I've written a page to explain <A href="http://topicexchange.com/doc/indexing">how to handle the data</A>. Enjoy! <A title="Click here to comment on this post." href="http://www.myelin.co.nz/phil/pss/comments.php?u=2&p=200304161&link=http://www.myelin.co.nz/post/2003/4/16/#200304161">Comment</A> [<A href="http://www.myelin.co.nz/post/">Second p0st</A>]</BLOCKQUOTE> This is fantastic news.  Well done Phil! http://matt.blogs.it/entries/00001399.html MyRadio gets ENT Mon, 21 Apr 2003 09:45:18 +0100 <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <A href="http://radio.weblogs.com/0100875/2003/04/17.html#a932">myRadio supports ENT 1.0</A>. My<IMG src="http://radio.weblogs.com/0100875/images/radioBadge.gif"> supports <A href="http://matt.blogs.it/specs/ENT/1.0/"><IMG src="http://matt.blogs.it/specs/ENT/1.0/ENT10-small.gif" border=0></A> Announcing the release of <A href="http://matt.blogs.it/specs/ENT/1.0/ENT10-small.gif">ENT 1.0</A> (Easy News Topics) support in <A href="http://radio.weblogs.com/0100875/outlines/myRadio/">myRadio</A>. One of the stated goals of ENT is to "represent topics sufficiently that they be useful in enabling smart aggregators (e.g. filtering, recombining feeds, etc...)". RSS+ENT feeds can be filtered in myRadio, by selecting topics of interest. Available topics for a feed are those seen by the aggregator, in the RSS feed. That list will grow in time. Later, myRadio will support topicRolls for this purpose. Future features may also include recombining feeds according to topic. Update myRadio.root in RU, or download the latest <A href="http://radio.weblogs.com/0100875/gems/myRadio.root">here</A>. Configure using the "Edit Topics" link in the myRadio navigation bar. Please contact me with any feedback, suggestions, and bug reports. Currently, the only known feeds supporting ENT 1.0 are <A href="http://matt.blogs.it/rss.xml">Curiouser and curiouser</A> and <A href="http://topicexchange.com/rss">Topic Exchange</A>. ENT enabled feeds should increase greatly when liveTopics 1.3.3 is released. [<A href="http://radio.weblogs.com/0100875/">Brain Off</A>]</BLOCKQUOTE> Fantastic news.  Well done Mikel. This will be the first application in the hands of users that will let them get the benefit of topics in their feeds.  liveTopics 1.1.3 is in beta at the moment and should be available soon.  Once that happens there will be a small cluster of feeds that do support ENT.  But we need to do more. Specifically we need to find a way to get at the hordes of MovableType users and get them in the game.   http://matt.blogs.it/entries/00001410.html David Sifry on ENT Mon, 21 Apr 2003 10:01:27 +0100 <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <A href="http://www.sifry.com/alerts/archives/000282.html">Easy News Topics</A>. Last week, Paolo Valdermarin and Matt Mower released their specification of Easy News Topics 1.0 (ENT), which is designed as an RSS 2.0 module that can add topic and categorization information to an RSS feed.  I committed to get back to them (and others) with a review and some commentary on the approach. The good news: As a format, ENT is easy to understand, easy for application developers to implement, and pretty easy to parse.  Kudos to Matt and Paolo for coming up with a design that is simple but extensible.  Now the bad news:  I'm worried about two issues.  First is the problem of self-categorization.  ENT presupposes that authors can successfully create microcontent with the following properties: It can be placed in one or more categories the author is qualified to categorize the content correctly the author's categories have meaning to the reader In addition, we then run into a larger problem with self-categorization, which is the question of categorization across feeds.  In other words, we have a problem of definitions - one person's rebel is another person's revolutionary.  Even with ENT's inclusion of clouds, which are (potentially) external topic maps that create self-consistent maps of the world, we still have the problem of intentional or unintentional misunderstanding and misreading of metadata like categories, which leads me to think that the entire concept of self-categorization is extremely difficult to work on a large scale. A good example of this failure to scale is the history of web page... [<A href="http://www.sifry.com/alerts/">Sifry's Alerts</A>]</BLOCKQUOTE> David presents a good analysis of <A href="http://www.purl.org/NET/ENT/1.0/">ENT 1.0</A> and, as you would expect from David, some of the wider issues around self-categorization of data.   In particular he compares a future of users adding topics to their RSS feeds to the abuse of META tags in HTML.  It's a point worth discussing: Off the cuff I can see two potential arguments to suggest that this won't be a big problem. <OL> <LI>ENT is not designed only for self-categorization of feeds.  Yes that's how we intend to use it, and certainly I think a lot of people will use it that way.  But ENT could just as easily be used by a categorizer bot that sucked in feeds and annotated them (using heuristics) with topics from it's own cloud.  This thought has lead me to wonder if there is some need for authorizing the use of a cloud.  Would you trust Googlebot to add topics to RSS feeds?  Or Feedster bot?</LI> <LI>As David points out, the solution to the META problem, as wrought by Google, was to bring an element of the social into the mix.  He rightly, I think, indicates that a solution to the eventual problems of metadata in RSS will probably be social also.  There has been a lot of talk recently about identity and reputation systems.  Blogging tends to be very much more personable than ever web publishing was before.  I read sites because they are meaningful to me.  If your categorization isn't, I probably won't read you for long.</LI></OL> http://matt.blogs.it/entries/00001415.html Aliases in ENT Tue, 22 Apr 2003 13:10:21 +0100 <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <A href="http://alevin.com/weblog/archives/001073.html">All Categories are Local</A>. Dave Sifry comments about the draft specification of Easy News Topics 1.0 (ENT), proposed by Paolo Valdermarin and Matt Mower.... [<A href="http://alevin.com/weblog/">BookBlog</A>]</BLOCKQUOTE> Adina's feed doesn't carry the whole post so: <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> Dave is concerned that a category standard would fall prey to the problems of ambiguity and scamming that killed HTML META tags. As I noted in comments on his post, Dave is absolutely right at the scale of the web or the blogosphere. However, I think that categories will be much more valuable at the community level. For example, Austin has a <A href="http://www.austinbloggers.org/">meta-blog</A>, aggregating posts related to Austin. People in other cities are starting to do the same. If we could map sub-categories, we would be able to create a cross-regional directory. There are local editors who keep the system from being spammed, and make decisions about how to map categories. So, I think that the system can work in the context of defined groups and defined applications. The only thing that ENT is missing is a way to alias categories -- Austin's "music events" maps to Ann Arbor's "concerts." Presumably this could be implemented at the application level.</BLOCKQUOTE> Aliasing topics is a powerful, and sometimes complicated, concept so we choose to leave it out of the <A href="http://www.purl.org/NET/ENT/1.0/">ENT</A> spec.  We took the view that this issue was best resolved by using a proper topic map behind the ENT <TT>cloud</TT>.  However if the functionality is needed and we can find a simple way to do it, we're open to that - especially while the spec is still in at the draft stage. The <A href="http://www.xfml.org/">XFML</A> standard, for example, provides a <A href="http://www.xfml.org/spec/1.0.html#connectingtopicsconcept"><TT><connect></TT></A> tag which can be used to explicitly link a topic in one document to the same topic in another document.  ENT could just duplicate this facility.  But what would it be connecting to? In XFML the answer is easy.  An XFML topics in one document connects to an XFML topic in another document.  Similarly for XTM the implication is that you make associations with other XTM topics.  But ENT topics are transient things that live for a short while in an RSS feed.  So logically you wouldn't connect an instance of an ENT topic in one feed to an instance of an ENT topic in another feed.  Would you?  Apart from the fact that I know of no way to address an arbitrary element in an RSS feed I think it far more likely that you want to alias the use of the topic to a fixed point of reference, e.g. <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> When you see "music event" in the Austin feed you should read it as the same thing that Ann Arbor folks mean by "concert."</BLOCKQUOTE> There may be no current item in the Ann Arbor feed using the concert topic so we definitely need a fixed point of reference.  What is that?  One answer might be a topic map and topic maps are certainly good for this.  How else could we do it? It would be easy enough to add an XFML style <TT><connect></TT> element to the ENT spec.  An example might be:<PRE> <topic id="music_event"> <connect>http://annarbor.example.org/topics.xml#concert</connect> </topic> </PRE> However ENT also allows topics without the backing of a topic map, in which case someone may just want to specify a topic ID, e.g.<PRE> <topic id="music_event"> <connect>concert</connect> </topic> </PRE> But the problem with this approach is that it means that music_event is now synonymous with anyone's definition of concert.  We could add an <TT>href</TT> attribute to <TT>connect</TT> to differentiate but I don't particularly like that either. Maybe someone else can come up with a simple alternative that befits the style of ENT?  I'm still leaning towards this as a problem best solved by topic maps. [Update] I've been thinking about this a little more and feel that the best way forwards is to work with groups like SocialText and the SSA to make sure the right tools are in place to solve this kind of problem using topic maps.  Adina? http://matt.blogs.it/entries/00001418.html Metadata is a social thing Tue, 22 Apr 2003 18:07:04 +0100 <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <A href="http://doc.weblogs.com/2003/04/21#notSoEasy">Not so easy?</A>. <A href="http://www.sifry.com/alerts/archives/000282.html#000282">As <A href="http://doc.weblogs.com/2003/04/11#askNotWhatRssCanDoForYou">requested</A>, David Sifry reviews</A> <A href="http://matt.blogs.it/specs/ENT/1.0/">Easy News Topics 1.0</A>. The upside: <BLOCKQUOTE> As a format, ENT is easy to understand, easy for application developers to implement, and pretty easy to parse. Kudos to Matt and Paolo for coming up with a design that is simple but extensible. </BLOCKQUOTE> The downside isn't so easily excerpted. Read the link for more. [<A href="http://doc.weblogs.com/">The Doc Searls Weblog</A>]</BLOCKQUOTE> Without wishing to seem oversensitive I think it is fair to say that David's issues are not with ENT per se, but with the idea of people cataloguing their own items with meta data.  His problems are social and the same argument could be made about RSS1.0 and mod_taxo. David reflects upon what happened to meta data in web pages and wonders if the same thing won't come about here too.  Here is how I responded in a comment on David's blog: <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> Thanks for the comment. I think you're broadly right that there will be a capacity for abuse here but it scales differently. When Google was indexing billions of pages the metadata became meaningless even without the abuse. However with RSS I think the game is different. I'm subscribed to 108 feeds right now. I add perhaps 1 a week on average. But I trust that the authors of those feeds would use topics reliably or not at all. Any application I have that can understand my subscription list can usefully utilize those topics whatever I think about anyone else. In a social software context somone else might trust my confidence in the indexing of those feeds. Etc... I think we can find ways of making this work. I also think that automatic annotation of feeds with topics is another possibility. To pick an example from my head. Syndic8 could have a topic engine that creates an annotated feed for every feed they monitor. If you trust Syndic8 you could use that feed instead and get the benefit of their indexing. And so on.</BLOCKQUOTE>   http://matt.blogs.it/entries/00001420.html ENT goes Movable Tue, 22 Apr 2003 21:59:14 +0100 <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <A href="http://www.andrerestivo.com/weblog/archives/001994.html">Easy News Topics</A>. Easy News Topics: Finally someone is working on blog categorization, just as I suggested some time ago. Paolo and... [<A href="http://www.andrerestivo.com/weblog/">Daily Bytes</A>]</BLOCKQUOTE> Congratulations to André for having the first <A href="http://www.purl.org/NET/ENT/1.0/">ENT</A> enabled <A href="http://www.movabletype.org/">MovableType</A> feed! This is really, really, fantastic news. http://matt.blogs.it/entries/00001423.html ENT goes Movable! Tue, 22 Apr 2003 23:03:08 +0100 <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <A href="http://www.andrerestivo.com/weblog/archives/002019.html">ENT enabled RSS</A>. ENT enabled RSS: No idea if its correctly implemented. Maybe a ENT validator is in order. Update: Some errors corrected.... [<A href="http://www.andrerestivo.com/weblog/">Daily Bytes</A>]</BLOCKQUOTE> Congratulations to André for having the first <A href="http://www.purl.org/NET/ENT/1.0/">ENT</A> enabled <A href="http://www.movabletype.org/">MovableType</A> feed! This is really, really, fantastic news. http://matt.blogs.it/entries/00001425.html Describing clouds Thu, 24 Apr 2003 12:05:22 +0100 <A href="http://paolo.evectors.it/">Paolo</A> and I have been chatting over some more revisions to the <A href="http://www.purl.org/NET/ENT/1.0/">ENT 1.0</A> spec.  In particular we have come across something that is awkward when it comes to user interface design. Right now a cloud is identified by a unique URL, e.g. <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <TT><cloud href="http://matt.blogs.it/topics/resources/topicRoll.opml"></TT></BLOCKQUOTE> Any topic from this roll can be uniquely identified as such, however a URL is not a very friendly thing to use in an interface as we have discovered implementing the interface for our k-collector proof of concept. We're thinking up alternatives and have a number of approaches: <OL> <LI>Add a description attribute to <TT><cloud></TT>. <LI>Add a description tag to <TT><cloud></TT>. <LI>Add a <TT><cloudinfo></TT> tag to the <TT><channel></TT> <LI>Refer to the cloud's definintion for more info.</LI></OL> Options (1) and (2) are more or less the same.  We've been somewhat baised towards attributes in ENT so I guess (1) makes most sense.  It's also very easy to do.  The downside is duplicating the description in every <TT><cloud></TT> tag.  But I guess nobody has complained about the duplication of the href. Option (3) might make sense.  We could move all the cloud information here and just refer to it from the <TT><item></TT>'s.  More efficient but it adds an extra burden on to processors. Option (4) was initially my favourite.  It's probably the right thing to do(tm).  But it's problematic.  We support all different kinds of external resource in ENT including things like XTM which doesn't really have any notion of a description.  In addition it places a huge burden on processors who may otherwise not be interested in the external resource. For this reason we will probably be adding a description attribute to the next draft of ENT (which will be published tomorrow). http://matt.blogs.it/entries/00001430.html MovableType & ENT Thu, 01 May 2003 22:19:21 +0100 My friend and former colleague <A href="http://blog.sockdrawer.org/">Paul Walk</A> has implemented a <A href="http://blog.sockdrawer.org/archives/000021.php">MovableType template</A> for generating an <A href="http://www.purl.org/NET/ENT/1.0/">ENT 1.0</A> feed.  Cool! Well done Paul. http://matt.blogs.it/entries/00001440.html Must it always be this way? Tue, 10 May 2005 18:37:21 +0100 So today it's Apples turn to incur my mighty wrath. Having gone to hell and back solving all the browser related issues with XSLT rendering of RSS feed, <a href="http://www.bethlet.net/">Beth</a> dropped the bombshell that Safari 2.0 was completely ignoring my stylesheet and rendering the feed itself. Now, i'll grant you that Safari does a pretty good job rendering the RSS, it's <a href="http://matt.blogs.it/images/safari-rss.jpg">sweetly pretty</a>. However it rather pisses on my parade since Safari doesn't know a damn thing about <a href="http://matt.blogs.it/specs/ENT/1.0/">topics</a>! So i'm busy rendering up topic cross-references (major thanks to <a href="http://www.bethlet.net/">Beth</a> for solving what she said were simple XSLT problems but which, nevertheless, had me pulling my hair out) which Safari will happily ignore. Why does it have to be this way? Especially when I am actually telling Safari exactly what XSLT stylesheet it should be using. Can anyone supply me with the magic incantation to make Safari honour my stylesheet? http://matt.blogs.it/entries/00002568.html