www-tag@w3.org from July 2002 by subject

"URIs, Addressability, and the use of HTTP GET"

[Agenda] 15 July TAG teleconf (arch doc, qnames, formatting props, httpRange-14)

[Agenda] 22 July TAG teleconference (arch doc, httpRange-14,...)

[Agenda] 29 July 2002 TAG teleconf (arch doc, httpRange-14, URIEquivalence-15)

[Agenda] 8 July TAG teleconf (httpRange-14, uriMediaType-9, URIEquivalence-15)

[contentTypeOverride-24] Can a specification include rules for overriding HTTP content type parameters?

[deepLinking-25] What to say in defense of principle that dee p linking is not an illegal act?

[deepLinking-25] What to say in defense of principle that deep linking is not an illegal act?

[Finding] Consistency of Formatting Property Names, Values, and Semantics

[Finding] Using Qualified Names (QNames) as Identifiers in Co ntent

[Finding] Using Qualified Names (QNames) as Identifiers in Content

[httpRange-14] range of mid:, tel:, uuid: etc.

[httpRange-14] Re: fragment identifiers

[httpRange-14] What do HTTP URIs Identify?

[Minutes] 1 July TAG teleconf (SOAP last call, xlinkScope-23, Arch Doc and httpRange-14)

[Minutes] 15 July TAG teleconf (arch doc, qnames as ids, formatting props, httpRange-14)

[Minutes] 22 July TAG teleconf (arch doc, httpRange-14, uriMediaType-9, URIEquivalence-15)

[Minutes] 29 July TAG teleconf (httpRange-14, URIEquivalence-15)

[Minutes] 8 July TAG teleconf (arch doc, media types, formatting props, whenToUseGet-7, augmentedInfoset-22)

[w3cMediaType-1] How to Register an Media Type with IANA

A radical finding on Using Qualified Names (QNames) as Identifiers in Content

Arch doc: meaning of term 'representation'?: Re: TB16 Re: Comments on arch doc draft

Arch doc: meaning of term 'representation'?: Re: TB16 Re:Comments on arch doc draft

Architecture Document: Terminology: Dereferencable, Retrivabl e, R esolvable.

Architecture Document: Terminology: Dereferencable, Retrivable, R esolvable.

ConegFragment (was Re: Early draft of Architecture Document for your review

Context Independent URI

customMediaType-2 : charset in RFC 3023

Draft TAG Finding: Consistency of Formatting Properties

Early draft of Architecture Document for your review

Fixed Section 1.1 language

fragment identifiers

Fragment identifiers and intermediaries

httpRange proposed text

httpRange-14 , what's the problem

httpRange-14; closer than we think to closing it?

I'd like to un-raise augmentedInfoset-22

Infoset consistency between versions

Internet Media Type registration Re: [Minutes] 8 July TAG teleconf (arch doc, media types, formatting props, whenToUseGet-7, augmentedInfoset-22)

Just updated s1.1 arch doc draft again

Maintaining uniformity with HTTP URIs

Namespace document and representations was Re: Arch doc: meaning of term 'representation'?

On XPointer and the context-independence of URIs

Potential wild-card issue outside W3C: legality of deep linking

Proposed TAG Finding: Using Qualified Names (QNames) as Ident ifiers in Content

QNames and the XPointer namespace scheme

range of http: modeling HTTP in RDF

Range of Web architecture? (was Re: Early draft of Architecture Document for your review

Representations of Resources and Precision of Denotation (was Re: TB16 Re: Comments on arch doc draft)

Republished finding: Using Qualified Names (QNames) as Identifiers in Content

resource and representation

resource and representation (and fragment identifiers)

resource equivalence was: Re: fragment identifiers

Resource references/httpRange-14 (was: [Minutes] 1 July TAG teleconf)

Section 1.1 Characteristics of URIs: Minor editorial

Some comments on latest draft

Summary of TAG activity from 9 June to 2 July 2002

TAG Finding: Using Qualified Names (QNames) as Identifiers in Content

Taxis via HTTP? [Was: Re: [Minutes] 29 July TAG teleconf (httpRange-14, URIEquivalence-15)]

TB16 Re: Comments on arch doc draft

Thoughts on "what does an HTTP URI identify?"

Two requests regarding TB16- was: naming and neccessity

Updated finding: Consistency of Formatting Property Names, Values, and Semantics

URIEquivalence-15 (was: Re: [Minutes] 22 July TAG teleconf)

URIEquivalence-15 and IRIs

URIs: resources and contradictions was: Re: httpRange proposed text

using http URIs to name IETF protocol elements [was: TB16]

Using Qualified Names (QNames) as Identifiers in Content

XLINK, HLINK or neither? Possible new TAG issue

xlink:href

Last message date: Wednesday, 31 July 2002 21:04:17 UTC