Archive of atom-syntax, by thread

• Re: finishing autodiscovery, like now, (continued)
  • Re: finishing autodiscovery, like now, Eric Scheid
  • Re: finishing autodiscovery, like now, Robert Sayre
  • Re: finishing autodiscovery, like now, Eric Scheid
  • Re: finishing autodiscovery, like now, Robert Sayre
  • Re: finishing autodiscovery, like now, James M Snell
  • Re: finishing autodiscovery, like now, Joe Gregorio
  • Re: finishing autodiscovery, like now, Eric Scheid
  • Re: finishing autodiscovery, like now, James M Snell
  • Re: finishing autodiscovery, like now, Phil Ringnalda
  • Re: finishing autodiscovery, like now, Joe Gregorio
  • Re: finishing autodiscovery, like now, Eric Scheid
  • Re: finishing autodiscovery, like now, A. Pagaltzis
  • Re: finishing autodiscovery, like now, Eric Scheid
  • Re: finishing autodiscovery, like now, Eric Scheid
  • Re: finishing autodiscovery, like now, A. Pagaltzis
  • Re: finishing autodiscovery, like now, Eric Scheid
  • Re: finishing autodiscovery, like now, Robert Sayre
  • Re: finishing autodiscovery, like now, A. Pagaltzis
  • Re: finishing autodiscovery, like now, James M Snell
  • Re: finishing autodiscovery, like now, James M Snell
  • Re: finishing autodiscovery, like now, Eric Scheid
  • Re: finishing autodiscovery, like now, Joe Gregorio
  • Re: finishing autodiscovery, like now, Eric Scheid
  • Re: finishing autodiscovery, like now, Joe Gregorio
  • Re: finishing autodiscovery, like now, John Panzer
  • Re: finishing autodiscovery, like now, Joe Gregorio
  • Re: finishing autodiscovery, like now, Eric Scheid
  • Re: finishing autodiscovery, like now, Tim Bray
    • RE: finishing autodiscovery, like now, Sean Lyndersay
      • RE: finishing autodiscovery, like now, John Panzer
      • Re: finishing autodiscovery, like now, Robert Sayre
      • Re: finishing autodiscovery, like now, A. Pagaltzis
      • Re: finishing autodiscovery, like now, John Panzer
    • Re: finishing autodiscovery, like now, James M Snell
• atom:content's src and server-driven content negotiation, Andreas Sewe
  • Re: atom:content's src and server-driven content negotiation, John Panzer
  • Re: atom:content's src and server-driven content negotiation, Graham Parks
    • Re: atom:content's src and server-driven content negotiation, David Powell
      • Re: atom:content's src and server-driven content negotiation, Graham Parks
      • Re: atom:content's src and server-driven content negotiation, Andreas Sewe
• partial xml in atom:content ?, Eric Scheid
  • Re: partial xml in atom:content ?, James M Snell
  • Re: partial xml in atom:content ?, James Holderness
  • Re: partial xml in atom:content ?, Elliotte Harold
    • Re: partial xml in atom:content ?, James M Snell
      • Re: partial xml in atom:content ?, Eric Scheid
      • Re: partial xml in atom:content ?, James M Snell
      • Re: partial xml in atom:content ?, Eric Scheid
      • Re: partial xml in atom:content ?, James Holderness
      • Re: partial xml in atom:content ?, Eric Scheid
      • Re: partial xml in atom:content ?, A. Pagaltzis
      • Re: partial xml in atom:content ?, Eric Scheid
      • Re: partial xml in atom:content ?, A. Pagaltzis
      • Re: partial xml in atom:content ?, Graham Parks
      • Re: partial xml in atom:content ?, James Holderness
      • Re: partial xml in atom:content ?, Eric Scheid
      • Re: partial xml in atom:content ?, James Holderness
      • Re: partial xml in atom:content ?, Graham Parks
      • Re: partial xml in atom:content ?, Manoj
      • Re: partial xml in atom:content ?, Eric Scheid
      • Re: partial xml in atom:content ?, Antone Roundy
      • Re: partial xml in atom:content ?, A. Pagaltzis
      • Re: partial xml in atom:content ?, James Holderness
      • Re: partial xml in atom:content ?, Graham Parks
      • Re: partial xml in atom:content ?, James Holderness
      • Re: partial xml in atom:content ?, Antone Roundy
      • Re: partial xml in atom:content ?, James Holderness
      • Re: partial xml in atom:content ?, A. Pagaltzis
      • Re: partial xml in atom:content ?, James Holderness
      • Re: partial xml in atom:content ?, Antone Roundy
      • Re: partial xml in atom:content ?, James Holderness
      • Re: partial xml in atom:content ?, James M Snell
      • Re: partial xml in atom:content ?, James Holderness
      • Re: partial xml in atom:content ?, A. Pagaltzis
      • Re: partial xml in atom:content ?, James Holderness
      • Re: partial xml in atom:content ?, David Powell
      • Re: partial xml in atom:content ?, David Powell
      • Re: partial xml in atom:content ?, James Holderness
      • Re: partial xml in atom:content ?, A. Pagaltzis
      • Re: partial xml in atom:content ?, James Holderness
    • Re: partial xml in atom:content ?, Eric Scheid
  • <Possible follow-ups>
  • Re: partial xml in atom:content ?, Robert Sayre
    • Re: partial xml in atom:content ?, James Holderness
  • Re: partial xml in atom:content ?, Robert Sayre
    • Re: partial xml in atom:content ?, James Holderness
      • Message not available
      • Message not available
      • Re: partial xml in atom:content ?, Graham Parks
      • Re: partial xml in atom:content ?, James Holderness
• info: IPTC starts testing the News Revolution, Laurent Le Meur
• Inheritance of atom:rights, David Powell
  • Re: Inheritance of atom:rights, A. Pagaltzis
• Reader 'updated' semantics, James Yenne
  • Re: Reader 'updated' semantics, James M Snell
    • Re: Reader 'updated' semantics, Tim Bray
      • RE: Reader 'updated' semantics, James Yenne
      • Re: Reader 'updated' semantics, Stephane Bortzmeyer
      • RE: Reader 'updated' semantics, James Yenne
      • RE: Reader 'updated' semantics, James Yenne
      • Re: Reader 'updated' semantics, A. Pagaltzis
      • Re: Reader 'updated' semantics, Stephane Bortzmeyer
      • Re: Reader 'updated' semantics, James Holderness
      • Re: Reader 'updated' semantics, Stephane Bortzmeyer
      • Re: Reader 'updated' semantics, James Holderness
      • RE: Reader 'updated' semantics, James Yenne
      • Re: Reader 'updated' semantics, James M Snell
      • Re: Reader 'updated' semantics, Tim Bray
      • Re: Reader 'updated' semantics, Stephane Bortzmeyer
      • Re: Reader 'updated' semantics, Bill de hÓra
• Category URI's, James M Snell
  • Re: Category URI's, A. Pagaltzis
    • Re: Category URI's, James M Snell
    • Re: Category URI's, Graham Parks
      • Re: Category URI's, Bill de hÓra
      • Re: Category URI's, A.Pagaltzis
      • Re: Category URI's, James M Snell
  • Re: Category URI's, Tim Bray
    • Re: Category URI's, James M Snell
  • Re: Category URI's, James Holderness
• I-D ACTION:draft-ietf-atompub-protocol-07.txt, Internet-Drafts
• [Fwd: Re: todo: add language encoding information], James M Snell
  • Re: [Fwd: Re: todo: add language encoding information], A. Pagaltzis
    • Re: [Fwd: Re: todo: add language encoding information], James M Snell
      • Re: [Fwd: Re: todo: add language encoding information], Henry Story
      • Re: [Fwd: Re: todo: add language encoding information], James M Snell
      • Re: todo: add language encoding information, Henry Story
      • Re: [Fwd: Re: todo: add language encoding information], James Holderness
      • Re: [Fwd: Re: todo: add language encoding information], Henry Story
      • Re: [Fwd: Re: todo: add language encoding information], Elliotte Harold
      • Re: [Fwd: Re: todo: add language encoding information], Henry Story
      • Re: [Fwd: Re: todo: add language encoding information], Walter Underwood
      • Re: [Fwd: Re: todo: add language encoding information], James Holderness
      • Re: todo: add language encoding information, Henry Story
      • Re: todo: add language encoding information, James Holderness
      • Re: todo: add language encoding information, Henry Story
      • Re: todo: add language encoding information, Henry Story
      • Re: todo: add language encoding information, Eric Scheid
      • Re: todo: add language encoding information, Henry Story
      • Re: [Fwd: Re: todo: add language encoding information], Henry Story
      • Re: [Fwd: Re: todo: add language encoding information], James Holderness
      • Re: todo: add language encoding information, Henry Story
      • Re: [Fwd: Re: todo: add language encoding information], David Powell
      • Re: [Fwd: Re: todo: add language encoding information], James Holderness
    • Re: [Fwd: Re: todo: add language encoding information], James Holderness
      • Re: [Fwd: Re: todo: add language encoding information], A. Pagaltzis
