<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV>i would think making sure there's an 'N/A' option for these taxonomy selectors would be a reasonable workaround for that. sure the UI might be a bit clunkier, but certainly tolerable -- and we'd have a nice feature enhancement.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>why not take it one step at a time and put that in? then we can refine it in step two later w/ form_alter or js hiding or something like that.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>chad</DIV><BR><DIV><DIV>On Mar 25, 2007, at 4:56 AM, dww wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="4" style="font: 14.0px Helvetica">a simple taxonomy would do (sort of).<SPAN class="Apple-converted-space"> </SPAN>however, i've run into the same problem with the "DB support" (mysql vs. pgsql vs. xxx) taxonomy term i want to apply to release nodes and/or project nodes: the DB support only makes sense for certain kinds of projects (modules), not others (themes [god help us if there's mysql-specific code in some theme], translations, etc).<SPAN class="Apple-converted-space"> </SPAN>likewise, the "php version" vocabulary would be meaningless (and confusing) for translations at least, and probably themes as well.</FONT></P> </BLOCKQUOTE></DIV><BR></BODY></HTML>