Tuesday, 29 November 2011
Monday, 28 November 2011
Thursday, 24 November 2011
- Re: Agreement on IRI "processing spec" moving to W3C
- Re: Agreement on IRI "processing spec" moving to W3C
- Re: Agreement on IRI "processing spec" moving to W3C
- Re: Agreement on IRI "processing spec" moving to W3C
- Re: Agreement on IRI "processing spec" moving to W3C
- Re: Agreement on IRI "processing spec" moving to W3C
Monday, 21 November 2011
- IRI session recording available
- Re: Agreement on IRI "processing spec" moving to W3C
- Re: Agreement on IRI "processing spec" moving to W3C
Sunday, 20 November 2011
- RE: Agreement on IRI "processing spec" moving to W3C
- Re: Agreement on IRI "processing spec" moving to W3C
- Re: Agreement on IRI "processing spec" moving to W3C
- Agreement on IRI "processing spec" moving to W3C
Thursday, 17 November 2011
- iri meeting minutes
- Re: [iri] #85: Align terminology in 3987bis with RFC 6365 (was: Align terminology in 3987bis with 3536bis)
- [iri] #107: Clarify requirement for security considerations
- Re: [iri] #106: Restore text about reverse domain name use for private URI/IRI schemes
- Re: [iri] #73: Decide on organization-specific schemes
- Re: 4395 bis comments
- RE: 4395 bis comments
Wednesday, 16 November 2011
- Meetecho support for IRI WG meeting session
- Re: [iri] #5: Separate IRI from "presentation of IRI" as concepts
Tuesday, 15 November 2011
- Re: [iri] #106: Restore text about reverse domain name use for private URI/IRI schemes
- Re: [iri] #2: Need better definition of "absolute URL" as used in HTML5 (and #1)
- Re: [iri] #24: sort out issues between IRIs and HTML form upload
- Re: [iri] #2: Need better definition of "absolute URL" as used in HTML5 (and #1)
- Re: [iri] #2: Need better definition of "absolute URL" as used in HTML5
- Re: [iri] #1: need better definition of "valid URL" as used in HTML5
- Re: [iri] #1: need better definition of "valid URL" as used in HTML5
- [iri] #106: Restore text about reverse domain name use for private URI/IRI schemes
Monday, 14 November 2011
- RE: [iri] #5: Separate IRI from "presentation of IRI" as concepts
- Re: [iri] #6: Allow "best practices for BIDI IRIs" to be separate document
- Re: [iri] #5: Separate IRI from "presentation of IRI" as concepts
- Re: key IRI issues
Saturday, 12 November 2011
- key IRI issues
- [iri] #85: Align terminology in 3987bis with 3536bis
- [iri] #92: Sections 3.4 & 3.5 should be moved into Section 3.6 of 3987bis
Friday, 11 November 2011
- [iri] #24: sort out issues between IRIs and HTML form upload
- [iri] #2: Need better definition of "absolute URL" as used in HTML5
- [iri] #1: need better definition of "valid URL" as used in HTML5
- [iri] #5: Separate IRI from "presentation of IRI" as concepts
- [iri] #6: Allow "best practices for BIDI IRIs" to be separate document
Saturday, 12 November 2011
Friday, 11 November 2011
- Re: [iri] #44: Reference Unicode TR 46, and if yes, how?
- Re: [iri] #44: Reference Unicode TR 46, and if yes, how?
Wednesday, 9 November 2011
- Re: [iri] #44: Reference Unicode TR 46, and if yes, how?
- Re: [iri] #44: Reference Unicode TR 46, and if yes, how?
- Re: IETF 82 Agenda and call for presenters
- Re: Bidi IRI with a Bidi TLD
- Re: [iri] #44: Reference Unicode TR 46, and if yes, how?
- Re: [iri] #104: Characters are still excluded from URIs
- Re: [iri] #47: Practical length limits on IRIs or components thereoff
- Re: [iri] #27: do we need to say anything special about ZWNJ and ZWJ?
- Re: [iri] #99: New schemes should make sure query part uses UTF-8
Tuesday, 8 November 2011
Monday, 7 November 2011
- Re: -08 nits: W3C references
- Re: Bidi IRI with a Bidi TLD
- Re: Bidi IRI with a Bidi TLD
- Re: Bidi IRI with a Bidi TLD
- Re: Bidi IRI with a Bidi TLD
Sunday, 6 November 2011
Saturday, 5 November 2011
- Fw: blog post: How many ways can you slice a URL and name the pieces?
- Bidi IRI with a Bidi TLD
- Re: IETF 82 Agenda and call for presenters
- RE: URL parsing in HTML5
- Re: URL parsing in HTML5
Wednesday, 2 November 2011
Friday, 4 November 2011
- Re: URL parsing in HTML5
- Re: URL parsing in HTML5
- Re: URL parsing in HTML5
- Re: URL parsing in HTML5
- Re: URL parsing in HTML5
- Re: URL parsing in HTML5
- Re: URL parsing in HTML5
- Re: URL parsing in HTML5
- Re: IETF 82 Agenda and call for presenters
- Re: URL parsing in HTML5
- URL parsing in HTML5