network.syndication.atom.protocol (date)

network.syndication.atom.protocol (date)

August 19, 2006

Re: By way of example., Tim Bray
Re: By way of example., Eric J. Bowman
Re: By way of example., Kyle Marvin
Re: PaceContentNegotiationSection, Eric J. Bowman
Re: By way of example., Eric J. Bowman
Re: By way of example., Kyle Marvin
Re: By way of example., Eric J. Bowman
Re: PaceContentNegotiationSection, James M Snell
Re: By way of example., Eric J. Bowman
Re: By way of example., Kyle Marvin
Re: PaceContentNegotiationSection, Eric J. Bowman
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Eric Scheid
Re: PaceContentNegotiationSection, Eric J. Bowman
Re: PaceURINomenclature and PaceOnlyMemberURI, Eric Scheid
Re: By way of example., Eric J. Bowman
Re: Why MD5 Headers are Imperative, James M Snell
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: By way of example., Kyle Marvin
Re: Why MD5 Headers are Imperative, Kyle Marvin
Re: By way of example., James M Snell
Re: PaceContentNegotiationSection, James M Snell
Re: By way of example., Eric J. Bowman
Re: PaceContentNegotiationSection, Eric J. Bowman
Re: PaceContentNegotiationSection, James M Snell
Re: PaceContentNegotiationSection, Eric J. Bowman
Re: Re: Why MD5 Headers are Imperative, Robert Sayre
Re: By way of example., James M Snell
Re: Why MD5 Headers are Imperative, Bill de hÓra
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: By way of example., Tim Bray
Re: Why MD5 Headers are Imperative, Tim Bray
Re: Why MD5 Headers are Imperative, Bill de hÓra
Re: By way of example., Eric J. Bowman
Re: By way of example., James M Snell

August 18, 2006

Re: PaceURINomenclature and PaceOnlyMemberURI, Elias Torres
Re: By way of example., Eric J. Bowman
Re: PaceURINomenclature and PaceOnlyMemberURI, Joe Gregorio
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: PaceURINomenclature and PaceOnlyMemberURI, Elias Torres
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Michael Wechner
Re: PaceContentNegotiationSection, James M Snell
Re: PaceContentNegotiationSection, James M Snell
Re: By way of example., Bill de hÓra
Re: PaceContentNegotiationSection, Eric J. Bowman
Re: PaceURINomenclature and PaceOnlyMemberURI, Tim Bray
Re: PaceURINomenclature and PaceOnlyMemberURI, Kyle Marvin
Re: PaceContentNegotiationSection, Eric J. Bowman
Re: Posted PaceURINomenclature, Bill de hÓra
Re: PaceOnlyMemberURI, Joe Gregorio
Re: PaceURINomenclature and PaceOnlyMemberURI, Thomas Broyer
Re: PaceOnlyMemberURI, Asbjørn Ulsberg
Re: PaceURINomenclature and PaceOnlyMemberURI, Elias Torres
Re: PaceURINomenclature and PaceOnlyMemberURI, Robert Sayre
Re: PaceURINomenclature and PaceOnlyMemberURI, Thomas Broyer
Re: PaceURINomenclature and PaceOnlyMemberURI, Kyle Marvin
Re: Posted PaceURINomenclature, Kyle Marvin
Re: By way of example., James M Snell
Re: Why MD5 Headers are Imperative, Thomas Broyer
Re: PaceNoServiceDocument, Eric J. Bowman
Mailing list tone, Paul Hoffman
Re: By way of example., Tim Bray
Re: Posted PaceURINomenclature, Tim Bray
Re: PaceAppModified2 - was Re: Some feedback on current APP issues, Sylvain Hellegouarch
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Sylvain Hellegouarch
Re: PaceAppModified2 - was Re: Some feedback on current APP issues, Eric J. Bowman
Re: PaceURINomenclature and PaceOnlyMemberURI, Elias Torres
Re: By way of example., Sylvain Hellegouarch
Re: Why MD5 Headers are Imperative, James M Snell
Re: By way of example., Eric J. Bowman
Re: Posted PaceURINomenclature, Kyle Marvin
Re: Posted PaceURINomenclature, Bill de hÓra
Re: Why MD5 Headers are Imperative, Lisa Dusseault
Re: Posted PaceURINomenclature, James M Snell
Re: Posted PaceURINomenclature, Bill de hÓra
Re: PaceOnlyMemberURI, Bill de hÓra
Re: Meet the Ape, Joe Gregorio
Re: Meet the Ape, Tim Bray
Re: Why MD5 Headers are Imperative, Bill de hÓra
Re: Meet the Ape, Joe Gregorio
Re: Some editoria of the '09 specification, Bill de hÓra
Re: PaceContentNegotiationSection, Asbjørn Ulsberg
Re: Posted PaceURINomenclature, Asbjørn Ulsberg
Re: PaceContentNegotiationSection, Asbjørn Ulsberg
Re: link@rel='self' -- different for /collection/entry and link@rel='edit'?, Asbjørn Ulsberg
Re: By way of example., Thomas Broyer
Re: PaceContentNegotiationSection, Thomas Broyer
Re: Re: PaceOnlyMemberURI, Asbjørn Ulsberg
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Joe Gregorio
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Asbjørn Ulsberg
Re: Some editoria of the '09 specification, Joe Gregorio
Re: Some editoria of the '09 specification, James M Snell
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Kyle Marvin
Re: Why MD5 Headers are Imperative, Tim Bray
Re: Why MD5 Headers are Imperative, Tim Bray
Re: Some editoria of the '09 specification, Asbjørn Ulsberg
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Tim Bray
Re: Why MD5 Headers are Imperative, Tim Bray
Re: PaceOnlyMemberURI, Asbjørn Ulsberg
Re: Some editoria of the '09 specification, Tim Bray
Re: PaceOnlyMemberURI, Asbjørn Ulsberg
Re: Why MD5 Headers are Imperative, Roy T. Fielding
Re: PaceOnlyMemberURI, Asbjørn Ulsberg
PaceURINomenclature and PaceOnlyMemberURI, James M Snell
Re: PaceNoServiceDocument, Thomas Broyer
Re: PaceAppModified2 - was Re: Some feedback on current APP issues, Thomas Broyer
Re: Why MD5 Headers are Imperative, Sylvain Hellegouarch
Re: By way of example., Eric J. Bowman
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Andreas Wuest
Re: Why MD5 Headers are Imperative, Eric Scheid
Re: Editorial suggestion: title of Section 8, Sylvain Hellegouarch
Re: PaceContentNegotiationSection, Eric J. Bowman
Re: Editorial suggestion: title of Section 8, Thomas Broyer
Re: Why MD5 Headers are Imperative, Sylvain Hellegouarch
Re: Some feedback on current APP issues, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Posted PaceURINomenclature, Thomas Broyer
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: PaceContentNegotiationSection, Thomas Broyer
Re: Some feedback on current APP issues, Thomas Broyer
Re: Why MD5 Headers are Imperative, Sylvain Hellegouarch
Re: Why MD5 Headers are Imperative, Sylvain Hellegouarch
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Sylvain Hellegouarch
Re: Collection paging section usefulness, Andreas Sewe
Re: Collection paging section usefulness, Andreas Sewe
Re: Why MD5 Headers are Imperative, Michael Wechner
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Elliotte Harold
Re: Why MD5 Headers are Imperative, Elliotte Harold
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Michael Wechner
Search functionality of APP, Michael Wechner
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Sylvain Hellegouarch
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Michael Wechner
Re: Why MD5 Headers are Imperative, Michael Wechner
Re: Some editoria of the '09 specification, Bill de hÓra
Re: Why MD5 Headers are Imperative, Sylvain Hellegouarch
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Julian Reschke
Re: Why MD5 Headers are Imperative, Eric Scheid
link@rel='self' -- different for /collection/entry and link@rel='edit'?, Eric Scheid
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric Scheid
Re: Why MD5 Headers are Imperative, Eric Scheid
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric Scheid
Re: Why MD5 Headers are Imperative, James M Snell
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric Scheid
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: PaceOnlyMemberURI, Roy T. Fielding
Re: Why MD5 Headers are Imperative, Roy T. Fielding
Re: PaceOnlyMemberURI, Roy T. Fielding
Re: Why MD5 Headers are Imperative, Robert Sayre
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, James M Snell
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Joe Gregorio
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Paul Hoffman
Re: Why MD5 Headers are Imperative, Joe Gregorio
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman

