- From: Paul Libbrecht <paul@activemath.org>
- Date: Thu, 26 Jul 2007 17:50:39 +0200
- To: "T.V Raman" <raman@google.com>
- Cc: alanruttenberg@gmail.com, www-tag@w3.org
- Message-Id: <42FABD1E-F20C-4EA1-9C07-4A06B005B77D@activemath.org>
I believe it isn't that horrible... except for the fact that, to non- browsers, http://www.cnn.com/video/ appears as a single resource. I think this is the (very) criticizable part. I have done recently a more constrained example where the internal part was used to jump inside the video. The whole day's workshop is here: http://www.openmath.org/meetings/linz2007/movies/day-1.html and you can jump right on a speaker. I see no other methods, except duplicate the page or split the video, to actually reference a jump to the right speaker except with the hash as in: http://www.openmath.org/meetings/linz2007/movies/day-1.html#Klaus As long as one accepts the idea that this is a single resource (the "whole recordings") it is good style. paul Le 26 juil. 07 à 17:16, T.V Raman a écrit : > > > Exactly, which is why I asked the question --- how does one > interpret the '#'? > > As you point out, the value after the '#' is not an idref into > the document; rather one way to interpret that '#' is as the > client-side equivalent of the server-side '?' in the URL, i.e. > > http://example.com/foo/?a=1 > a=1 is a server param > > http://example.com/foo#a=1 > > a is a client-side param > > But it's a bit mor eindirect than that. > > > Things to take away: > > The CNN example is an interesting case of include processing --- > ie the #foobar in the URL refers to some portion of the document > that materializes after all scripts have run. > > More interestingly, it's not simple include processing at the > level of jumping to an idref after all > scripts have been processed; rather it's jumping off to another > server. > > So this is why I asked the TAG question: > > What does '#' mean in that CNN URL. > > > > Alan Ruttenberg writes: >> A GET of http://www.cnn.com/video/ is done and the client >> "application" is responsible for interpreting and processing the >> fragment identifier (/video/living/2007/07/06/ >> cnn.heroes.scott.southworth.two.cnn) . Typically one would expect >> that if this is html and the client is the browser then the fragid is >> an anchor, but in this case it appears that a script that gets run >> when that page is loaded picks up the rest of the stuff past the "#" >> and arranges for another request in which the full path is passed as >> a query parameter, that parameter being used by a different server to >> retrieve the video in question. >> >> -Alan >> >> http://en.wikipedia.org/wiki/Fragment_identifier >> >> On Jul 26, 2007, at 10:31 AM, T. V. Raman wrote: >> >>> >>> So I see URLs like the following on the CNN page: >>> http://www.cnn.com/video/#/video/living/2007/07/06/ >>> cnn.heroes.scott.southworth.two.cnn >>> >>> So what does the '#' in that URL mean? >>> >>> -- >>> > > -- > Best Regards, > --raman > > Title: Research Scientist > Email: raman@google.com > WWW: http://emacspeak.sf.net/raman/ > Google: tv+raman > GTalk: raman@google.com, tv.raman.tv@gmail.com > PGP: http://emacspeak.sf.net/raman/raman-almaden.asc > >
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Thursday, 26 July 2007 15:51:12 UTC