Leveraging 2^W For Accessibility
"Cool Uris" is a working draft - addressed issues
[ACTION-28] Blog entry on Version Identifiers posted
[httpRange-14] Conneg and Acceptable HTTP Variants
[httpRange-14] What is an Information Resource?
- Re: [httpRange-14] What is an Information Resource?
- Re: [httpRange-14] What is an Information Resource?
- Re: [httpRange-14] What is an Information Resource?
- Re: [httpRange-14] What is an Information Resource?
- Re: [httpRange-14] What is an Information Resource?
- Re: [httpRange-14] What is an Information Resource?
- Re: [httpRange-14] What is an Information Resource?
ISSUE-60 (webApplicationState-48): Web Application State Management
- webApplicationState-60 (was RE: ISSUE-60 (webApplicationState-48): Web Application State Management)
A couple of versioning personal blog entries
TAG telcon Agenda for 13th Dec 2007: Rich Web Clients; httpredirections-57;Reviews; ping attribute;
- RE: TAG telcon Agenda for 13th Dec 2007: Rich Web Clients; httpredirections-57;Reviews; ping attribute;
- TAG telcon Minutes for 13th Dec 2007
ACTION-83: Review http://www.w3.org/TR/access-control/
Sad news from Cleveland
Sad news from Cleveland
Re: TAG input to EXI WG on Efficient XML Interchange and EXI Measurements
Minutes from TAG telcon of 2007-11-29
Re: New draft of Associating Resources with Namespaces
RE: New draft of Associating Resources with Namespaces
RE: New draft of Elaborated Infosets document (xmlFunctions-34)
TAG Telcon Agenda 6th Dec 2007: xmlFunctions-34; namespaceDocument-8; httpRedirections-57; Rich Web Clients
httpRange-14 - what are the use-cases?
Re: The meaning of "representation"
- Re: The meaning of "representation"
httpRange-14 Two Years On
Re: httpRange-14: Consequences of redirection
RE: httpRange-14 Adjunct: 302 is Valid for Non-Information Resources
- Re: httpRange-14 Adjunct: 302 is Valid for Non-Information Resources
- Re: httpRange-14 Adjunct: 302 is Valid for Non-Information Resources
- Alternative to 303 response: Description-ID: header
- Re: Alternative to 303 response: Description-ID: header
- Re: Alternative to 303 response: Description-ID: header
- Re: Alternative to 303 response: Description-ID: header
- Re: Alternative to 303 response: Description-ID: header
- Re: Alternative to 303 response: Description-ID: header
- Re: Alternative to 303 response: Description-ID: header
- Re: Alternative to 303 response: Description-ID: header
- Re: Alternative to 303 response: Description-ID: header