August 17, 2006

Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, James M Snell
Re: Why MD5 Headers are Imperative, James M Snell
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: PaceOnlyMemberURI, Eric J. Bowman
Re: Media resources in an entry with APP and PaceCompoundEntry, Ben Bangert
Re: APP with media/docbook, James M Snell
Re: PaceOnlyMemberURI, Lisa Dusseault
Re: APP with media/docbook, Thomas Broyer
Re: PaceOnlyMemberURI, Asbjørn Ulsberg
Re: Collection paging section usefulness, Asbjørn Ulsberg
Some editoria of the '09 specification, Asbjørn Ulsberg
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Asbjørn Ulsberg
Re: Meet the Ape, Asbjørn Ulsberg
Re: Meet the Ape, Asbjørn Ulsberg
Media resources in an entry with APP, Ben Bangert
Re: Why MD5 Headers are Imperative, James M Snell
Re: Why MD5 Headers are Imperative, Tim Bray
Re: Why MD5 Headers are Imperative, Paul Hoffman
Re: Collection paging section usefulness, Michael Wechner
Re: Collection paging section usefulness, Eric Scheid
Re: Collection paging section usefulness, Eric J. Bowman
Re: Collection paging section usefulness, Eric J. Bowman
Re: Collection paging section usefulness, Eric J. Bowman
Re: Collection paging section usefulness, Henry Story
Re: Collection paging section usefulness, Eric J. Bowman
Re: Collection paging section usefulness, Henry Story
Re: Collection paging section usefulness, Henry Story
Re: Collection paging section usefulness, Eric J. Bowman
Collection paging section usefulness, Sylvain Hellegouarch
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Sylvain Hellegouarch
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Fwd: I-D ACTION:draft-nottingham-atompub-feed-history-06.txt, Andreas Sewe
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Henry Story
Re: Why MD5 Headers are Imperative, Julian Reschke
Re: Why MD5 Headers are Imperative, Julian Reschke
Re: Why MD5 Headers are Imperative, Julian Reschke
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: PaceNoServiceDocument, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: PaceOrderCollectionsByAppModified2, Henry Story
Re: Why MD5 Headers are Imperative, Eric Scheid
Re: PaceNoServiceDocument, Henry Story
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: PaceAppModified, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: PaceNoServiceDocument, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Julian Reschke
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, Julian Reschke
Re: PaceNoServiceDocument, Sylvain Hellegouarch
Re: Why MD5 Headers are Imperative, Eric J. Bowman
Re: Why MD5 Headers are Imperative, James M Snell
Re: Why MD5 Headers are Imperative, Julian Reschke
Why MD5 Headers are Imperative, Eric J. Bowman
Re: PaceOnlyMemberURI, Robert Sayre

August 16, 2006

