From: S. Mike Dierken (email@example.com)
Date: Tue Sep 05 2000 - 10:26:34 PDT
This sort of 'architectural form' approach works pretty well, I've used it
in the past to output RDBMS records and provide field level meta-data (type,
name, etc.) and at the same provide simple HTML. By making it well formed,
all sorts of low-cost automation is also possible.
By using 'class=', you can also do some cool 'transforms' on existing
browsers via CSS.
Perhaps an literal example of RSS expressed with HTML tags and 'class='
attributes would help.
> -----Original Message-----
> From: Dan Brickley [mailto:Daniel.Brickley@bristol.ac.uk]
> Sent: Tuesday, September 05, 2000 10:10 AM
> To: Dave Winer
> Cc: Gerald Oskoboiny; Gregory Alan Bolcer; foRK
> Subject: Re: Survey on the evolution of RSS
> On Tue, 5 Sep 2000, Dave Winer wrote:
> > [...] I want to make end-user level syndication formats that are
> > transparently simple. Formats like RSS."
> What do you think of the idea that we use a (profile of) XHTML,
> augmented in places with CLASS=item CLASS=channel etc tags? Then XSLT
> (or Perl etc) convertors could extract RSS flavours, scripting
> news etc from
> such HTML. Advantage to webmasters being that they simply maintain an
> HTML 'latest news' page, with automation of various kinds following from
> HTML has provide itself simple enough to be adopted across the Web, and
> has a variety of authoring, conversion, indexing etc tools. I'm worried
> that RSS as a standalone format risks going head-to-head with (to
> pick one of several examples) WAP/WML site summaries...
This archive was generated by hypermail 2b29 : Tue Sep 05 2000 - 10:30:36 PDT