Click Here

Today I spent: 45 minutes in morning rush hour traffic, wishing painful butt ulcers on every driver who cut me off/nearly killed us both/yakked on the cell phone 30 minutes in an overcrowded cafe trying to juggle 1) eating giant burrito, 2) reading Terry Pratchett novel and 3)dodging 9-5 Dilberts at the soda fountain 30 minutes returning urgent yet completely not voicemails 15 minutes peeing (why was I cursed with the Barbie Bladder?) 7 hours enduring annual training on the titilating aspects of the National School Lunch & Breakfast Program 60 minutes in evening rush hour traffic, several of which were spent nearly impaling car on poorly placed lane divider poles and recovering after near heart attack Tomorrow promises lake tahoe hotel deal o be just as soul-crushing/educational. (sigh)

joyfully unusual dice

My last two posts were motivated by Sean McGrath’s piece on URLs and the social contracts they imply. So, too, this one. Sean argues for the network-value of a naming convention for URLs, namely, the inclusion in URLs-of-permanent-intent of the string ‘purl’. When I first read his post, my egocentrism led me to think he was alluding to the PURL system, launched by OCLC a dozen years ago in response to our frustrations with the ground-hog-day character of the URN meetings in the IETF . We launched PURLs with an expectation that they would be widely adopted and deployed by all right-thinking Web managers (we had a LOT of silly ideas like that…). PURLs have never been as widely deployed as were our hopes, delay generator ut they are still alive and growing, and remain both useful and an instructive data point in the evolution of the Internet naming architecture. One reason I was so ready to conclude that Sean was talking about PURLS is his argument: I am thinking of nothing more complicated than a social naming convention. What if permanent URLs contained the fragment '/purl/' for example? Would that not do the trick? As a consumer, I look at example.com/purl/info12.html and can immediately infer that it is a good candidate for bookmarking. From a URL consumer's perspective, this would be very handy I think. From a URL producer's perspective, it would also be very handy. In effect, it would allow URL producers to send out signals to the world.

robber parental responsibility

My last two posts were motivated by Sean McGrath’s piece on URLs and the social contracts they imply. So, too, this one. Sean argues for the network-value of a naming convention for URLs, namely, the inclusion in URLs-of-permanent-intent of the string ‘purl’. When I first read his post, my egocentrism led me to think he was alluding to the PURL system, launched by OCLC a dozen years ago in response to our frustrations with the ground-hog-day character of the URN meetings in the IETF . We launched PURLs with an expectation that they would be widely adopted and deployed by all right-thinking Web managers (we had a LOT of silly ideas like that…). PURLs have never been as widely deployed as were our hopes, but they are still alive and growing, and remain both useful and an instructive data point in the evolution of the Internet naming architecture. One reason I was so ready to conclude that Sean was talking about PURLS is his argument: I am thinking of nothing more complicated than a social naming convention. What if permanent URLs contained the fragment '/purl/' for example? Would that not do the trick? As a consumer, visual password look at example.com/purl/info12.html and can immediately infer that it is a good candidate for bookmarking. From a URL consumer's perspective, this would be very handy I think. From a URL producer's perspective, it would also be very handy. In effect, it would allow URL producers to send out signals to the world.

My last two posts were motivated by Sean McGrath’s piece on URLs and the social contracts they imply. So, too, this one. Sean argues for the network-value of a naming convention for URLs, namely, the inclusion in URLs-of-permanent-intent of the string ‘purl’. When I first read his post, my egocentrism led me to think he was alluding to the PURL windows media player plugins ystem, launched by OCLC a dozen years ago in response to our frustrations with the ground-hog-day character of the URN meetings in the IETF . We launched PURLs with an expectation that they would be widely adopted and deployed by all right-thinking Web managers (we had a LOT of silly ideas like that…). PURLs have never been as widely deployed as were our hopes, but they are still alive and growing, and remain both useful and an instructive data point in the evolution of the Internet naming architecture. One reason I was so ready to conclude that Sean was talking about PURLS is his argument: I am thinking of nothing more complicated than a social naming convention. What if permanent URLs contained the fragment '/purl/' for example? Would that not do the trick? As a consumer, I look at example.com/purl/info12.html and can immediately infer that it is a good candidate for bookmarking. From a URL consumer's perspective, this would be very handy I think. From a URL producer's perspective, it would also be very handy. In effect, it would allow URL producers to send out signals to the world.

My last two posts were motivated by Sean McGrath’s piece on URLs and the social contracts they imply. So, too, this one. Sean argues for the network-value of a naming convention for URLs, namely, the inclusion in URLs-of-permanent-intent of the string ‘purl’. When I first read his post, my egocentrism led me to think he was alluding to the PURL system, launched by OCLC a dozen years ago in response to our frustrations with the ground-hog-day character of the URN meetings in the IETF . We launched PURLs with an expectation that they would be widely adopted and deployed by all right-thinking Web managers (we had a LOT of silly ideas like that…). PURLs have never been as widely deployed as were our hopes, but they are still alive and growing, and remain both useful and an instructive data point in the evolution of the Quick response nternet naming architecture. One reason I was so ready to conclude that Sean was talking about PURLS is his argument: I am thinking of nothing more complicated than a social naming convention. What if permanent URLs contained the fragment '/purl/' for example? Would that not do the trick? As a consumer, I look at example.com/purl/info12.html and can immediately infer that it is a good candidate for bookmarking. From a URL consumer's perspective, this would be very handy I think. From a URL producer's perspective, it would also be very handy. In effect, it would allow URL producers to send out signals to the world.

joyfully Tweak UI