Re: PaceNoServiceDocument, Eric J. Bowman
Re: PaceNoServiceDocument, Eric J. Bowman
Re: PaceOnlyMemberURI, Kyle Marvin
Re: Is xml:base inherited from workspace to collection?, Michael Wechner
Re: PaceOnlyMemberURI, James M Snell
Re: Re: PaceOnlyMemberURI, Robert Sayre
Re: PaceOnlyMemberURI, Tim Bray
Re: PaceOnlyMemberURI, James M Snell
Re: PaceOnlyMemberURI, Tim Bray
Re: PaceOnlyMemberURI, Elias Torres
Re: PaceOnlyMemberURI, James M Snell
Re: PaceOnlyMemberURI, Joe Gregorio
Re: PaceNoServiceDocument, Henry Story
Re: PaceOnlyMemberURI, Kyle Marvin
Re: PaceOnlyMemberURI, Joe Gregorio
Re: Is xml:base inherited from workspace to collection?, James M Snell
Re: PaceOnlyMemberURI, Joe Gregorio
Re: PaceOnlyMemberURI, Henry Story
Re: PaceOnlyMemberURI, James M Snell
Re: scope of xml:base and inheritance, Andreas Wuest
Is xml:base inherited from workspace to collection?, Michael Wechner
Re: scope of xml:base and inheritance, James M Snell
Re: PaceNoServiceDocument, Kyle Marvin
Re: PaceNoServiceDocument, Henry Story
Re: PaceOnlyMemberURI, Joe Gregorio
scope of xml:base and inheritance, Andreas Wuest
Re: PaceNoServiceDocument, Sylvain Hellegouarch
Re: PaceNoServiceDocument, Henry Story
Re: PaceNoServiceDocument, Eric J. Bowman
Re: PaceOnlyMemberURI, Stefan Eissing
Re: PaceNoServiceDocument, Sylvain Hellegouarch
Re: PaceNoServiceDocument, Eric J. Bowman
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Henry Story
Re: PaceOnlyMemberURI, Eric J. Bowman
Re: PaceOnlyMemberURI, Kyle Marvin
Re: PaceOnlyMemberURI, Julian Reschke
Re: PaceOnlyMemberURI, Sylvain Hellegouarch
Re: PaceOnlyMemberURI, Eric J. Bowman
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Henry Story
Re: PaceOnlyMemberURI, Roy T. Fielding
Re: PaceOnlyMemberURI, Sylvain Hellegouarch
Re: PaceOnlyMemberURI, Stefan Eissing
Re: PaceOnlyMemberURI, Eric J. Bowman
Re: PaceOnlyMemberURI, Stefan Eissing
Re: PaceOnlyMemberURI, Eric J. Bowman
Re: PaceOnlyMemberURI, Eric J. Bowman
Re: PaceOnlyMemberURI, James M Snell
Re: PaceOnlyMemberURI, Eric J. Bowman
Re: PaceOnlyMemberURI, James M Snell
Re: PaceOnlyMemberURI, Joe Gregorio
Re: PaceOnlyMemberURI, Eric J. Bowman
Re: PaceAppModified2, Eric Scheid
Re: PaceOnlyMemberURI, Eric J. Bowman
Re: PaceOnlyMemberURI, Eric J. Bowman
Re: PaceOnlyMemberURI, Tim Bray
Re: PaceOnlyMemberURI, Eric J. Bowman
Re: PaceAppModified2, James M Snell
Re: PaceOnlyMemberURI, Joe Gregorio
Re: PaceOnlyMemberURI, Joe Gregorio
Re: PaceOnlyMemberURI, Kyle Marvin
Re: PaceOnlyMemberURI, Elias Torres
Re: PaceAppModified2, Eric J. Bowman
Re: PaceOnlyMemberURI, Joe Gregorio
Re: PaceAppModified2 - was Re: Some feedback on current APP issues, Eric Scheid
Re: PaceOnlyMemberURI, Joe Gregorio
Re: PaceNoServiceDocument - Re: Some feedback on current APP issues, Eric J. Bowman
Re: PaceCollectionLinkType (Was: PaceServiceLinkType), Eric Scheid
Re: PaceAppModified2 - was Re: Some feedback on current APP issues, Eric J. Bowman

August 15, 2006

Re: PaceOnlyMemberURI, Elias Torres
Re: PaceOnlyMemberURI, Kyle Marvin
Clarifying the usage of accept element, Michael Wechner
Re: PaceOnlyMemberURI, Joe Gregorio
FYI... atom client code, James M Snell
Re: PaceOnlyMemberURI, Elias Torres
Re: PaceOnlyMemberURI, Tim Bray
Re: PaceOnlyMemberURI, James M Snell
Re: PaceOnlyMemberURI, Joe Gregorio
Re: PaceOnlyMemberURI, Tim Bray
Re: 8.1 needs a little revision, Joe Gregorio
PaceOnlyMemberURI, Joe Gregorio
Re: PaceCollectionLinkType (Was: PaceServiceLinkType), Elias Torres
Re: PaceCollectionLinkType (Was: PaceServiceLinkType), Joe Gregorio
Re: PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), Joe Gregorio
Re: PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), Joe Gregorio
Re: 8.1 needs a little revision, Henry Story
Aargh. Re: 8.1 needs a little revision, Tim Bray
Re: 8.1 needs a little revision, Tim Bray
Re: 8.1 needs a little revision, Henry Story
Re: PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), Kyle Marvin
Re: PaceCollectionLinkType (Was: PaceServiceLinkType), James M Snell
Re: PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), James M Snell
Re: AtomPubIssuesList for 2006/08/07, Kyle Marvin
Re: PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), James M Snell
Re: PaceCollectionLinkType (Was: PaceServiceLinkType), Elias Torres
Re: 8.1 needs a little revision, Joe Gregorio
Re: Collection Paging, Joe Gregorio
Re: 8.1 needs a little revision, Tim Bray
Re: PaceCollectionLinkType (Was: PaceServiceLinkType), Joe Gregorio
Re: PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), Sylvain Hellegouarch
Collection Paging, Michael Wechner
Re: PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), Henry Story
PaceNoServiceDocument - Re: Some feedback on current APP issues, Henry Story
PaceAppModified2 - was Re: Some feedback on current APP issues, Henry Story
Re: PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), Sylvain Hellegouarch
Re: PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), Joe Gregorio
PaceCollectionLinkType (Was: PaceServiceLinkType), Elias Torres
Re: PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), Kyle Marvin
Re: PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), Elias Torres
Re: 8.1 needs a little revision, Elias Torres
Re: 8.1 needs a little revision, Kyle Marvin
Re: Editorial suggestion: Section 7.2.3, Elias Torres
PaceServiceLinkType (Was: Editorial suggestion: Section 7.2.3), Joe Gregorio
Re: Editorial suggestion: Section 7.2.3, Joe Gregorio
Re: 8.1 needs a little revision, Joe Gregorio
Re: Editorial suggestion: specify PUT & DELETE, Yogesh Mujumdar
Re: Editorial suggestion: title of Section 8, Yogesh Mujumdar
Re: Posted PaceCompoundEntries, Henry Story
Re: Media-link entries and caching, James M Snell

