On Sun, Apr 03, 2005 at 03:06:26PM -0400, Joe Gregorio wrote: > > I agree with Sam, +1 to the required <link>. The argument that you > can't have an HTML representation are weak, since *I* can > generate one for your feed, whether you like it or not, ala: > > http://www.rss2html.com/
OK, I have Atom documents stored in the following places: 1. An attachment (or the content body) of an e-mail message 2. In an Oracle database behind a firewall 3. In an LDAP attribute, also behind a firewall 4. On a key chain hard drive 5. Typed out on a sheet of paper What URL can I use to refer to each of those? The key chain drive usually shows up as drive E:, if that helps. For simplicity, let's assume the sheet of paper can be stored on/in a flatbed scanner. > I can also generate an XSLT sheet that transforms Atom into > HTML then use the W3C XLST service to transform > an Atom feed into HTML: > > http://www.w3.org/2001/05/xslt Let's say I care about providing an HTML representation for my data. XML lets me embed an XML stylesheet into the XML data itself. So now I have a completely self-contained Atom resource that user agents can transform into HTML without needing a link to any external resource. Even if this could be represented with a URI, why would I want to specify an alternate version when the first version has everything I could want? All I hear are ways *some* Atom documents can be given alternate versions. I still haven't heard WHY that should be required, other than "because RSS does it." Why does RSS require it? Maybe we can start there. David -- == David Nesting WL7RO Fastolfe [EMAIL PROTECTED] http://fastolfe.net/ == fastolfe.net/me/pgp-key A054 47B1 6D4C E97A D882 C41F 3065 57D9 832F AB01
