RE: Don't put descriptive info in a URI, only identifying info

From: Larry Masinter (masinter@parc.xerox.com)
Date: Mon, Dec 21 1998


From: "Larry Masinter" <masinter@parc.xerox.com>
To: "Warner ten Kate" <tenkate@natlab.research.philips.com>
Cc: <www-tv@w3.org>
Date: Mon, 21 Dec 1998 14:28:09 PST
Message-ID: <001b01be2d31$2fd22060$aa66010d@copper.parc.xerox.com>
Subject: RE: Don't put descriptive info in a URI, only identifying info

Re "http://www.w3.org/TV/TVWeb/TVWeb-URI-Requirements-19981126.html"

(Minor note: RFC 2119 isn't really appropriate for use
in a requirements document; the MUST/MAY/SHOULD levels
apply to implementation compliance with a protocol
specification, not specification compliance with
protocol goals.)

You identify a TV broadcast content model 
(service, event, component, and fragment) but haven't
justified the need for a URL scheme to span them all.

TV channels and TV programs are different kinds of resources,
and might need entirely different schemes, since they have
very different kinds of access methods and specifications.

The TVWeb-URI-Requirements seem to be written presuming that
there's only one URL scheme.

Larry
-- 
http://www.parc.xerox.com/masinter