- From: Craig A. Finseth <fin@finseth.com>
- Date: Mon, 23 Nov 1998 10:14:09 -0600 (CST)
- To: tenkate@natlab.research.philips.com
- Cc: rob@mtvmail.com, www-tv@w3.org, e-e@toocan.philabs.research.philips.com
...
Triggered by your comment I changed the fourth requirement.
I hope that reflects your needs.
o Given a URI, it must be possible for a receiver to determine
the time period(s) within which the resource can be retrieved
from the (also resolved) location. The accuracy of the time
period should correspond with the event's granularity as
provided by the service signaling system.
[Note: the time period in which the resource is valid/meaningful
is controlled by the lifecycle of the application calling the
resource. That application also controls the synchronization
of the time period in which the resource is presented. The URI
indicates the time period within which the resource is available.]
Warner ten Kate.
Do you envision that this requirement could be met by the trivial
implementation of having the open() call fail when the resource is not
available?
(This implementation would correspond to the traditional Internet
implementation: "http://foo.bar.com/xxx" can only be opened when the
site and files are available.)
Craig
Received on Monday, 23 November 1998 11:14:11 UTC