When is a jurisdiction tag required in a question?

Question

The help page says:

If you are looking for the law in a particular area, please tag your question with the appropriate jurisdiction tag (e.g. united-states, texas, new-york-city, england-and-wales). Even if you supply a jurisdiction tag, we expect and encourage answers dealing with other jurisdictions – while it might not answer your question directly, your question will be here for others who may be from those jurisdictions. If you do this, please tag your answer using the tag markdown: [tag: some-tag].

This suggests that if you are not looking for the law in a particular area, there is no need for a jurisdiction tag.

Quite a while ago, not knowing about this policy, user Someone created the tag any-jurisdiction, which is somewhat redundant because of this policy. It seems to have been received well by other users, though; it is currently used on 205 questions (124 by the most-frequent user of the tag, 38 from the second-most-frequent user, and 12 from the third-most-frequent user).

Should every question be tagged with either a location-specific jurisdiction tag or any-jurisdiction? Or conversely, is it okay to leave a question untagged when you don't care where an answer comes from?

If the community prefers an explicit any-jurisdiction I'll follow along.

---

^{I ask because I have been told that not specifying "any-jurisdiction" "misleads the community who is trying to help" and that I could "use that loophole to play mind tricks with those who are try to help." I am not sure in what sense I could use it as a "loophole." Without a tag, people would answer my question from a variety of jurisdictions. The only side effect is that I'd be more informed than I would have been otherwise. It doesn't sound like a downside to me or the community to have answers from multiple jurisdictions. I don't mean to pick on or give too much significance to this one critique, but it is a perspective I had not considered and admittedly do not understand.}

Answer 1

The any-jurisdiction tag has been bulk removed and blocked, per the consensus reached on this post.

Answer 2

Follow Stack Rules and say: BEGONE!

It is policy that any jurisdiction is demanded in answers not matching the question jurisdiction.

As such, the any-jurisdiction tag serves no purpose - answers that don't match the jurisdiction need to be tagged anyway, and no jurisdiction means all answers need tags. As a result, the any-jurisdiction tag is a tag-tax and meta-tag. Those should not exist in the first place. As such I propose to delete the tag altogether and declare it an invalid tag.

Answer 3

Suggestion: Require jurisdiction tags on all questions

Creating any-jurisdiction was not really necessary, and if I'd known about the policy when I created it, I wouldn't have. However, now that it is somewhat established and used regularly, I think it is helpful.

New users often don't know that they should indicate a jurisdiction if they care about a particular one; because of this, and especially now that any-jurisdiction exists and is used somewhat often, the lack of a tag is not really equivalent to any-jurisdiction. More often, though not always, it means that the user isn't aware of jurisdiction tags, and does care about a particular jurisdiction but didn't know to tag the question as such.

Because the author's intent is ambiguous without a jurisdiction tag, and the role formerly filled by the deliberate lack of one is now more clearly filled by any-jurisdiction, I believe we should require jurisdiction tags for all questions, and close new questions without them as "needs details or clarity" if it cannot be determined from the question whether the user is interested in one particular jurisdiction.