Could we make tags imply other tags?
I am going to define the problem by providing a quick example: Let's say I am developing a
Rails application (
v 3.2.1) and have a problem. So, naturally after almost giving up on Google, I began to post the question on
StackOverflow. The problem comes when I am choosing the tags - The following all accurately define my application environment to some degree of precision:
ruby-on-rails : More than 70k questions (77 asked today)
ruby-on-rails-3 : More than 25k questions (36 asked today)
ruby-on-rails-3.2 : Around 370 questions (7 asked today)
ruby-on-rails-3.2.1 : Around 55 questions (8 asked this month)
Ideally, I should choose just ruby-on-rails-3.2.1, but a quick glance at the number of questions asked with that tag (recently) makes me act otherwise. While, I understand that ruby-on-rails is meant to signify
Rails 1.0, I doubt many people are still on that version. Looking at some recent rails questions confirms this belief as it seems that most people include two-three tags related to the question such as: ruby-on-rails; ruby-on-rails-3 ... (and so on).
There is usually no way for them to include all the four above tags without adequately defining the problem they have in tags - and thus often leave out ruby-on-rails-3.2.1 (the most precise tag).
The solution I propose is
tag-subsets - such that choosing ruby-on-rails-3.2.1 would automatically select the other three tags (and they don't count towards the five-tag limit). Note, that these are different from
For the sake of a discussion - there is another solution I thought of (although I like the idea of
- Rename tags so they precisely include the version number. So, for instance ruby-on-rails be renamed to ruby-on-rails-1.0 ; ruby-on-rails-3 be renamed to ruby-on-rails-3.0 and so on. This would force users to choose the right tag (there is only one "right" tag ever).
The major problem I see with this is the issue of backward compatibility. As mentioned earlier, there are a lot of questions with the ruby-on-rails-3 tag that don't really pertain to
The other concern with forcing version numbers is that only few of the questions are actually version specific and if someone wants to ask a generic
Rails related question, then, having to choose the version number may not be the best idea.