closed as off-topic by Undo, Martijn Pieters, Shadow Wizard, 3ventic, random May 13 '14 at 19: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." – Undo, Martijn Pieters, Shadow Wizard, 3ventic, random
The fact that a question has the ambiguity tag doesn't tell anyone anything. And since you can't possibly be an expert at ambiguous questions, nobody is going to follow that tag (well, except one). It should be removed.
Or, if there is a particular use case in which the tag will make sense (e.g. in AI techniques), then the tag wiki should reflect that very clearly and all questions that are not about that topic should have their tag removed.
At first it seems ambiguity is itself an ambiguous tag.
It seems like tagging something with confusing.
But actually it's not like that. Ambiguity is, dictionary: "uncertainty or inexactness" -- in code ambiguity is the name of a specific problem where things are inexact or imprecise. The ambiguity tag is all about this problem.
That said, it isn't that useful a tag, imo
I think burnination is overkill in this situation. ambiguity could be used as a meta tag, but I don't think it always is used that way in practice. Seems to me that it would be valid on a question like
I need to implement a solution for the ISO-2410593813513 spec, which says that all bars must be fooed when baz is not null. I'm running into cases where baz is null, and the spec doesn't address that. What do I do now?
In other words, it's a meta tag if you use it to mean "this question is ambiguous," but it's okay if you're asking about ambiguity elsewhere.
If you want to make the claim that people are using the tag improperly, then okay, but burnination isn't the solution to that problem.
Can't think of any case where there's not a better tag.
In the case of understanding specifications.
In the case of method declarations.
In the case of code being ambiguous, no tag is necessary, there should already be existing tags.
So, I can't find a case where another tag would make the
Ambiguity tag less Ambiguous (lololol).
I think this is a case of people wanting to add search terms to the question to pick up more hits, when tags are really meant for categorization, not searching. The difference being that search terms could get way more precise than categorizations, to the point that they're not useful for the purpose of following the tag. It's better to put these things into the title instead.
Even so, I can't think of someone including "Ambiguity" in their search.