August 14, 2006

Re: Media-link entries and caching, Roy T. Fielding
Re: Media-link entries and caching, Paul Hoffman
Re: Posted PaceURINomenclature, Kyle Marvin
Re: PaceContentNegotiationSection, Lisa Dusseault
Re: Media-link entries and caching, James M Snell
Re: Media-link entries and caching, Roy T. Fielding
Media-link entries and caching, James M Snell
Re: Editorial suggestion: specify PUT & DELETE, Asbjørn Ulsberg
Re: Posted PaceURINomenclature, Asbjørn Ulsberg
Re: Editorial suggestion: Section 7.2.3, Henry Story
Re: Editorial suggestion: Section 7.2.3, James M Snell
Re: Editorial suggestion: Section 7.2.3, Tim Bray
Re: Editorial suggestion: specify PUT & DELETE, James M Snell
Re: Posted PaceURINomenclature, Sylvain Hellegouarch
Re: Posted PaceURINomenclature, Tim Bray
Re: Posted PaceURINomenclature, James M Snell
Re: Posted PaceURINomenclature, Sylvain Hellegouarch
Re: Posted PaceURINomenclature, Tim Bray
Re: Posted PaceURINomenclature, Sylvain Hellegouarch
Re: Posted PaceURINomenclature, James M Snell
Re: Editorial suggestion: Section 7.2.3, Elias Torres
Re: Posted PaceURINomenclature, Bill de hÓra
Re: Editorial suggestion: Section 7.2.3, Bill de hÓra
Re: Editorial suggestion: specify PUT & DELETE, James M Snell
Re: Posted PaceURINomenclature, James M Snell
Editorial suggestion: specify PUT & DELETE, Tim Bray
Posted PaceURINomenclature, Tim Bray
Editorial suggestion: Section 7.1, Tim Bray
Re: Editorial suggestion: title of Section 8, James M Snell
Re: Editorial suggestion: Section 7.2.3, James M Snell
Re: Editorial suggestion, Section 4, Robert Sayre
Editorial suggestion: title of Section 8, Tim Bray
Editorial suggestion: Section 7.2.3, Tim Bray
Editorial selection: section 6, Tim Bray
Editorial suggestion, Section 4, Tim Bray
Re: By way of example., Eric J. Bowman
Re: By way of example., James M Snell
By way of example., Eric J. Bowman

August 13, 2006

Re: 8.1 needs a little revision, Bill de hÓra
Re: 8.1 needs a little revision, Bill de hÓra
Re: 8.1 needs a little revision, Bill de hÓra
Re: AtomPubIssuesList for 2006/08/07, Bill de hÓra
Re: POSTing media content, James M Snell
Re: POSTing media content, Eric Scheid
POSTing media content, Sylvain Hellegouarch
Re: AtomPubIssuesList for 2006/08/07, Henry Story
Re: AtomPubIssuesList for 2006/08/07, James Holderness
Re: AtomPubIssuesList for 2006/08/07, Eric Scheid
Re: PaceContentNegotiationSection, Sylvain Hellegouarch
Re: Some feedback on current APP issues, Eric Scheid
Re: PaceContentNegotiationSection, Eric Scheid
Re: 8.1 needs a little revision, James M Snell
Re: PaceContentNegotiationSection, Eric J. Bowman
Re: 8.1 needs a little revision, Eric Scheid
Re: Some feedback on current APP issues, Eric J. Bowman
Re: PaceContentNegotiationSection, Eric Scheid
Re: PaceContentNegotiationSection, John Panzer
Re: PaceContentNegotiationSection, Eric J. Bowman
Re: 8.1 needs a little revision, Tim Bray
Re: Some feedback on current APP issues, Eric Scheid
Re: 8.1 needs a little revision, James M Snell
Re: PaceContentNegotiationSection, Eric Scheid
Re: 8.1 needs a little revision, Eric Scheid
Re: 8.1 needs a little revision, Tim Bray
Re: Meet the Ape, Tim Bray
Re: 8.1 needs a little revision, John Panzer
Re: 8.1 needs a little revision, Eric Scheid
Re: 8.1 needs a little revision, James M Snell
Re: 8.1 needs a little revision, Tim Bray
Re: 8.1 needs a little revision, James M Snell
Re: 8.1 needs a little revision, Tim Bray
Re: Meet the Ape, Elias Torres
Re: Meet the Ape, Elias Torres
Re: 8.1 needs a little revision, Elias Torres
Re: 8.1 needs a little revision, James M Snell
Re: 8.1 needs a little revision, James M Snell
Re: 8.1 needs a little revision, Joe Gregorio
Re: 8.1 needs a little revision, Tim Bray
Re: 8.1 needs a little revision, Tim Bray
Re: AtomPubIssuesList for 2006/08/07, James M Snell
Re: PaceContentNegotiationSection, Eric J. Bowman
Re: AtomPubIssuesList for 2006/08/07, Joe Gregorio

