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

From: Craig A. Finseth (fin@finseth.com)
Date: Mon, Dec 21 1998


Date: Mon, 21 Dec 1998 14:26:08 -0600 (CST)
Message-Id: <199812212026.OAA27998@isis.visi.com>
From: "Craig A. Finseth" <fin@finseth.com>
To: miked@tbt.com
Cc: gomer@lgerca.com, connolly@w3.org, ietf-url@imc.org, www-tv@w3.org
Subject: Re: Don't put descriptive info in a URI, only identifying info

	...
   >I believe that in most, if not all cases, the time dimension will be
   >specified by identifying the "event" (TV program, in ordinary
   >terminology), with perhaps in some cases an offset relative to the start
   >of the event, rather than by explicitly specifying a clock time.

   This is one way to do it that is more object-oriented and fits the object
   model much better.  However, there is not agreement on the list that this
   is the (only) possible or useful solution.  There are other possible URI
   designs that do not directly reference an EPG object, and thus might need
   absolute (GMT) time.

Umm, you just proved the opposite of your point.

We all agree (I believe) that there is a requirement to designate
time-related content on a channel (e.g., an event).

The open question is whether that requirement may _only_ be met
by putting time-related information in the URI itself.

You agree that there are valid schemes that meet the requirement
without such encoding.  That indicates that the encoding is not itself
part of the requirement.  (The fact that one can devise schemes that use
the encoding is not relevant to the question.)

Craig