Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Last days I've noticed a few posts of users on Asp.Net Web Api that has a specific tag but that were tagged by the users by (what I call) 'low-level supertags'


My first instinct would be to replace the low-level tag with the more specific .

But on second thought I believe some people might be looking/following at the more low-level tags so I think that just adding the specific tag is viable too..

What's the general rule on this?

share|improve this question

closed as off-topic by Martijn Pieters, Emrakul, random, Shadow Wizard, Al E. Jul 11 '14 at 0:59

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question pertains only to a specific site in the Stack Exchange Network. Questions on Meta Stack Exchange should pertain to our network or software that drives it as a whole, within the guidelines defined in the help center. You should ask this question on the meta site where your concern originated." – Martijn Pieters, Emrakul, random, Shadow Wizard, Al E.
If this question can be reworded to fit the rules in the help center, please edit the question.

You're right when you would replace with since it seems that web-api is a very basic tag. It doesn't add any great value to the question because I find it too wide, too generic.

When looking at related tags of :

It seems that most people use it in addition to* tag.

I think we could retag all questions (for example):


Job done.

I don't know what should be done with:

share|improve this answer
+1 - good taxonomy. The proposed retagging makes sense to me (as an ASP.Net/MVC/Web API enthusiast). – Tim Medora Apr 4 '13 at 9:51

I once discussed this in another question. I repeat it here:

I disagree that there should be no "compound tags" in any circumstances. While I agree that the specific example and shouldn't be allowed, it's only because neither the individual tags nor the combination are acceptable for Stack Overflow. Where one or both of the tags can stand alone, however, a compound tag may be appropriate. Here are some examples:

Note that especially in the second example, two tags can combine to form a new concept. In the case of , the compound tag is useful to clarify the topic, since the tag can hardly stand alone.

In this case, just like "android-activity", I think it's appropriate to combine the two tags into "", since "web-api", unlike "", can hardly stand alone.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged .