<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>From the rel-tag spec (<a href="http://microformats.org/wiki/rel-tag">http://microformats.org/wiki/rel-tag
</a>):<br><br>"Tags are embedded in HTTP URIs in a well-defined manner so that the tag<br>embedded in an HTTP URI can be mechanically extracted from that URI.<br>Specifically, the last segment of the path portion of the URI (after the
<br>final "/" character) contains the tag value."<br><br>In the world of Microformats there is only one url segment after the /<br>which properly encodes a tag/category/keyword/term/etc; adding a<br>textfield to control that wouldn't be too useful since there is only one
<br>option for compliance with this spec.<br><br>I would like to see core have this without the addition of any UI,<br>probably using the approach laid out in <a href="http://drupal.org/node/63635">http://drupal.org/node/63635
</a> for<br>nodes on the code side. The URLs can be '.../{vocabulary}(/{parent<br>category})*/{category}'.<br><br>And since we are coding Drupal here, might as well throw in an API for a<br>pathauto-like module to go and change everything up. A module could Form
<br>API in a text field for manual editing if someone wants that.<br><br>(A system to manage redirects would be nice so URLs get redirects as<br>they are changed.)<br><br>--<br>Neil Drumm<br><a href="http://delocalizedham.com/">
http://delocalizedham.com/</a><br><br></blockquote></div>
<div> </div>
<div>In the beginning of 2006 I have started to develop module called friendly_url. Its features are:</div>
<div>* Extends custom_url_rewrite functionality.</div>
<div>* Friendly user URLs: user/1.* --> user/root.* (e.g. user/1/edit --> user/root/edit).<br> root - was the name of user. If friendly_url module is enabled then users can't register with login names that will be encoded in URL.
</div>
<div>* Nodes URLs: When user adds new node he can specify a friendly URL - which can't be number or some of the forbidden names (forbidden URLs are fetched using hook_url_rewrite_forbidden().)</div>
<div>* Taxonomy URLs: same as nodes.</div>
<div>* Taxonomy_menu URLs.</div>
<div>* Friendly URL caching.</div>
<div> </div>
<div>Taxonomy_menu provides special rewrite from taxonomy/term/* to hierarchical taxonomy_menu/<voc_name>/<term_friendly_url>/<term_friendly_url>. Also taxonomy_menu/<voc_name>/<term_name>/<term_name>/depth/0 etc. was implemented for feeds.
</div>
<div>Also, taxonomy_menu can be striped from the URL.</div>
<div>e.g. I have a taxonomy_menu/articles/artificial-intelligence/neural-networks. ---> articles/artificial-intelligence/neural-networks.</div>
<div>(where articles is the friendly url of vocabulary.)</div>
<div> </div>
<div>Maybe this ways can be helpful for developing a hierarchical taxonomy URLs.</div>
<div> </div>
<div>sincerely,</div>
<div>doq doques.</div>