*。。連鎖超商邀你加盟。。*
Comments on arch doc draft
- RE: Comments on arch doc draft
- Re: Comments on arch doc draft
- RE: Comments on arch doc draft
- RE: Comments on arch doc draft
[Agenda] 1 July TAG teleconf (arch doc, qnames, formatting properties, URI equiv, RFC3023, SOAP/WSDL)
[Minutes] 24 June 2002 TAG teleconference (Arch doc, qnameAsId-18, SOAP/WSDL/GET)
- Re: [Minutes] 24 June 2002 TAG teleconference (Arch doc, qnameAsId-18, SOAP/WSDL/GET)
- Re: [Minutes] 24 June 2002 TAG teleconference (Arch doc, qnameAsId-18, SOAP/WSDL/GET)
PSVI architectural discussion
My review of 0607 document
Draft agenda: 24 June TAG teleconference (Arch document, WSA update)
- RE: Draft agenda: 24 June TAG teleconference (Arch document, WSA update)
- Re: Draft agenda: 24 June TAG teleconference (Arch document, WSA update)
- Re: Draft agenda: 24 June TAG teleconference (Arch document, WSA update)
Re: Proposed TAG Finding: Using Qualified Names (QNames) as Identifiers in Content
[Minutes] 17 June TAG teleconf (Infoset/PSVI, XLink, Style properties, Qnames, Mime registration)
RE: Proposed TAG Finding: Using Qualified Names (QNames) as Ident ifiers in Content
Summary of resolution to TAG Get finding
Proposed TAG Finding: Using Qualified Names (QNames) as Identifiers in Content
- Re: Proposed TAG Finding: Using Qualified Names (QNames) as Identifiers in Content
- Typo (Re: Proposed TAG Finding: Using Qualified Names (QNames) as Identifiers in Content)
- Re: Proposed TAG Finding: Using Qualified Names (QNames) as Identifiers in Content
- Re: Proposed TAG Finding: Using Qualified Names (QNames) as Identifiers in Content
- Re: Proposed TAG Finding: Using Qualified Names (QNames) as Identifiers in Content
- A radical finding on Using Qualified Names (QNames) as Identifiers in Content
Draft TAG Finding: Consistency of Formatting Properties
超值雙組合=駭客技術加新名單 LdiWkZ21G9g5mfw
Bad practice: Overriding HTTP content-type with a URI reference
XLINK, HLINK or neither? Possible new TAG issue
[Agenda] 17 June TAG teleconf (SOAP/GET update, charmodReview-17 update, URIEquivalence-15)
Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- Re: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- Re: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- Re: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- Re: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- Re: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- RE: Potential new issue: PSVI considered harmful
- Re: Potential new issue: PSVI considered harmful
TAG Finding: URIs, Addressability, and the use of HTTP GET
Dissent: Internet Media Type registration, consistency of use
- Re: Dissent: Internet Media Type registration, consistency of use
- Re: Dissent: Internet Media Type registration, consistency of use
- Suggestion: Internet Media Type registration, consistency of use
Minutes of 10 June 2002 TAG teleconf
Summary of TAG activity 10 May - 9 June 2002
Re: Proposed TAG Finding: Internet Media Type registration, consistency of use
charset diagram: relevance? bugs?
Re: Proposed TAG Finding: Internet Media Type registration, consistency of use
Two messages from James Clark that ought to be read
- Re: Two messages from James Clark that ought to be read
- Re: Two messages from James Clark that ought to be read
Re: [uriMediaType-9] Dear IETF ...
Re: [URIEquivalence-15] Namespaces in XML -- URI, IRIs and equivalence
- Re: [URIEquivalence-15] Namespaces in XML -- URI, IRIs and equivalence
- Re: [URIEquivalence-15] Namespaces in XML -- URI, IRIs and equivalence
[Agenda] 10 June 2002 TAG teleconf (whenToUseGet-7, qnameAsId, charmodReview-17, URIEuivalence-15)
[Fwd: announcing public-ietf-w3c@w3.org]
Re: [charmodReview-17] "security problems" with Unicode homographs
Re: Proposed TAG Finding: Internet Media Type registration, consistency of use
Updated: issue qnameAsId-18
- Re: Updated: issue qnameAsId-18
- Re: Updated: issue qnameAsId-18
TAG comments on Character Model for the World Wide Web 1.0
[Minutes] 3 June TAG teleconference (errorHandling-20, w3cMediaType-1, RFC3023-charset-21, charmodReview-17, whenToUseGet-7)
RE: New issue: error recovery practices (Re: Proposed TAG Finding : Internet Media Type registration, consistency of use)
Re: New issue: error recovery practices (Re: Proposed TAG Finding: Internet Media Type registration, consistency of use)
Re: URIEquivalence-15 and IRIs
- off topic (was Re: URIEquivalence-15 and IRIs)
- Re: URIEquivalence-15 and IRIs
- Re: URIEquivalence-15 and IRIs
- Re: URIEquivalence-15 and IRIs
- Re: URIEquivalence-15 and IRIs
[namespaceDocument-8] RDF in HTML: Approaches
Re: New issue: error recovery practices (Re: Proposed TAG Finding: Internet Media Type registration, consistency of use)
- Re: New issue: error recovery practices (Re: Proposed TAG Finding: Internet Media Type registration, consistency of use)
- Re: New issue: error recovery practices (Re: Proposed TAG Finding: Internet Media Type registration, consistency of use)
- Re: New issue: error recovery practices (Re: Proposed TAG Finding: Internet Media Type registration, consistency of use)
- Re: New issue: error recovery practices (Re: Proposed TAG Finding: Internet Media Type registration, consistency of use)