# We've blacklisted [engine], should we do the same for the other similar tags?

This is a follow up of a previous question about doing something with the tags API and SDK, which made me realize they were not alone, and that they might be useless.

It is also a follow up of this question asking about the usage of the engine tag, where the conclusion was that the tag was not needed as it was a meta-tag.

Should we do the same for the following engine-like tags, where the descriptions are ok but, don't contain tag usage?

Is there a case where one of these could not be tagged with their specific API/Framework/Library/SDK, or with , or with , or with another more specific tag?

If you feel a tag should be added to this list, please add them, or leave a comment.

• I've removed all of the uses of "sdk" and put it on the blacklist. – Josh Jun 23 '17 at 18:45
• Same for 'framework'. – Vaillancourt Jun 24 '17 at 2:27

## 1 Answer

I am of the opinion that these tags should be blacklisted.

• You would not be able to use the tags by themselves to adequately tag a question, unless the question was only specific to general context. Such context would probably be to broad for our scope.
• To more accurately use the tags, you would have to also use the more specific tag to provide context, in which case these tags are only being used as meta tags. On brief review, this appears to be the current most recent usage of these tags.
• I could argue with this by saying, that you can use them by themselves when you want to make your own engine/framework/library, but that doesn't add anything to the questiom and thus they're still pointless. – Bálint May 24 '17 at 5:24
• @Bálint, that was my reasoning behind use of the engine tag. It was pointed out that such questions are also too broad for our scope, by nature. – Gnemlock May 24 '17 at 5:46