Return to Question

By super tagging I mean for example adding tags such as visual-studio to a question tagged visual-studio-2010.

Why this would be desirable:

• it is easier to ignore / follow a single super tag rather than every single new version that comes out.

  I can't stand anymore ignoring visual-studio versions (visual-studio, visual-studio-2010-sp1, ...) or every single library for a language that I don't know like javascript (node.js, angular.js, backbone.js, etc.).

  EDIT as Doorknoob mentioned, one can ignore with asterisks as visual-studio* to ignore all visual-studio tags. This would not however work for example for language vs library as in python vs django.

• Employers who want to measure how much visual-studio you know have to add up all visual-studio-XXX without counting duplicates. That would be hard.

Also the top answer for this question at the time of writing says that sub/super tagging is good.

So how do we ensure that super tagging gets done?

Alternatives I can see so far:

• accept retag edits and give people repo for that.

  Dangerous, because I got 200 rep today by adding visual-studio super tags, so even a bot could give someone 2000 rep in 10 days. This would however ensure that super tagging gets done.

• accept retag edits and don't give people repo for them, or give them little repo. I am not sure this is possible, but probably has been suggested (please link to if you know where).

  Of course, if you don't give people repo, many questions will go without proper supertags.

• suggest somewhere that askers supertag and give examples of valid supertags.

For the three abouve options to work, reviewers or askers would need guidelines to what counts as a good supertag, and any such guideline will have many edge cases and be very hard to decide on.

• automatic supertagging. It seems that this has been vetoed by Jeff on his comment, and might be hard to implement.

Or should we reject all supertagging edits, since all of the above have problems? But then, how do we decide what counts as a supertag and what does not? If we decide everything that is not a supertag, wouldn't that be the same as deciding what is a supertag?

EDIT when I asked this I had in mind for it to be a conditional discussion: if we want to add super and sub tags, how should we do it, and not if we should do it or not (true, the way it was asked was very partial). I suggest the question of should we add both tags be moved to this older question which as far as I understand already discusses that. Thinking about it now, this could even be marked as a dupe, because it we decide that we should do something, then we should also decide how at the same time.

By super tagging I mean for example adding tags such as visual-studio to a question tagged visual-studio-2010.

Why this would be desirable:

• it is easier to ignore / follow a single super tag rather than every single new version that comes out.

  I can't stand anymore ignoring visual-studio versions (visual-studio, visual-studio-2010-sp1, ...) or every single library for a language that I don't know like javascript (node.js, angular.js, backbone.js, etc.).

  EDIT as Doorknoob mentioned, one can ignore with asterisks as visual-studio* to ignore all visual-studio tags. This would not however work for example for language vs library as in python vs django.

• Employers who want to measure how much visual-studio you know have to add up all visual-studio-XXX without counting duplicates. That would be hard.

Also the top answer for this question at the time of writing says that sub/super tagging is good.

So how do we ensure that super tagging gets done?

Alternatives I can see so far:

• accept retag edits and give people repo for that.

  Dangerous, because I got 200 rep today by adding visual-studio super tags, so even a bot could give someone 2000 rep in 10 days. This would however ensure that super tagging gets done.

• accept retag edits and don't give people repo for them, or give them little repo. I am not sure this is possible, but probably has been suggested (please link to if you know where).

  Of course, if you don't give people repo, many questions will go without proper supertags.

• suggest somewhere that askers supertag and give examples of valid supertags.

For the three abouve options to work, reviewers or askers would need guidelines to what counts as a good supertag, and any such guideline will have many edge cases and be very hard to decide on.

• automatic supertagging. It seems that this has been vetoed by Jeff on his comment, and might be hard to implement.

Or should we reject all supertagging edits, since all of the above have problems? But then, how do we decide what counts as a supertag and what does not? If we decide everything that is not a supertag, wouldn't that be the same as deciding what is a supertag?

EDIT when I asked this I had in mind for it to be a conditional discussion: if we want to add super and sub tags, how should we do it, and not if we should do it or not (true, the way it was asked was very partial). I suggest the question of should we add both tags be moved to this older question which as far as I understand already discusses that. Thinking about it now, this could even be marked as a dupe, because it we decide that we should do something, then we should also decide how at the same time.