• Re: todo: add language encoding information, Henry Story
  • Re: todo: add language encoding information, James Holderness
    • Re: todo: add language encoding information, Henry Story
  • Message not available
    • Re: todo: add language encoding information, Henry Story
      • Re: todo: add language encoding information, James Holderness
  • <Possible follow-ups>
  • Re: todo: add language encoding information, Henry Story
  • Re: todo: add language encoding information, Henry Story
    • Re: todo: add language encoding information, Henry Story
• examples of merged feeds/feed aggregation?, Michael Stillwell
  • Re: examples of merged feeds/feed aggregation?, A. Pagaltzis
  • Re: examples of merged feeds/feed aggregation?, Eric Scheid
• info: newsml-2 ready for test, Laurent Le Meur
• Tag URIs, Alan Gutierrez
  • Re: Tag URIs, A. Pagaltzis
    • Re: Tag URIs, A. Pagaltzis
  • Re: Tag URIs, Stephane Bortzmeyer
  • Re: Tag URIs, Tim Bray
• RSS 2.0 to Atom 1.0, Alan Gutierrez
  • Re: RSS 2.0 to Atom 1.0, James M Snell
    • Re: RSS 2.0 to Atom 1.0, Alan Gutierrez
      • Re: RSS 2.0 to Atom 1.0, James Holderness
      • Re: RSS 2.0 to Atom 1.0, Alan Gutierrez
      • Re: RSS 2.0 to Atom 1.0, James Holderness
      • Re: RSS 2.0 to Atom 1.0, James M Snell
• Extension draft updates, James M Snell
  • Feed thread draft (was: Extension draft updates), James Holderness
    • Re: Feed thread draft, James M Snell
      • Re: Feed thread draft, James Holderness
      • Re: Feed thread draft, A. Pagaltzis
      • Re: Feed thread draft, James Holderness
      • Re: Feed thread draft, A. Pagaltzis
      • Re: Feed thread draft, James Holderness
      • Re: Feed thread draft, A. Pagaltzis
      • Re: Feed thread draft, James Holderness
  • Feed Thread Extension (was: Extension draft updates), A. Pagaltzis
  • Re: Extension draft updates, Alex Milowski
    • Re: Extension draft updates, James M Snell
• draft-snell-atompub-link-extensions-00.txt, James M Snell
• Author of an empty feed?, Phil Ringnalda
  • Re: Author of an empty feed?, James Holderness
• RFC 4287 on The Atom Syndication Format, rfc-editor
• Should titles really not be blank?, James Holderness
• Firefox feed autodiscovery, James Holderness
• AtomPubIssuesList for 2005/11/30, Sam Ruby
  • Re: AtomPubIssuesList for 2005/11/30, Robert Sayre
    • Re: AtomPubIssuesList for 2005/11/30, Sam Ruby
      • Re: AtomPubIssuesList for 2005/11/30, Robert Sayre
      • Re: AtomPubIssuesList for 2005/11/30, Sam Ruby
      • Re: AtomPubIssuesList for 2005/11/30, Robert Sayre
      • Re: AtomPubIssuesList for 2005/11/30, Robert Sayre
  • Re: AtomPubIssuesList for 2005/11/30, Paul Hoffman
• Is there a bug in undefinedAttribute?, A. Pagaltzis
  • Re: Is there a bug in undefinedAttribute?, Uche Ogbuji
    • Re: Is there a bug in undefinedAttribute?, A. Pagaltzis
      • Re: Is there a bug in undefinedAttribute?, Uche Ogbuji
      • Re: Is there a bug in undefinedAttribute?, Thomas Broyer
      • Info: NewsML 2 Working Drafts published, Laurent Le Meur
