Should the "metro" tag refer to a Java framework or Windows 8 technology? [closed]

Question

Looking through pending edits, I noticed someone had stripped metro off a Java webservices app.

However, Metro is a well-known Java WS framework, as well as what the tag currently says: "Metro is the user interface design developed by Microsoft and used in recent Zune firmwares, Windows Phone 7 and Microsoft Windows 8."

What do we do when one tag clearly fits two completely different technologies? I'm actually surprised that metro wasn't already in-use for Java purposes; its existence predates Windows 8 by a number of years.

Some additional background is on Tag merge request: [metro-ui] and [metro].

Answer 1

There already is a metro-ui tag. Use it for the Windows questions. I just edited 20 or so of the metro questions about the Windows UI; if 10-20 of us take 10 minutes each we can be done shortly, as there are only 269 questions with the tag.

As cdeszaq and Ben Brocka suggested, a framework-specific tag should be used for the Java questions.

There are two schools of thought on prefixes: One states that it should have a java prefix, so it can be easily filtered. The other states that it should have no such prefix, so that it can be easily found by people who start typing metr. Either tag, be it metro-framework or java-metro-framework, would be preferable to the current dual meaning.

After the existing questions are divided up, there should be no vanilla metro tag. People don't read the tag wikis, so this tag would still need to be cleaned up. That's undesirable.

---

Edit: I went through about 30 of these today in two sessions. I came across 1 Java question, and there is another down the page a little ways, but the vast majority are metro-ui questions. It would be far easier to just edit all the Java ones, have a mod do a merge without synonym creation, and delete the original tag.

Answer 2

I think it best to leave the "vanilla" metro tag for the Windows UI and perhaps have java-metro-framework or something similar for the java framework.

Given the following (unfortunate) facts...

1. People don't read, so differentiating using the tag wiki excerpt won't do any good
2. The metro-ui will get much more press as Windows 8 moves towards release
3. There are many more .Net / Windows-oriented questions than there are Java oriented questions

...having the more commonly used (or most likely used) tag as the shorter varient is likely to keep things the cleanest and reduce the need to re-tag things. Unfortunately, the whims of the unwashed masses who apply the first tag that they see drives what tages are used. Making the more commonly chosen tag line up with the more common topic reduces the disconnect, keeps things clean, and makes the lives of editors easier.

I would much rather see a tag have one use (especially if it can be rather specific as opposed to a paradigm like mvc), like a specific framework or UI, than for a tag to be used for multiple rather distinct things.

Answer 3

You update the Wiki to reflect this, then whenever you see it being messed with @ the user who edited to ask them to check the wiki.

The same situation came up with me when I was informed that knockoutjs also described its architecture as mvvm. I stopped removing it from javascript questions and updated the wiki to reflect the dual nature of the tag.