11

There are a bunch of tags prefixed with WPF, most, if not all, of which in my opinion have no justification for existing, because if their generic versions are paired with the general WPF-tag that is quite enough:

There are synonym proposals for some of those and some of the tags are not used in many questions so manual retagging might be an option, but first of all: Do people agree that those tags are generally not needed, are there any specific tags worth keeping? Also: What to do if there is a consensus?

Edit: Just to be more clear, I would propose assimilation via synonyms so that for example is mapped to and is mapped to , I do not propose the blunt removal of tags.

It would be nice if a moderator could do something about this, the synonym proposals on the major tags do not even seems to be noticed...

Databinding tags screenshot

Improve this question
4
  • There might be a use case for these tags: as far as I know, it is not possible to follow the intersection of two tags. Thus if I'm only interested in wpf-xaml, it after the remapping is not possible to follow wpf ∩ xaml. (I'm not interested in this, but there might be people who are.)
    – Paŭlo Ebermann
    Aug 22, 2011 at 9:44
  • @Paŭlo Ebermann: In my opinion the tags should not be modelled after this, if someone wants an intersection they do a search with both relevant tags.
    – H.B.
    Aug 22, 2011 at 14:08
  • Are you suggesting synonyms or deletion?
    – Yuck
    Aug 25, 2011 at 17:38
  • @Yuck: Does not really matter as long as the questions affected have the more generic tag afterwards.
    – H.B.
    Aug 25, 2011 at 19:08

4 Answers 4

Reset to default
4
+50

I don't think these are entirely wrong but definitely a lot of egregious over-tagging going on here.

Mostly, I deleted any wpf-* tag that had less than 60 ~ 80 questions attached.

Improve this answer
1

As far as I can see, only (or ) would stand on its own. Maybe given we've still got 3.5'ers around.

Tags which should drop the wpf- prefix and stand on their own:

Some tags that may stand on their own (but may not need to be added because of ):

  • controltemplates
  • datatemplate
  • styles
  • resources
  • triggers
  • commands
  • themes
  • storyboard / animation
  • validation (we see lots of these)

The rest should be removed as far as I can tell.

Improve this answer
2
  • I would drop the latter as well, those questions should just be tagged wpf wpftoolkit datagrid, don't you think?
    – H.B.
    Jun 10, 2011 at 15:06
  • 1
    I agree, although I hate when I have to go back and revise/delete an answer of mine for the 4.0 datagrid when they wanted the 3.5 toolkit datagrid. But I think accurate tagging could solve that.
    – user7116
    Jun 10, 2011 at 15:10
0

I would not mind manually retagging all afflicted questions to strip out the prefixes, but this will result in ~3000 questions being bumped during the process...

Improve this answer
1
  • I don't think the prefix (as there's only one) should be stripped out. It will encourage users to tag with wpf-* instead of [wpf] [something] [else].
    – M. Tibbits
    Aug 28, 2011 at 19:20
-1

What about a Facebook style themed portal on Stack Overflow?

< http://wpf.stackoverflow.com > ??

has over 32K questions by itself. has only 11K?

Improve this answer
2
  • meta.stackexchange.com/questions/103977/…
    – Cody Gray
    Aug 28, 2011 at 22:35
  • @Cody, yep. I didn't this would be the policy until two days ago. I proposed this three days ago. Not sure if I should edit my suggestion as I believe .Net could stand as its own mini-site.
    – M. Tibbits
    Aug 28, 2011 at 23:03

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