• Atom, files and directories: what it's all about, Henry Story
  • Re: Atom, files and directories: what it's all about, Ernest Prabhakar
    • Re: Atom, files and directories: what it's all about, Luke Arno
      • Re: Atom, files and directories: what it's all about, Henry Story
      • Re: Atom, files and directories: what it's all about, Uche Ogbuji
      • Re: Atom, files and directories: what it's all about, Henry Story
      • Re: Atom, files and directories: what it's all about, Uche Ogbuji
      • Re: Atom, files and directories: what it's all about, Henry Story
• FYI: Microsoft Simple Sharing Extensions for RSS and OPML, James M Snell
• I-D ACTION:draft-ietf-atompub-protocol-06.txt, Internet-Drafts
• How to specify multiple alternative encodings of the same content?, J.B. Nicholson-Owens
  • Re: How to specify multiple alternative encodings of the same content?, A. Pagaltzis
    • Re: How to specify multiple alternative encodings of the same content?, Thomas Broyer
    • Re: How to specify multiple alternative encodings of the same content?, James M Snell
  • Re: How to specify multiple alternative encodings of the same content?, Sjoerd Visscher
  • <Possible follow-ups>
  • RE: How to specify multiple alternative encodings of the same content?, Lindsley Brett-ABL001
    • RE: How to specify multiple alternative encodings of the same content?, David Powell
      • Re: How to specify multiple alternative encodings of the same content?, A. Pagaltzis
  • RE: How to specify multiple alternative encodings of the same content?, Lindsley Brett-ABL001
    • Re: How to specify multiple alternative encodings of the same content?, A. Pagaltzis
• Re: Is Atom Broken?, Henry Story
• app:updated ordering in Collections, Manuzhai
  • Re: app:updated ordering in Collections, Joe Gregorio
    • Re: app:updated ordering in Collections, Joe Gregorio
    • Re: app:updated ordering in Collections, Bill de hÓra
• Re: FYI: hAtom, Henry Story
• clarification needed: order of children of atom:entry, Eric Scheid
  • Re: clarification needed: order of children of atom:entry, James M Snell
  • Re: clarification needed: order of children of atom:entry, A. Pagaltzis
    • Re: clarification needed: order of children of atom:entry, Eric Scheid
  • Re: clarification needed: order of children of atom:entry, Tim Bray
• How to represent an authenticated identity in an <author> tag, Byrne Reese
  • Re: How to represent an authenticated identity in an <author> tag, Tim Bray
• icon and logo on entry, Henry Story
  • Re: icon and logo on entry, James M Snell
    • Re: icon and logo on entry, Henry Story
      • Re: icon and logo on entry, Henry Story
      • Re: icon and logo on entry, James M Snell
• RE: Are Generic Link Relations Always a Good Idea? [was: Feed History -04], Byrne Reese
• New Link Relations -- Last Call, Mark Nottingham
  • Re: New Link Relations -- Last Call, Elias Torres
    • Re: New Link Relations -- Last Call, Mark Nottingham
      • Re: New Link Relations -- Last Call, Elias Torres
    • Re: New Link Relations -- Last Call, James M Snell
    • Re: New Link Relations -- Last Call, A. Pagaltzis
  • Re: New Link Relations -- Last Call, James M Snell
  • Re: New Link Relations -- Last Call, Peter Robinson
    • Re: New Link Relations -- Last Call, Mark Nottingham
      • Re: New Link Relations -- Last Call, A. Pagaltzis
      • Re: New Link Relations -- Last Call, Stefan Eissing
      • Re: New Link Relations -- Last Call, Henry Story
      • Re: New Link Relations -- Last Call, A. Pagaltzis
      • Re: New Link Relations -- Last Call, Peter Robinson
      • Re: New Link Relations -- Last Call, Mark Nottingham
      • Re: New Link Relations -- Last Call, Mark Nottingham
  • Re: New Link Relations -- Last Call, James Holderness
• What is this entry about?, James M Snell
  • Re: What is this entry about?, Bill de hÓra
    • Re: What is this entry about?, James M Snell
      • Re: What is this entry about?, Bill de hÓra
  • Re: What is this entry about?, A. Pagaltzis
    • Re: What is this entry about?, James M Snell
      • Re: What is this entry about?, Antone Roundy
      • Re: What is this entry about?, Bill de hÓra
      • Re: What is this entry about?, =?utf-8?b?QmlsbCBkZSBow5NyYQ==?=
      • Re: What is this entry about?, James M Snell
      • Re: What is this entry about?, =?utf-8?b?QmlsbCBkZSBow5NyYQ==?=
      • Re: What is this entry about?, Danny Ayers
      • Re: What is this entry about?, Henry Story
      • Re: What is this entry about?, Henry Story
