RE: IETF tree URL registration procedure incomplete

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Larry-

Your points are well-taken.   But...

Where it *does* work is when the page with the tv: reference in it 
will be broadcast and not available on a globally accessible web 
server.  It thus implicitly contains the context of the channel on 
which it is broadcast, which is a local context to the receiver.  So, 
when watching the Disney channel, Disney will be able to put "tv:abc" 
in one of the broadcast web pages, and the tune event that that URI 
permits will in fact do the "right" thing.  It is in fact good that 
it is somewhat non-specific (and perhaps thus not a URL).  In 
contrast, they can't put in tv:7 at the studio, since it would surely 
do the wrong thing more than 50% of the time, since ABC is not always 
on channel 7.

We've had this discussion before, and I'm not sure Dan and Mark would 
agree with me, but in my view, for network feeds it is a URN.  The 
resolution to a specific transport and channel occurs within the 
receiver.  "abc" is translated locally to a transport (DIRECTV or 
NTSC for example) and channel to the best (or possibly multiple) ABC 
network feeds which is OK.  The receiver knows how to do this.

Disney feeds sent to Australia would not contain "tv:abc" (unless of 
course they meant to get the Australian Broadcasting Company).

And, within intranets, or any locally scoped network where the TV 
space is well known, you can in fact put "click here tv:7 to see the 
president's speech" and it too will do the right thing.

So, we'll try to document all these better, which is I think your 
main point.

	Mike

But yep, you put tv:7 on a global web server

At 05:01 PM 8/25/99 PDT, Larry Masinter wrote:
>
>In the case of 'tv:abc' in any kind of Internet content, the
>sender has no way of knowing anything about the receiver's mapping
>of network identifiers to channels. In this case (unlike all of
>the other cases), it's likely that those with the most content
>(US content providers) will provide links which *they* intend
>to refer to mainly US network identifiers. The result will be
>that most TV URLs that are authored with a station identifier will
>use 'tv:abc' to refer to the American Broadcasting Company, and
>those who have a mapping to the Australian Broadcast Corporation
>will just be out of luck. The Australian receiver's will wind up
>adapting (after all, they wanted to watch "Dallas", too, if that's
>what the link *meant*), and the result will be that 'tv:abc' will
>evolve to mean the primary meaning.
>
>I don't think that draft-ietf-urlreg-guide-05.txt currently
>does a good job of layout out this guideline, and I propose
>adding some text to it to capture some requirement for
>'uniform interpretation': does the URL designate the same
>'resource' no matter where and who is interpreting it. We
>might want to acknowledge that some schemes don't do this,
>and they suffer because of it.
>
>Larry
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBN8SPFSl9dIG/haQGEQLsWwCg+fqVecXCDztMHTixxAAmgiK0JwQAn0Mo
ydNmjEVC5Q58nTzGlX2px1Qi
=zdND
-----END PGP SIGNATURE-----

------------------------------------------------------
Michael A. Dolan, Representing DIRECTV,  (619)445-9070   
PO Box 1673 Alpine, CA 91903        FAX: (619)445-6122