By super tagging I mean for example adding tags such as visual-studio to a question tagged visual-studio-2010.

Why this would be desirable:

• it is easier to ignore / follow a single super tag rather than every single new version that comes out.

  I can't stand anymore ignoring visual-studio versions (visual-studio, visual-studio-2010-sp1, ...) or every single library for a language that I don't know like javascript (node.js, angular.js, backbone.js, etc.).

  EDIT as Doorknoob mentioned, one can ignore with asterisks as visual-studio* to ignore all visual-studio tags. This would not however work for example for language vs library as in python vs django.

• Employers who want to measure how much visual-studio you know have to add up all visual-studio-XXX without counting duplicates. That would be hard.

Also the top answer for this question at the time of writing says that sub/super tagging is good.

So how do we ensure that super tagging gets done?

Alternatives I can see so far:

• accept retag edits and give people repo for that.

  Dangerous, because I got 200 rep today by adding visual-studio super tags, so even a bot could give someone 2000 rep in 10 days. This would however ensure that super tagging gets done.

• accept retag edits and don't give people repo for them, or give them little repo. I am not sure this is possible, but probably has been suggested (please link to if you know where).

  Of course, if you don't give people repo, many questions will go without proper supertags.

• suggest somewhere that askers supertag and give examples of valid supertags.

For the three abouve options to work, reviewers or askers would need guidelines to what counts as a good supertag, and any such guideline will have many edge cases and be very hard to decide on.

• automatic supertagging. It seems that this has been vetoed by Jeff on his comment, and might be hard to implement.

Or should we reject all supertagging edits, since all of the above have problems? But then, how do we decide what counts as a supertag and what does not? If we decide everything that is not a supertag, wouldn't that be the same as deciding what is a supertag?

EDIT when I asked this I had in mind for it to be a conditional discussion: if we want to add super and sub tags, how should we do it, and not if we should do it or not (true, the way it was asked was very partial). I suggest the question of should we add both tags be moved to this older question which as far as I understand already discusses that. Thinking about it now, this could even be marked as a dupe, because it we decide that we should do something, then we should also decide how at the same time.

By super tagging I mean for example adding tags such as visual-studio to a question tagged visual-studio-2010.

Why this would be desirable:

• it is easier to ignore / follow a single super tag rather than every single new version that comes out.

  I can't stand anymore ignoring visual-studio versions (visual-studio, visual-studio-2010-sp1, ...) or every single library for a language that I don't know like javascript (node.js, angular.js, backbone.js, etc.).

  EDIT as Doorknoob mentioned, one can ignore with asterisks as visual-studio* to ignore all visual-studio tags. This would not however work for example for language vs library as in python vs django.

• Employers who want to measure how much visual-studio you know have to add up all visual-studio-XXX without counting duplicates. That would be hard.

Also the top answer for this question at the time of writing says that sub/super tagging is good.

So how do we ensure that super tagging gets done?

Alternatives I can see so far:

• accept retag edits and give people repo for that.

  Dangerous, because I got 200 rep today by adding visual-studio super tags, so even a bot could give someone 2000 rep in 10 days. This would however ensure that super tagging gets done.

• accept retag edits and don't give people repo for them, or give them little repo. I am not sure this is possible, but probably has been suggested (please link to if you know where).

  Of course, if you don't give people repo, many questions will go without proper supertags.

• suggest somewhere that askers supertag and give examples of valid supertags.

For the three abouve options to work, reviewers or askers would need guidelines to what counts as a good supertag, and any such guideline will have many edge cases and be very hard to decide on.

• automatic supertagging. It seems that this has been vetoed by Jeff on his comment, and might be hard to implement.

Or should we reject all supertagging edits, since all of the above have problems? But then, how do we decide what counts as a supertag and what does not? If we decide everything that is not a supertag, wouldn't that be the same as deciding what is a supertag?