• Profile links, James M Snell
  • Re: Profile links, Bill de hÓra
    • Re: Profile links, James M Snell
      • Re: Profile links, Bill de hÓra
      • Re: Profile links, James M Snell
      • Re: Profile links, Bill de hÓra
      • Re: Profile links, James M Snell
      • Re: Profile links, James Holderness
      • Re: Profile links, James M Snell
      • Re: Profile links, Bill de hÓra
      • Re: Profile links, James M Snell
      • Re: Profile links, Robert Sayre
      • Re: Profile links, James M Snell
      • Re: Profile links, James Holderness
      • Re: Profile links, Antone Roundy
      • Re: Profile links, James M Snell
      • Re: Profile links, Joe Gregorio
      • Re: Profile links, James M Snell
      • Re: Profile links, Joe Gregorio
      • Message not available
      • Re: Profile links, Paul Denning
  • Re: Profile links, James Holderness
    • Re: Profile links, James M Snell
• Sponsored Links and other link extensions, James M Snell
  • Re: Sponsored Links and other link extensions, James Holderness
    • Re: Sponsored Links and other link extensions, James M Snell
    • Re: Sponsored Links and other link extensions, Eric Scheid
      • Re: Sponsored Links and other link extensions, James M Snell
      • Re: Sponsored Links and other link extensions, Eric Scheid
      • Re: Sponsored Links and other link extensions, James Holderness
      • Re: Sponsored Links and other link extensions, Antone Roundy
      • Re: Sponsored Links and other link extensions, James Holderness
      • Re: Sponsored Links and other link extensions, James M Snell
      • Re: Sponsored Links and other link extensions, James Holderness
      • Re: Sponsored Links and other link extensions, Eric Scheid
      • Re: Sponsored Links and other link extensions, A. Pagaltzis
      • Re: Sponsored Links and other link extensions, Antone Roundy
      • Re: Sponsored Links and other link extensions, A. Pagaltzis
      • Re: Sponsored Links and other link extensions, Antone Roundy
      • Re: Sponsored Links and other link extensions, A. Pagaltzis
      • Re: Sponsored Links and other link extensions, Antone Roundy
      • Re: Sponsored Links and other link extensions, A. Pagaltzis
      • Re: Sponsored Links and other link extensions, Eric Scheid
      • Re: Sponsored Links and other link extensions, Antone Roundy
      • Re: Sponsored Links and other link extensions, James M Snell
      • Re: Sponsored Links and other link extensions, Antone Roundy
      • Re: Sponsored Links and other link extensions, Eric Scheid
      • Re: Sponsored Links and other link extensions, James Holderness
      • Re: Sponsored Links and other link extensions, James M Snell
      • Re: Sponsored Links and other link extensions, Antone Roundy
      • Re: Sponsored Links and other link extensions, Henry Story
      • Re: Sponsored Links and other link extensions, Eric Scheid
      • Re: Sponsored Links and other link extensions, James Holderness
      • Re: Sponsored Links and other link extensions, A. Pagaltzis
      • Re: Sponsored Links and other link extensions, Eric Scheid
      • Re: Sponsored Links and other link extensions, Eric Scheid
      • Re: Sponsored Links and other link extensions, A. Pagaltzis
      • Re: Sponsored Links and other link extensions, Eric Scheid
      • Re: Sponsored Links and other link extensions, Eric Scheid
      • Re: Sponsored Links and other link extensions, James M Snell
      • Re: Sponsored Links and other link extensions, Eric Scheid
  • <Possible follow-ups>
  • RE: Sponsored Links and other link extensions, Byrne Reese
• Application for addition to Atom Registry of Link Relations, James M Snell
  • Re: Application for addition to Atom Registry of Link Relations, Antone Roundy
    • Re: Application for addition to Atom Registry of Link Relations, James M Snell
      • Re: Application for addition to Atom Registry of Link Relations, Antone Roundy
      • Re: Application for addition to Atom Registry of Link Relations, James M Snell
      • Re: Application for addition to Atom Registry of Link Relations, Eric Scheid
