I very much support the idea of creating a mechanism to link into tags and node names directly. It seems this is coming up from a couple of places. One of the difficuluties is that you really need a mapping from http://www.drupal.org/node/12342 to http://www.drupal.org/taxonomy/horses (Or http://www.drupal.org/taxonomy/MyHorse) Is there a way to make this mapping automatic? so that users never see http://www.drupal.org/node/12342 unless intended? Julian Bond <julian_bond@voidstar.com> writes: % Moshe Weitzman <weitzman@tejasa.com> Wed, 23 Mar 2005 10:11:00 % >can we not keep on supporting the existing, non ambigous urls. these % >urls are great, but not appropriate for certain links. also, some % >people insist on localizing their links which is insanity but there you % >go ... % % I'm not sure what to say here. The whole REST world is moving towards % meaningful URLs, and they have a big advantage in that a 3rd party % system can create them speculatively, so as long as I know the scheme I % can construct % http://www.drupal.org/taxonomy/vterm/tags/photo without knowing if % "photo" is used or not. The other factor is that Technorati tags uses % the final directory (/photo) to scrape the tag information out. With % every folksonomy scheme doing the same thing so that they can be % compatible with technorati. Similarly with things like Wikipedia. eg % http://en.wikipedia.org/wiki/Category:Horses % % I don't want to break the existing Drupal scheme. But I do want to use a % text based URL scheme as well. This was one of the reasons why I started % building this entirely in contrib and adding extra links to the node so % that folksonomy was entirely separate from taxonomy both in the code and % in the UI. % % -- % Julian Bond Email&MSM: julian.bond at voidstar.com % Webmaster: http://www.ecademy.com/ % Personal WebLog: http://www.voidstar.com/ % M: +44 (0)77 5907 2173 T: +44 (0)192 0412 433 % S: callto://julian.bond/ ----- John Sechrest . Helping people use . computers and the Internet . more effectively . . Internet: sechrest@peak.org . . http://www.peak.org/~sechrest