-
Website
http://www.scobleizer.com/ -
Original page
http://scobleizer.com/2005/11/22/a-better-permalink-or-is-that-purplelink/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
danja
44 comments · 4 points
-
polizeros
52 comments · 1 points
-
AndyBeard
69 comments · 4 points
-
Zachary Adam Cohen
35 comments · 8 points
-
dbarefoot
40 comments · 3 points
-
-
Popular Threads
-
The best and worst thing Twitter did in 2009: RT
1 day ago · 22 comments
-
World-brand-building mistakes France’s entrepreneurs make
1 week ago · 181 comments
-
2010: the year SEO isn’t important anymore
1 week ago · 67 comments
-
A new addition here: the Meebo bar
1 day ago · 7 comments
-
iPhone developers abandoning app model for HTML5?
1 week ago · 52 comments
-
The best and worst thing Twitter did in 2009: RT
--bill
But instead of using a sequence number, which breaks (as Scoble notes), I use the time the paragraph was created (which breaks if you create two paragraphs in the same second, hard to do). That way you can add a paragraph in the middle, or even move them around, and the permalinks don't break (I don't bother displaying a number, people don't need that, the machines do, so the number is encoded in the url as a time).
Now that said, I don't bother generating them for sub-paragraphs. I could, but I think that's a bit anal.
I dont't think, a single paragraph is this important. I've never felt the urge to link to a single paragraph.
I mean, every composition by Mozart is referenced by it's Köchel catalogue number. If a simple number per piece is enough for Mozart's art, it sure is sufficient for my lame attempts at writing.
Janek.
http://www.tbray.org/ongoing/When/200x/2004/05/...
Though they boil down to the same idea, I think the granularity of purple is slightly different than Dave's permalinks. Purple numbers appear within (the equivalent of) a single blog/RSS item, whereas the permalinks are per-item. It looks the same in Dave's case because he only has one paragraph per item.
You might also want to check out Annotea, which allows you to mark pieces of a doc with per-character precision (using XPointer).
http://www.tbray.org/ongoing/When/200x/2004/05/...
http://wiki.wordpress.org/?pagename=PurpleNumbers
Plus a title link is more relevant to the actual content of what you are linking to.
BTW, does anybody know about a Movable Type implementation?
XPointer lets us refer to parts of a resource (page) explicitly -- without relying on the page author to have foreseen every permutation of subselection we might want to reference. But XPointer was initially crippled by lack of a practical, implementable (implemented) query language or "scheme".
This situation may be changing quickly since the folks over at the Text Encoding Initiative have defined (and co-opted) a nice simple little composable family of XPointer "schemes" based on simple, off the shelf stuff like XPath and friends: http://tinyurl.com/9lkat With this in place, the referring application reads the target page and applies the query part of the URL through the scheme(s) to arrive at the content.
Everybody always hits on the issue of purple number ugliness. In the earlier implementations that I've been involved with, making the numbers very apparent was important so that people knew they were there and had that moment of discovery. CSS and other tools can help constrain the presentation of the numbers.
In the end the implementation of granular addressability and transclusion isn't really that important: it's getting the concepts into brains so it can be improved and evolve. Small, simple, reusable chunks help build a complex and interesting world.
Actually, it isn't. The "K number" gets you to the desired composition (though there can be multiple versions) but then you may also specify the movement within the piece and even the section of a movement. (For example, 1st theme of in the exposition section of the first movement of symphony #40.)
Fun stuff...
Dan
There are bound to be places were you would want to only reference a single *sentance*, for instance - it would be really amazingly cool if my browser let me highlight part of a text and create a permalink out of it, which if you referenced it, would go to the page, scroll to the right bit of it and highlight the section. It's overheating my brain a little trying to think through the implementation of that(!) - but I don't think these purple numbers are it. It's got me thinking though... :)
I like your idea for a browser imlpementation, as it does remove the ghastly links. But also, more importantly, it removes the writer from the misguided belief that every paragraph they write is worth bookmarking.
@Will
Using a title also makes sense - if you believe the paragraph is worth linking to direct, then it's probably worth having its own heading.
Here's a friendlier implementation: The publishing software can automatically create permalinks for each paragraph, but doesn't display them until you click on a link at the end of the post.
Such a tool exists (JavaScript+DOM-based). It's called Ahoy and works in every Mozilla-based browser, including Firefox, but requires the site/page owner to link the ahoy.js file into the page via a SCRIPT element. Just click and select some text with your Alt key pressed.
For example, a direct link to "creating your first Ahoy anchor from a text selection" (there's no 'preview' option for comments here, so hopefully Wordpress won't mangle the url):
http://dev.lophty.com/ahoy/article.htm?ahyAncho...
Here's the plain vanilla link to the article: http://dev.lophty.com/ahoy/article.htm
Ahoy is GPL'd. You can download it and use it on your own sites.
You didn't miss the meme.
That's for the silly LiveJournal/Xanga/etc. kids.
;)
http://webseitz.fluxent.com/wiki/z2003-05-04-Im...
Ahoy is cool in that it enables a _consumer_ of the Web page to link to a particular passage of their choosing, umm, provided the publisher has implemented Ahoy on their web site. I think this would also be the case for the Text Encoding Initiative.
Two years ago I got around this short coming of Ahoy by transcoding the Ahoy script into the target web page on the fly via a web proxy.[1][2]
A year or so prior to that I had written PurpleSlurple[3] to transcode purple numbers into web pages on the fly.
Last year I released QuiP. QuiP reverses the process of creating the granular link, vs PSAhoy, to a more logical sequence, to my mind: Select text to link to, click bookmarklet, optionally add note (something Ahoy doesn't do)[3].
Parlor tricks perhaps, but effective enough for my uses, and _importantly_ tools for the consumer.
[1]PSAhoy post: http://collab.blueoxen.net/forums/yak/2003-11/m...
[2]PSAhoy sample: http://sasites.com/suse/apache/files/psAhoy.php...
[3]PurpleSlurple: http://purpleslurple.net/
[4]QuiP sample: http://sasites.com/quip04.php?url=http://scoble...