• Unofficial Last Call - draft-snell-atompub-feed-thread-04.txt, James M Snell
  • Re: Unofficial Last Call - draft-snell-atompub-feed-thread-04.txt, James Holderness
    • Re: Unofficial Last Call - draft-snell-atompub-feed-thread-04.txt, James M Snell
  • Re: Unofficial Last Call - draft-snell-atompub-feed-thread-04.txt, James Holderness
    • Re: Unofficial Last Call - draft-snell-atompub-feed-thread-04.txt, James M Snell
    • Re: Unofficial Last Call - draft-snell-atompub-feed-thread-04.txt, A. Pagaltzis
  • <Possible follow-ups>
  • RE: Unofficial Last Call - draft-snell-atompub-feed-thread-04.txt, Byrne Reese
    • Re: Unofficial Last Call - draft-snell-atompub-feed-thread-04.txt, James M Snell
      • Re: Unofficial Last Call - draft-snell-atompub-feed-thread-04.txt, James Holderness
      • Re: Unofficial Last Call - draft-snell-atompub-feed-thread-04.txt, James M Snell
• Unofficial Last Call - draft-snell-atompub-feed-index-03.txt, James M Snell
  • Re: Unofficial Last Call - draft-snell-atompub-feed-index-03.txt, James Holderness
• Re: draft-snell-atompub-feed-license-03.txt, James M Snell
• New Link Relations -- Ready to go?, Mark Nottingham
  • Re: New Link Relations -- Ready to go?, James M Snell
  • Re: New Link Relations -- Ready to go?, Eric Scheid
    • Re: New Link Relations -- Ready to go?, Henry Story
  • Re: New Link Relations -- Ready to go?, James Holderness
  • Re: New Link Relations -- Ready to go?, Tim Bray
    • Re: New Link Relations -- Ready to go?, James Holderness
      • Re: New Link Relations -- Ready to go?, Tim Bray
      • Re: New Link Relations -- Ready to go?, Mark Nottingham
      • Re: New Link Relations -- Ready to go?, Tim Bray
      • Re: New Link Relations -- Ready to go?, Mark Nottingham
      • Re: New Link Relations -- Ready to go?, Tim Bray
      • Re: New Link Relations -- Ready to go?, James Holderness
      • Re: New Link Relations -- Ready to go?, Mark Nottingham
      • Re: New Link Relations -- Ready to go?, Eric Scheid
      • Re: New Link Relations -- Ready to go?, James Holderness
      • Re: New Link Relations -- Ready to go?, Tim Bray
      • Re: New Link Relations -- Ready to go?, Mark Nottingham
      • Re: New Link Relations -- Ready to go?, Tim Bray
      • Re: New Link Relations -- Ready to go?, Mark Nottingham
    • Re: New Link Relations -- Ready to go?, Eric Scheid
      • Re: New Link Relations -- Ready to go?, A. Pagaltzis
      • Re: New Link Relations -- Ready to go?, James M Snell
      • Re: New Link Relations -- Ready to go?, Eric Scheid
  • Re: New Link Relations -- Ready to go?, Thomas Broyer
    • Re: New Link Relations -- Ready to go?, James M Snell
      • Re: New Link Relations -- Ready to go?, Thomas Broyer
      • Re: New Link Relations -- Ready to go?, James M Snell
      • Re: New Link Relations -- Ready to go?, Thomas Broyer
      • Re: New Link Relations -- Ready to go?, James M Snell
      • Re: New Link Relations -- Ready to go?, Thomas Broyer
      • Re: New Link Relations -- Ready to go?, James M Snell
      • Re: New Link Relations -- Ready to go?, Thomas Broyer
      • Re: New Link Relations -- Ready to go?, James Holderness
      • Re: New Link Relations -- Ready to go?, Thomas Broyer
      • Re: New Link Relations -- Ready to go?, Thomas Broyer
      • Re: New Link Relations -- Ready to go?, Mark Nottingham
      • Re: New Link Relations -- Ready to go?, James M Snell
      • Re: New Link Relations -- Ready to go?, Thomas Broyer
      • Re: New Link Relations -- Ready to go?, Eric Scheid
      • Re: New Link Relations -- Ready to go?, James Holderness
      • Re: New Link Relations -- Ready to go?, Antone Roundy
      • Re: New Link Relations -- Ready to go?, James Holderness
      • Re: New Link Relations -- Ready to go?, Thomas Broyer
      • Re: New Link Relations -- Ready to go?, James Holderness
      • Re: New Link Relations -- Ready to go?, Antone Roundy
      • Re: New Link Relations -- Ready to go?, James Holderness
      • Re: New Link Relations -- Ready to go?, Antone Roundy
  • Re: New Link Relations -- Ready to go?, Peter Robinson
    • Re: New Link Relations -- Ready to go?, Robert Sayre
  • <Possible follow-ups>
  • RE: New Link Relations -- Ready to go?, Byrne Reese
  • RE: New Link Relations -- Ready to go?, Byrne Reese