August 12, 2006

Re: Meet the Ape, Joe Gregorio
Some feedback on current APP issues, Eric J. Bowman
Re: 8.1 needs a little revision, James M Snell
Re: Meet the Ape, James M Snell
Re: Meet the Ape, Tim Bray
8.1 needs a little revision, Tim Bray
Re: Meet the Ape, Julian Reschke
Re: Meet the Ape, Robert Sayre
Re: Meet the Ape, Tim Bray
Re: Meet the Ape, James M Snell
Re: Meet the Ape, Tim Bray
Re: Meet the Ape, Tim Bray
Re: Meet the Ape, Sam Ruby
Re: AtomPubIssuesList for 2006/08/07, Andreas Sewe
Re: Meet the Ape, James M Snell
Re: Meet the Ape, Robert Sayre
Re: Meet the Ape, Tim Bray
Re: Meet the Ape, Sam Ruby
PaceNoServiceDocument (was: AtomPubIssuesList), Sam Ruby
Re: AtomPubIssuesList for 2006/08/07, Mark Baker
Re: AtomPubIssuesList for 2006/08/07, Eric Scheid
Re: AtomPubIssuesList for 2006/08/07, Henry Story
Re: AtomPubIssuesList for 2006/08/07, Sylvain Hellegouarch
Re: AtomPubIssuesList for 2006/08/07, Eric Scheid
Meet the Ape, Tim Bray
Re: PaceRequireContentType, Eric Scheid

August 11, 2006

Re: AtomPubIssuesList for 2006/08/07, Sylvain Hellegouarch
Re: AtomPubIssuesList for 2006/08/07, James M Snell
Re: Introspection document and workspace, James M Snell
Re: AtomPubIssuesList for 2006/08/07, Sylvain Hellegouarch
Re: APP with media/docbook, Joe Gregorio
Re: AtomPubIssuesList for 2006/08/07, Joe Gregorio
Introspection document and workspace, Sylvain Hellegouarch
Re: APP with media/docbook, James Holderness
Re: APP with media/docbook, Michael Wechner
Re: collections, Sylvain Hellegouarch
Re: PaceOrderCollectionsByAppModified2, Eric Scheid

August 10, 2006

