Comments on: Latent OpenURLs in HTML http://www.wallandbinkley.com/quaedam/?p=19 Morning postings from Route 66 Tue, 27 Jul 2010 15:02:44 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Quædam cuiusdam » Blog Archive » OpenURLs in Wordpress http://www.wallandbinkley.com/quaedam/?p=19&cpage=1#comment-79 Quædam cuiusdam » Blog Archive » OpenURLs in Wordpress Mon, 06 Jun 2005 16:06:07 +0000 http://www.wallandbinkley.com/quaedam/?p=19#comment-79 [...] laquo; Ajax and Autocompletion OpenURLs in Wordpress Eric left a note about the problem I had incorporating a latent OpenURL into a Wordpress comment. In a f [...] [...] laquo; Ajax and Autocompletion OpenURLs in WordPress Eric left a note about the problem I had incorporating a latent OpenURL into a WordPress comment. In a f [...]

]]> By: eric http://www.wallandbinkley.com/quaedam/?p=19&cpage=1#comment-77 eric Sat, 04 Jun 2005 18:43:11 +0000 http://www.wallandbinkley.com/quaedam/?p=19#comment-77 I think that if you can't implement the openurl "rel" attribute in wordPress, that's a problem! I think that if you can’t implement the openurl “rel” attribute in wordPress, that’s a problem!

]]> By: Peter http://www.wallandbinkley.com/quaedam/?p=19&cpage=1#comment-36 Peter Thu, 07 Apr 2005 16:39:26 +0000 http://www.wallandbinkley.com/quaedam/?p=19#comment-36 Thanks, Ross, clearly I've fallen way behind on this stuff. I see that I missed an important feature of Openly's proposal, that the anchor should be empty and therefore invisible until it is activated by the external service. And I tried putting a discoverable OpenURL in this comment, but WordPress replaced the <code>rel</code> attribute with "nofollow", so it didn't work. One other implication of this is that sid's are going to proliferate in all kinds of ways. Any attempt to derive usage stats from our link resolvers will be affected. Thanks, Ross, clearly I’ve fallen way behind on this stuff. I see that I missed an important feature of Openly’s proposal, that the anchor should be empty and therefore invisible until it is activated by the external service. And I tried putting a discoverable OpenURL in this comment, but WordPress replaced the rel attribute with “nofollow”, so it didn’t work.

One other implication of this is that sid’s are going to proliferate in all kinds of ways. Any attempt to derive usage stats from our link resolvers will be affected.

]]> By: Ross http://www.wallandbinkley.com/quaedam/?p=19&cpage=1#comment-35 Ross Thu, 07 Apr 2005 13:40:16 +0000 http://www.wallandbinkley.com/quaedam/?p=19#comment-35 Actually, the idea of a div or a span (per Dan and Jeremy's original article) was given up a while ago in favor of using empty anchors. <a href="http://curtis.med.yale.edu/dchud/resolvable/" rel="nofollow">http://curtis.med.yale.edu/dchud/resolvable/</a> explores the ideas a little more realistically than in their original paper (a revised paper, based on this work, will come out in the Spring issue of <a href="http://www.ariadne.ac.uk/" rel="nofollow">Ariadne</a>. There's still a difference. The "Appropriate Resolver" page really only addresses OpenURL v. 0.1 urls. The tension between the simplicity of v 0.1 and the versatility of 1.0 is something that really needs to be worked out. You can see some of your ideas in the last paragraph already have some traction. Actually, the idea of a div or a span (per Dan and Jeremy’s original article) was given up a while ago in favor of using empty anchors.

http://curtis.med.yale.edu/dchud/resolvable/ explores the ideas a little more realistically than in their original paper (a revised paper, based on this work, will come out in the Spring issue of Ariadne. There’s still a difference. The “Appropriate Resolver” page really only addresses OpenURL v. 0.1 urls. The tension between the simplicity of v 0.1 and the versatility of 1.0 is something that really needs to be worked out.

You can see some of your ideas in the last paragraph already have some traction.

]]>