Fwd: Problem beyond the design decision of HttpRange-14
Call for Two Year Feature Freeze -- to httpRange-14 resolution
- Re: Call for Two Year Feature Freeze -- to httpRange-14 resolution
- Re: Call for Two Year Feature Freeze -- to httpRange-14 resolution
- Re: Call for Two Year Feature Freeze -- to httpRange-14 resolution
Microsoft HTTP S&M
Proposal to amend the httpRange-14 resolution [revision]
Re: httpRange-14 Change Proposal [editorial tweaks]
- Re: httpRange-14 Change Proposal [editorial tweaks]
- Re: httpRange-14 Change Proposal [editorial tweaks]
- Re: httpRange-14 Change Proposal [editorial tweaks]
- Re: httpRange-14 Change Proposal [editorial tweaks]
Classification of ISSUE-57 change proposals
- Re: Classification of ISSUE-57 change proposals
Fragment identifiers, RFC3023bis: Preparing for the F2F (ACTION-675)
There will be no TAG teleconference tomorrow, 29 March 2012
httpRange-14 Conformance
The TAG Member's Guide to ISSUE-57 Discussion - F2F reading
- Re: The TAG Member's Guide to ISSUE-57 Discussion - F2F reading
Privacy by Design in APIs
ISSUE-57 F2F reading
Minutes from March 15 TAG Telcon
Brass Tacks
URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
- Re: URIs, used in RDF, that do not have associated documentation
Middle ground change proposal for httpRange-14 -- submission
- Re: Middle ground change proposal for httpRange-14 -- submission
How to move ISSUE-57 off the TAG's plate
Re: Change Proposal for HttpRange-14
Change Proposal 25 for HttpRange-14
Happy 10th birthday ISSUE-14
TAG prep for ISSUE-57 (httpRange-14, etc.) session
httpRange-14 Change Proposal
- Re: httpRange-14 Change Proposal
- Re: httpRange-14 Change Proposal
- Re: httpRange-14 Change Proposal
- Re: httpRange-14 Change Proposal
- Re: httpRange-14 Change Proposal
- Re: httpRange-14 Change Proposal
- Re: httpRange-14 Change Proposal
- Re: httpRange-14 Change Proposal
Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
- Re: Proposal to amend the httpRange-14 resolution
Minutes of TAG teleconference of 22 March 2012
Preliminary TAG F2F Agenda ready for review
Agenda for TAG call on 22 April 2011
Draft F2F agenda entry on copyright and linking
- Re: Draft F2F agenda entry on copyright and linking
- Re: Draft F2F agenda entry on copyright and linking
Need link to Copyright & Linking draft for F2F required reading
ACTION-647 Product page for Client-side Storage
Invitation to meet with the TAG
ACTION-678: Fwd: Dom visiting the TAG
Agenda for the TAG teleconference of 15 March 2012
ACTION-560: Polyglot documents
Draft on Web App storage for TAG F2F
Requesting update on HTML/XML unification work
- Re: Requesting update on HTML/XML unification work
- Re: Requesting update on HTML/XML unification work
Meeting with the TAG to discuss RFC 3023bis and fragment identifier semantics
Minutes from March 08 TAG Telcon
Agenda for TAG teleconference of 8 March - F2F planning
TAG liaison at IETF Paris
Re: ACTION 610: Draft Meta Formats section for W3C site
- Re: ACTION 610: Draft Meta Formats section for W3C site
- Re: ACTION 610: Draft Meta Formats section for W3C site
- Re: ACTION 610: Draft Meta Formats section for W3C site
Draft minutes of TAG telcon 2012-03-01
Fwd: http+aes URI scheme
HTTP Range 14
Re: Understanding URI Hosting Practice as Support for Documentation Discovery: 'meaning of meaning'
either strengthen or retract httpRange-14(a)
FW: Minutes of the W3C/IETF Coordination Call, 2012-02-28
Two httpRange-14 change proposals
Re: Call for proposals to amend the "httpRange-14 resolution"
- Re: Call for proposals to amend the "httpRange-14 resolution"
- Re: Call for proposals to amend the "httpRange-14 resolution"