Re: collections, Thomas Broyer
Re: Security Considerations, Robert Sayre
Re: Security Considerations, Eric Rescorla
Re: Security Considerations, Robert Sayre
Re: collections, Duncan Cragg
Re: Security Considerations, Eric Rescorla
Re: Security Considerations, Robert Sayre
Re: Security Considerations, Eric Rescorla
Re: Re: Security Considerations, Robert Sayre
Re: APP with media/docbook, Ben Bangert
Re: APP with media/docbook, Ben Bangert
Re: Security Considerations, Eric Rescorla
Re: Security Considerations, Robert Sayre
Re: Security Considerations, Eric Rescorla
Re: Security Considerations, Eric Rescorla
Re: APP with media/docbook, Tim Bray
Re: Security Considerations, Robert Sayre
Re: Security Considerations, Eric Rescorla
Re: APP with media/docbook, Thomas Broyer
Re: Re: PaceSecurityConsiderations and PaceAuthenticationAndSecurityConsiderations, Robert Sayre
Re: PaceSecurityConsiderations and PaceAuthenticationAndSecurityConsiderations, Paul Hoffman
Re: PaceOrderCollectionsByAppModified2, Thomas Broyer
Re: APP with media/docbook, James M Snell
Fwd: eBay: Secure SSL Certificates at Low Prices!!!! (item 5879247587 end time Sep-07-06 23:01:15 PDT), Robert Sayre
Re: AtomPubIssuesList for 2006/08/07, Thomas Broyer
Re: APP with media/docbook, Sylvain Hellegouarch
Re: APP with media/docbook, Michael Wechner
Re: PaceOrderCollectionsByAppModified2, Henry Story
Re: PaceOrderCollectionsByAppModified2, Eric Scheid
Re: AtomPubIssuesList for 2006/08/07, Sam Ruby
Re: PaceOrderCollectionsByAppModified2, James M Snell
Re: AtomPubIssuesList for 2006/08/07, Eric Scheid
PaceOrderCollectionsByAppModified2, Eric Scheid
Re: collections (was: Last whack at the issues), Eric Scheid
Re: Last whack at the issues, Duncan Cragg
Re: Last whack at the issues, James M Snell

August 09, 2006

Re: AtomPubIssuesList for 2006/08/07, John Panzer
Re: Last whack at the issues, Paul Hoffman
APP with media/docbook, Ben Bangert
Re: Last whack at the issues, James M Snell
Last whack at the issues, Tim Bray
Re: status of atom introspection discovery, Tim Bray
Re: Preserve foreign markup is one-way?, James M Snell
Re: Preserve foreign markup is one-way?, Sylvain Hellegouarch

August 08, 2006

Re: Preserve foreign markup is one-way?, Bill de hÓra
Re: Preserve foreign markup is one-way?, James M Snell
Preserve foreign markup is one-way?, Tim Bray
Re: PaceRealisticSecurity, James M Snell
Re: PaceRealisticSecurity, James M Snell
Re: PaceRealisticSecurity, Robert Sayre
Re: PaceRealisticSecurity, James M Snell
Re: PaceRealisticSecurity (was: AtomPubIssuesList for 2006/08/07), Robert Sayre
Re: PaceRealisticSecurity (was: AtomPubIssuesList for 2006/08/07), James M Snell
Re: PaceRealisticSecurity (was: AtomPubIssuesList for 2006/08/07), Robert Sayre

August 07, 2006

Re: PaceRealisticSecurity (was: AtomPubIssuesList for 2006/08/07), James M Snell
Re: PaceRealisticSecurity (was: AtomPubIssuesList for 2006/08/07), Robert Sayre
Re: PaceRealisticSecurity (was: AtomPubIssuesList for 2006/08/07), Bill de hÓra
PaceSecurityConsiderations and PaceAuthenticationAndSecurityConsiderations, James M Snell
Re: PaceRealisticSecurity (was: AtomPubIssuesList for 2006/08/07), Paul Hoffman
Re: PaceRealisticSecurity (was: AtomPubIssuesList for 2006/08/07), Robert Sayre
Re: PaceRealisticSecurity (was: AtomPubIssuesList for 2006/08/07), Paul Hoffman
Survey on service & introspection & so on, Tim Bray
Re: AtomPubIssuesList for 2006/08/07, James M Snell
Re: PaceRealisticSecurity (was: AtomPubIssuesList for 2006/08/07), James M Snell
Re: Security Considerations, Robert Sayre
PaceRealisticSecurity (was: AtomPubIssuesList for 2006/08/07), Robert Sayre
AtomPubIssuesList for 2006/08/07, Sam Ruby

August 06, 2006

Re: Posted PaceRealisticSecurity, Robert Sayre
Posted PaceRealisticSecurity, Robert Sayre
Re: Implement vs deploy, John Panzer
Re: Implement vs deploy, Mark Baker
Re: Implement vs deploy, John Panzer
Re: Implement vs deploy, Ted Hardie
Re: Implement vs deploy, Robert Sayre
Re: Implement vs deploy, Paul Hoffman
Re: Implement vs deploy, Robert Sayre
Re: Implement vs deploy, Bill Fenner
Re: Implement vs deploy, Sam Ruby
Re: Implement vs deploy, Robert Sayre
Re: Implement vs deploy, Paul Hoffman
Re: Implement vs deploy, Bill de hÓra
Re: Implement vs deploy (was: interoperibility & quality), Robert Sayre

