public-iri@w3.org from June 2011 by date

Wednesday, 29 June 2011

• Re: canonical form and scheme-specific processing rules for URI/IRI spec Boris Zbarsky
• Re: canonical form and scheme-specific processing rules for URI/IRI spec Julian Reschke
• Re: canonical form and scheme-specific processing rules for URI/IRI spec Adam Barth
• canonical form and scheme-specific processing rules for URI/IRI spec Chris Weber

Tuesday, 28 June 2011

• Re: same-document references Boris Zbarsky
• RE: same-document references Larry Masinter

Sunday, 26 June 2011

• Re: same-document references Boris Zbarsky
• RE: same-document references Larry Masinter
• Re: same-document references Boris Zbarsky
• Re: same document reference in emailed HTML Anne van Kesteren

Saturday, 25 June 2011

• same document reference in emailed HTML Larry Masinter
• RE: same-document references Larry Masinter
• Re: same-document references Boris Zbarsky

Friday, 24 June 2011

• RE: same-document references Larry Masinter
• Re: same-document references Boris Zbarsky
• same-document references Julian Reschke

Thursday, 23 June 2011

• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Bjoern Hoehrmann
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Bjoern Hoehrmann
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Anne van Kesteren
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Some remarks on 4395bis Mykyta Yevstifeyev
• Re: parsing URI (references) according to RFC 3986 Julian Reschke

Wednesday, 22 June 2011

• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: space-separated URI references in HTML Anne van Kesteren

Tuesday, 21 June 2011

• Re: space-separated URI references in HTML Edward O'Connor
• space-separated URI references in HTML Chris Weber

Monday, 20 June 2011

• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: making interoperability decisions (was Re: parsing URI (references) according to RFC 3986) Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: making interoperability decisions (was Re: parsing URI (references) according to RFC 3986) Adam Barth
• Re: making interoperability decisions (was Re: parsing URI (references) according to RFC 3986) Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: making interoperability decisions (was Re: parsing URI (references) according to RFC 3986) Martin J. Dürst
• Re: parsing URI (references) according to RFC 3986 Chris Weber
• Re: making interoperability decisions (was Re: parsing URI (references) according to RFC 3986) Martin J. Dürst
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Chris Weber
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: parsing URI (references) according to RFC 3986 Chris Weber
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Chris Weber
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: making interoperability decisions (was Re: parsing URI (references) according to RFC 3986) Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: making interoperability decisions (was Re: parsing URI (references) according to RFC 3986) Adam Barth
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• making interoperability decisions (was Re: parsing URI (references) according to RFC 3986) Chris Weber
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: requesting feedback regarding HTML5 and RFC 3987 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: parsing URI (references) according to RFC 3986 Boris Zbarsky
• Re: requesting feedback regarding HTML5 and RFC 3987 Adam Barth
• Re: requesting feedback regarding HTML5 and RFC 3987 Boris Zbarsky
• Re: requesting feedback regarding HTML5 and RFC 3987 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Adam Barth

Sunday, 19 June 2011

• Re: parsing URI (references) according to RFC 3986 Chris Weber
• Re: parsing URI (references) according to RFC 3986 Chris Weber
• Re: requesting feedback regarding HTML5 and RFC 3987 Adam Barth
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: requesting feedback regarding HTML5 and RFC 3987 Julian Reschke
• Re: requesting feedback regarding HTML5 and RFC 3987 Boris Zbarsky
• Re: requesting feedback regarding HTML5 and RFC 3987 Boris Zbarsky
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• Re: requesting feedback regarding HTML5 and RFC 3987 Bjoern Hoehrmann

Saturday, 18 June 2011

• Re: IETF 80 IRI Working Group Meeting Minutes Anne van Kesteren
• Re: requesting feedback regarding HTML5 and RFC 3987 Anne van Kesteren
• Re: parsing URI (references) according to RFC 3986 Chris Weber
• Re: parsing URI (references) according to RFC 3986 Chris Weber
• Re: parsing URI (references) according to RFC 3986 Julian Reschke
• Re: parsing URI (references) according to RFC 3986 Adam Barth
• parsing URI (references) according to RFC 3986 Julian Reschke

Friday, 17 June 2011

• Last Call for HTML5 in the W3C Mark Nottingham

Monday, 13 June 2011

• Re: BIDI? Adil Allawi

Sunday, 12 June 2011

• Re: BIDI? Slim Amamou
• RE: BIDI? Shawn Steele

Saturday, 11 June 2011

• Re: BIDI? Adil Allawi

Tuesday, 7 June 2011

• Re: [bidi] BIDI? Adil Allawi

Monday, 6 June 2011

• Re: [bidi] BIDI? Adil Allawi
• RE: [bidi] BIDI? Larry Masinter
• Re: [bidi] BIDI? Aharon (Vladimir) Lanin

Sunday, 5 June 2011

• RE: [bidi] BIDI? Shawn Steele
• Re: [bidi] BIDI? Aharon (Vladimir) Lanin
• Re: [bidi] BIDI? Matitiahu Allouche
• Re: [bidi] Re: BIDI? Aharon (Vladimir) Lanin
• RE: [bidi] Re: BIDI? Shawn Steele
• Re: [bidi] Re: BIDI? Matitiahu Allouche

Friday, 3 June 2011

• Re: Discussion of Blob URI Scheme for Binary Data Access | IETF Graham Klyne
• Re: Are minutes going to be published soon John C Klensin
• requesting feedback regarding HTML5 and RFC 3987 Chris Weber
• Re: [bidi] Re: BIDI? Mohamed Mohie
• Comments on "URI Fragment Identifiers for the text/csv Media Type" Richard Cyganiak

Thursday, 2 June 2011

• Re: Aligning IRI specification with HTML5 (was Re: requesting feedback regarding HTML5 and RFC 3987) Peter Saint-Andre

Wednesday, 1 June 2011

• Re: Aligning IRI specification with HTML5 (was Re: requesting feedback regarding HTML5 and RFC 3987) Bjoern Hoehrmann
• Re: nit comment Martin J. Dürst
• Re: requesting feedback regarding HTML5 and RFC 3987 Peter Saint-Andre

Last message date: Wednesday, 29 June 2011 15:00:55 UTC