• Re: General/Specific [was: Feed History / Protocol overlap], Antone Roundy
  • <Possible follow-ups>
  • RE: General/Specific [was: Feed History / Protocol overlap], Byrne Reese
• Feed History / Protocol overlap, Robert Sayre
  • Re: Feed History / Protocol overlap, Mark Nottingham
    • Re: Feed History / Protocol overlap, Robert Sayre
      • Re: Feed History / Protocol overlap, Mark Nottingham
      • Re: Feed History / Protocol overlap, Robert Sayre
      • Re: Feed History / Protocol overlap, Mark Nottingham
      • Re: Feed History / Protocol overlap, Robert Sayre
      • Re: Feed History / Protocol overlap, Mark Nottingham
      • Re: Feed History / Protocol overlap, Robert Sayre
      • Re: Feed History / Protocol overlap, James M Snell
      • Re: Feed History / Protocol overlap, Mark Nottingham
      • Re: Feed History / Protocol overlap, Thomas Broyer
      • Re: Feed History / Protocol overlap, Mark Nottingham
      • Re: Feed History / Protocol overlap, Robert Sayre
      • Re: Feed History / Protocol overlap, Antone Roundy
      • Re: Feed History / Protocol overlap, James M Snell
      • Re: Feed History / Protocol overlap, Antone Roundy
      • Re: Feed History / Protocol overlap, Robert Sayre
      • Re: Feed History / Protocol overlap, Antone Roundy
      • Re: Feed History / Protocol overlap, Antone Roundy
      • Re: Feed History / Protocol overlap, Thomas Broyer
      • General/Specific [was: Feed History / Protocol overlap], Mark Nottingham
      • Re: General/Specific [was: Feed History / Protocol overlap], James M Snell
      • Re: General/Specific [was: Feed History / Protocol overlap], James Holderness
      • Re: General/Specific [was: Feed History / Protocol overlap], Thomas Broyer
      • Re: General/Specific [was: Feed History / Protocol overlap], Thomas Broyer
      • Re: General/Specific [was: Feed History / Protocol overlap], Eric Scheid
      • Re: General/Specific [was: Feed History / Protocol overlap], Stefan Eissing
      • Re: General/Specific [was: Feed History / Protocol overlap], Joe Gregorio
      • Re: Feed History / Protocol overlap, Eric Scheid
      • Re: Feed History / Protocol overlap, Eric Scheid
      • Re: Feed History / Protocol overlap, Robert Sayre
      • Re: Feed History / Protocol overlap, Eric Scheid
      • Re: Feed History / Protocol overlap, Bill de hÓra
      • Re: Feed History / Protocol overlap, Eric Scheid
• Spec wording bug?, Danny Ayers
  • Re: Spec wording bug?, Paul Hoffman
  • Re: Spec wording bug?, Antone Roundy
  • Message not available
    • Re: Spec wording bug?, Robert Sayre
      • Re: Spec wording bug?, Danny Ayers
• Re: draft-snell-atompub-feed-thread-01.txt, Byrne Reese
  • Re: draft-snell-atompub-feed-thread-01.txt, Thomas Broyer
    • Re: draft-snell-atompub-feed-thread-01.txt, James M Snell
• Signifying a Complete Feed, Byrne Reese
  • Re: Signifying a Complete Feed, A. Pagaltzis
  • Re: Signifying a Complete Feed, James M Snell
    • Re: Signifying a Complete Feed, James Holderness
      • Re: Signifying a Complete Feed, James M Snell
  • <Possible follow-ups>
  • Re: Signifying a Complete Feed, A. Pagaltzis
    • Re: Signifying a Complete Feed, Graham
      • Re: Signifying a Complete Feed, Robert Sayre
      • Re: Signifying a Complete Feed, James Holderness
  • RE: Signifying a Complete Feed, Byrne Reese