August 05, 2006

Re: Implement vs deploy (was: interoperibility & quality), Ted Hardie
Re: Implement vs deploy, Sam Ruby
Re: Implement vs deploy, James M Snell
Re: Implement vs deploy (was: interoperibility & quality), Cullen Jennings

August 04, 2006

Re: Implement vs deploy resolution, James M Snell
Re: Conformance Levels, James M Snell
Implement vs deploy resolution, Joe Gregorio
Re: Conformance Levels (was: Re: Forking), John Panzer
Re: Versioning, Sam Hartman
Re: Conformance Levels, Tim Bray
Re: Implement vs deploy (was: interoperibility & quality), Ted Hardie
Conformance Levels (was: Re: Forking), James M Snell
Security Considerations, Pace update, James M Snell
Re: Versioning, Bill de hÓra
Re: Versioning, Sam Hartman
Re: Forking, Robert Sayre
Implement vs deploy (was: interoperibility & quality), Sam Ruby
Re: Versioning [was Forking], Bill de hÓra
Re: Forking, Brian E Carpenter
Re: Forking, Brian E Carpenter
Re: Versioning [was Forking], Brian E Carpenter
Re: Forking, Bill de hÓra
Re: Comment on interoperibility & protocol quality, Robert Sayre
Re: Comment on interoperibility & protocol quality, Robert Sayre
Re: Comment on interoperibility & protocol quality, Eric Rescorla
Re: Comment on interoperibility & protocol quality, Eric Rescorla
Re: Comment on interoperibility & protocol quality, Ted Hardie
Re: Comment on interoperibility & protocol quality, Robert Sayre
Re: Comment on interoperibility & protocol quality, Eric Rescorla
Re: Forking, James M Snell
Re: Comment on interoperibility & protocol quality, Robert Sayre
Re: Comment on interoperibility & protocol quality, Eric Rescorla
Re: Forking, Paul Hoffman
Re: Comment on interoperibility & protocol quality, Eric Rescorla
Re: Comment on interoperibility & protocol quality, Robert Sayre
Re: Comment on interoperibility & protocol quality, Bill de hÓra

August 03, 2006

Comment on interoperibility & protocol quality, Cullen Jennings
Re: Forking, Bill de hÓra
Re: PUT and DELETE, Mark Nottingham
Re: Forking, Robert Sayre
Re: Forking, Eric Rescorla
Re: Forking, Paul Hoffman
Re: Re: Forking, Robert Sayre
Re: Forking, Bill de hÓra
Re: Forking, Robert Sayre
Re: Forking, Bill de hÓra
Versioning [was Forking], Bill de hÓra
Re: Forking, Sam Ruby
Re: Re: Forking, Robert Sayre
Re: Security Considerations, Bill de hÓra
Re: Forking, Sam Hartman
Re: Security Considerations, Bill de hÓra
Re: Forking (was: Security Considerations), Robert Sayre
Re: Security Considerations, Sam Hartman
Re: Security Considerations, Sam Hartman
Forking (was: Security Considerations), Sam Ruby
Re: Security Considerations, Julian Reschke
Re: Security Considerations, Lisa Dusseault
Re: Security Considerations, Tim Bray
Re: Security Considerations, Robert Sayre
Re: Security Considerations, James M Snell
Re: Security Considerations, Joe Gregorio
Re: Security Considerations, James M Snell
Re: Security Considerations, Sam Hartman
Re: Security Considerations, Robert Sayre
Re: Security Considerations, Bill de hÓra
Re: Security Considerations, Robert Sayre
Re: Security Considerations, James M Snell
Re: Security Considerations, Eric Rescorla
Re: Security Considerations, James M Snell
Re: Security Considerations, Robert Sayre
Re: Security Considerations, Eric Rescorla
Re: Security Considerations, Robert Sayre
Re: Security Considerations, Sam Hartman
Re: Security Considerations, Brian E Carpenter
Re: Security Considerations, Brian E Carpenter
Re: Security Considerations, Sylvain Hellegouarch
Re: Security Considerations, Roy T. Fielding

August 02, 2006

Re: Security Considerations, Robert Sayre
Re: Security Considerations, Brian E Carpenter
Re: Re: Security Considerations, Robert Sayre
Re: Security Considerations, Brian E Carpenter
Re: Security Considerations, Roy T. Fielding

August 01, 2006

Re: PaceAppModified, Henry Story
Re: Security Considerations, Robert Sayre

News | FAQ | advertise