EDIT when I asked this I had in mind for it to be a conditional discussion: if we want to add super and sub tags, how should we do it, and not if we should do it or not (true, the way it was asked was very partial). I suggest the question of should we add both tags be moved to this older question which as far as I understand already discusses that. Thinking about it now, this could even be marked as a dupe, because it we decide that we should do something, then we should also decide how at the same time.

By super tagging I mean for example adding tags such as visual-studio to a question tagged visual-studio-2010.

Why this would be desirable:

• it is easier to ignore / follow a single super tag rather than every single new version that comes out.

  I can't stand anymore ignoring visual-studio versions (visual-studio, visual-studio-2010-sp1, ...) or every single library for a language that I don't know like javascript (node.js, angular.js, backbone.js, etc.).

  EDIT as Doorknoob mentioned, one can ignore with asterisks as visual-studio* to ignore all visual-studio tags. This would not however work for example for language vs library as in python vs django.

• Employers who want to measure how much visual-studio you know have to add up all visual-studio-XXX without counting duplicates. That would be hard.

Also the top answer for this question at the time of writing says that sub/super tagging is good.

So how do we ensure that super tagging gets done?

Alternatives I can see so far:

• accept retag edits and give people repo for that.

  Dangerous, because I got 200 rep today by adding visual-studio super tags, so even a bot could give someone 2000 rep in 10 days. This would however ensure that super tagging gets done.

• accept retag edits and don't give people repo for them, or give them little repo. I am not sure this is possible, but probably has been suggested (please link to if you know where).

  Of course, if you don't give people repo, many questions will go without proper supertags.

• suggest somewhere that askers supertag and give examples of valid supertags.

For the three abouve options to work, reviewers or askers would need guidelines to what counts as a good supertag, and any such guideline will have many edge cases and be very hard to decide on.

• automatic supertagging. It seems that this has been vetoed by Jeff on his comment, and might be hard to implement.

Or should we reject all supertagging edits, since all of the above have problems? But then, how do we decide what counts as a supertag and what does not? If we decide everything that is not a supertag, wouldn't that be the same as deciding what is a supertag?

By super tagging I mean for example adding tags such as visual-studio to a question tagged visual-studio-2010.

Why this would be desirable:

• it is easier to ignore / follow a single super tag rather than every single new version that comes out.

  I can't stand anymore ignoring visual-studio versions (visual-studio, visual-studio-2010-sp1, ...) or every single library for a language that I don't know like javascript (node.js, angular.js, backbone.js, etc.).

  EDIT as Doorknoob mentioned, one can ignore with asterisks as visual-studio* to ignore all visual-studio tags. This would not however work for example for language vs library as in python vs django.

• Employers who want to measure how much visual-studio you know have to add up all visual-studio-XXX without counting duplicates. That would be hard.

Also the top answer for this question at the time of writing says that sub/super tagging is good.

So how do we ensure that super tagging gets done?

Alternatives I can see so far:

• accept retag edits and give people repo for that.

  Dangerous, because I got 200 rep today by adding visual-studio super tags, so even a bot could give someone 2000 rep in 10 days. This would however ensure that super tagging gets done.

• accept retag edits and don't give people repo for them, or give them little repo. I am not sure this is possible, but probably has been suggested (please link to if you know where).

  Of course, if you don't give people repo, many questions will go without proper supertags.

• suggest somewhere that askers supertag and give examples of valid supertags.

For the three abouve options to work, reviewers or askers would need guidelines to what counts as a good supertag, and any such guideline will have many edge cases and be very hard to decide on.

• automatic supertagging. It seems that this has been vetoed by Jeff on his comment, and might be hard to implement.

Or should we reject all supertagging edits, since all of the above have problems? But then, how do we decide what counts as a supertag and what does not? If we decide everything that is not a supertag, wouldn't that be the same as deciding what is a supertag?

EDIT when I asked this I had in mind for it to be a conditional discussion: if we want to add super and sub tags, how should we do it, and not if we should do it or not (true, the way it was asked was very partial). I suggest the question of should we add both tags be moved to this older question which as far as I understand already discusses that. Thinking about it now, this could even be marked as a dupe, because it we decide that we should do something, then we should also decide how at the same time.