• more than one content element?, Pascal Philippe
  • Re: more than one content element?, James Holderness
    • Re: more than one content element?, A. Pagaltzis
      • Re: more than one content element?, James Holderness
      • Re: more than one content element?, John Panzer
      • Re: more than one content element?, A. Pagaltzis
      • Re: more than one content element?, John Panzer
      • Re: more than one content element?, A. Pagaltzis
      • Re: more than one content element?, Antone Roundy
      • Re: more than one content element?, James Holderness
  • Re: more than one content element?, Eric Scheid
• I-D ACTION:draft-ietf-atompub-protocol-05.txt, Internet-Drafts
• Re: Straw Poll: age:expires vs. dcterms:valid (was Re: Unofficial last call on draft-snell-atompub-feed-expires-04.txt) On Oct 8, 2005, at 8:37 AM, James M Snell wrote: I wanted to indicate that a given entry must expire at Midnight on Dec, 12, 2005 (GMT). using age:expires: [snip] using dcterms:valid (http://web.resource.org/rss/1.0/modules/dcterms/#valid) <entry> <dcterms:valid>end:2005-12-12T00:00:00Z</dcterms:valid> </entry> Advantage: * Existing namespace, known element Disadvantage: * Value can be many different things. I've even seen cases in which the content of dcterms:valid is an XML structure. My chief problem with dcterms:valid (and with dublin core in general) is that the elements are very loosely defined. The content can literally be anything folks want it to be and still be considered valid. Unless we constrain the value space for this element when used in Atom, it *could* lead to a bunch of extra work for consumers to parse and process those dates. I prefer very crisply defined elements. Then again, reusing an existing namespace is Goodness. I think it would be going too far to say "when using dcterms:valid in Atom, you must follow this profile", because we don't own dcterms, and doing so might limit people from doing valid things with it that don't follow that profile. But I do think it would be reasonable to say "when using dcterms:valid in Atom, it is recommended that you follow this profile--otherwise your data may be technically valid, but not widely understood", thus giving developers an excuse for not supporting data not formatted according to that profile. If a use case that requires a different format becomes common, then developers can start supporting more formats at that point. That said, my "vote" is for doing what I just said--advocate the use of dcterms:valid for this purpose, with the date formatted to match Atom's date construct profile. BTW, you might choose language that leaves room for having both start and end dates for validity--! for exam, Antone Roundy
  • Re: Straw Poll: age:expires vs. ...... plus a gazillion words, Antone Roundy
• re: Straw Poll: age:expires vs. dcterms:valid, Robert Sayre
• FYI: Google Reader and Atom 1.0, James M Snell
  • Re: FYI: Google Reader and Atom 1.0, Julian Reschke
    • Re: FYI: Google Reader and Atom 1.0, Robert Sayre
      • Re: FYI: Google Reader and Atom 1.0, James M Snell
• FYI: Advertising Web services with Atom 1.0, James M Snell
  • Re: FYI: Advertising Web services with Atom 1.0, Aleksander Slominski
    • Re: FYI: Advertising Web services with Atom 1.0, A. Pagaltzis
      • Re: FYI: Advertising Web services with Atom 1.0, James M Snell
      • Re: FYI: Advertising Web services with Atom 1.0, A. Pagaltzis
    • Re: FYI: Advertising Web services with Atom 1.0, James M Snell
      • Re: FYI: Advertising Web services with Atom 1.0, Aleksander Slominski
      • Re: FYI: Advertising Web services with Atom 1.0, James M Snell
• Question about category@scheme, Byrne Reese
  • Re: Question about category@scheme, James M Snell
  • Re: Question about category@scheme, Tim Bray
    • Re: Question about category@scheme, A. Pagaltzis
  • Re: Question about category@scheme, A. Pagaltzis
• Next and Previous, Alan Gutierrez
  • Re: Next and Previous, Mark Nottingham
    • Re: Next and Previous, James Holderness
      • Re: Next and Previous, Mark Nottingham
      • Re: Next and Previous, Thomas Broyer
      • Re: Next and Previous, James Holderness
      • Re: Next and Previous, Thomas Broyer
      • Re: Next and Previous, James Holderness
      • Re: Next and Previous, James M Snell
      • Re: Next and Previous, James Holderness
• ACE - Atom Common Extensions Namespace, James M Snell

The web site for this mailing list is sponsored by the Internet Mail Consortium. If you have any suggestions for additions or corrections to this Web page, please send them to phoffman@imc.org.