- From: Craig A. Finseth <fin@finseth.com>
- Date: Wed, 12 May 1999 16:44:29 -0500 (CDT)
- To: gomer@lgerca.com
- CC: www-tv@w3.org
Also, the URIs would not be entirely opaque. For example, a URI referring to a data item in a data carousel being broadcast as part of a data event could ... I'd like to clarify before we all get confused. URIs are opaque to the client in the same sense that they currently are on the WWW: relative forms work and the client can construct URIs, but by and large they are simply strings. What Gomer discussed is an important part of making the design efficient, but not relevant for a basic understanding. One of the optimizations that we designed in is to take advantage of the existing mapping information so as to cut down (substantially) on the amount of additional information to be sent. Many documents relevant to btv: can be found at: http://www.finseth.com/~fin/uri Craig
Received on Wednesday, 12 May 1999 17:44:36 UTC