RE: Naming things with hashes (not #, but e.g. md5)

httpRange-14 is about trying to give a meaning to URIs other than the meaning that derives naturally from the interpretation of the URI in an a@href. Thus, I think httpRange-14 is based on a presumption that is false.

The "ni:" scheme is about naming content which is static. If the content changes then the hash changes, and so the name no longer applies.

Meaning and persistence are intimately tied together: if you ask for a name to be "persistent", what you're asking to persist is its meaning. If you ask what a name "means", you're asking about what of its mapping to meaning you want to persist.

Anyway: you can't name "things" with hashes, you can only name static content. 

Larry
--
http://larry.masinter.net


-----Original Message-----
From: Kingsley Idehen [mailto:kidehen@openlinksw.com] 
Sent: Tuesday, April 10, 2012 9:52 PM
To: www-tag@w3.org
Subject: Re: Naming things with hashes (not #, but e.g. md5)

On 4/10/12 10:39 AM, Yves Lafon wrote:
> On Fri, 6 Apr 2012, Henry S. Thompson wrote:
>
>> Relevant to the httpRange-14 discussion, maybe:
>>
>>  http://www.ietf.org/id/draft-farrell-decade-ni-02.txt
>
> Note that it's related to content-centric networking that was cited by 
> Jim Gettys in his bufferbloat talk (and here: [1], ref to CCnx [2])
>
> [1] http://lists.w3.org/Archives/Public/www-tag/2011Sep/0055.html
> [2] http://www.ccnx.org/
>
Yes, very relevant. Anyway, here are time segment based URLs from Van's 
Google TechTalk presentation on the same subject:

1. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=1048s 
-- Communications vs Data Networking

2. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=1242s 
-- Doing it differently with same infrastructure

3. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=2320s 
-- Named Chunks of Data (Data Objects style of Resources)

4. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=2407s 
-- Data Abstraction is what matters not the underlying Network

5. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=2570s 
-- Focusing on the Data by Name

6. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=2657s 
-- Security the Data using Crytpo .

7. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=2662s 
-- Trusting Data via Data i.e., using Crytpo and Trust Logic .

8. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=2685s 
-- Data Dissemination (Data Diffusion) Example that includes 
Vectorization via indirection in response to Data by Generic Name Requests.

9. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=2949s 
-- Data Items have Names as opposed to Addresses

10. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=3003s 
-- Integrity and Trust are Data Properties .

11. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=3081s 
-- Artificial Tensions about Networking (Bit Shifting).

12. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=3178s 
-- Communication Wins from Good Data Dissemination Architecture .

13. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=3640s 
-- Data Integrity and Broken Hierarchical CA Network.

14. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=3722s 
-- Change has to be Unobtrusive (back to why 200 OK for Locations is a 
nice heuristic when disambiguating HTTP URI Names).

15. 
http://www.youtube.com/watch?feature=player_detailpage&v=gqGEMQveoqg#t=3874s 
- What exactly is a Name?

-- 

Regards,

Kingsley Idehen	
Founder&  CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen

Received on Tuesday, 10 April 2012 21:20:21 UTC