Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

Is there a facility, either planned or available, to prevent some ambiguous and/or overlapping tags from being used. See, for example, this discussion Tag overlap: Oracle APEX and APEX VisualForce.

I think that could be safely banned, because, for instance, the question Oracle APEX: popup menuOracle APEX: popup menu before editing had , while the better fit would be to have on it, and you could understand neither from initial tags nor from the title what this question is about unitl you follow it and read the question.

neither adds anyting useful to the question, nor does it remove the ambiguity. I would get rid of it and retag existing questions having to have .

Is there a facility, either planned or available, to prevent some ambiguous and/or overlapping tags from being used. See, for example, this discussion Tag overlap: Oracle APEX and APEX VisualForce.

I think that could be safely banned, because, for instance, the question Oracle APEX: popup menu before editing had , while the better fit would be to have on it, and you could understand neither from initial tags nor from the title what this question is about unitl you follow it and read the question.

neither adds anyting useful to the question, nor does it remove the ambiguity. I would get rid of it and retag existing questions having to have .

Is there a facility, either planned or available, to prevent some ambiguous and/or overlapping tags from being used. See, for example, this discussion Tag overlap: Oracle APEX and APEX VisualForce.

I think that could be safely banned, because, for instance, the question Oracle APEX: popup menu before editing had , while the better fit would be to have on it, and you could understand neither from initial tags nor from the title what this question is about unitl you follow it and read the question.

neither adds anyting useful to the question, nor does it remove the ambiguity. I would get rid of it and retag existing questions having to have .

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

Is there a facility, either planned or available, to prevent some ambiguous and/or overlapping tags from being used. See, for example, this discussion Tag overlap: Oracle APEX and APEX VisualForceTag overlap: Oracle APEX and APEX VisualForce.

I think that could be safely banned, because, for instance, the question Oracle APEX: popup menu before editing had , while the better fit would be to have on it, and you could understand neither from initial tags nor from the title what this question is about unitl you follow it and read the question.

neither adds anyting useful to the question, nor does it remove the ambiguity. I would get rid of it and retag existing questions having to have .

Is there a facility, either planned or available, to prevent some ambiguous and/or overlapping tags from being used. See, for example, this discussion Tag overlap: Oracle APEX and APEX VisualForce.

I think that could be safely banned, because, for instance, the question Oracle APEX: popup menu before editing had , while the better fit would be to have on it, and you could understand neither from initial tags nor from the title what this question is about unitl you follow it and read the question.

neither adds anyting useful to the question, nor does it remove the ambiguity. I would get rid of it and retag existing questions having to have .

Is there a facility, either planned or available, to prevent some ambiguous and/or overlapping tags from being used. See, for example, this discussion Tag overlap: Oracle APEX and APEX VisualForce.

I think that could be safely banned, because, for instance, the question Oracle APEX: popup menu before editing had , while the better fit would be to have on it, and you could understand neither from initial tags nor from the title what this question is about unitl you follow it and read the question.

neither adds anyting useful to the question, nor does it remove the ambiguity. I would get rid of it and retag existing questions having to have .

Fixup of bad MSO links to MSE links migration
Source Link

Is there a facility, either planned or available, to prevent some ambiguous and/or overlapping tags from being used. See, for example, this discussion Tag overlap: Oracle APEX and APEX VisualForce.

I think that apex could be safely banned, because, for instance, the question Oracle APEX: popup menu before editing had apex, while the better fit would be to have oracle-apex on it, and you could understand neither from initial tags nor from the title what this question is about unitl you follow it and read the question.

apex neither adds anyting useful to the question, nor does it remove the ambiguity. I would get rid of it and retag existing questions having apex to have oracle-apex.

Is there a facility, either planned or available, to prevent some ambiguous and/or overlapping tags from being used. See, for example, this discussion Tag overlap: Oracle APEX and APEX VisualForce.

I think that apex could be safely banned, because, for instance, the question Oracle APEX: popup menu before editing had apex, while the better fit would be to have oracle-apex on it, and you could understand neither from initial tags nor from the title what this question is about unitl you follow it and read the question.

apex neither adds anyting useful to the question, nor does it remove the ambiguity. I would get rid of it and retag existing questions having apex to have oracle-apex.

Is there a facility, either planned or available, to prevent some ambiguous and/or overlapping tags from being used. See, for example, this discussion Tag overlap: Oracle APEX and APEX VisualForce.

I think that could be safely banned, because, for instance, the question Oracle APEX: popup menu before editing had , while the better fit would be to have on it, and you could understand neither from initial tags nor from the title what this question is about unitl you follow it and read the question.

neither adds anyting useful to the question, nor does it remove the ambiguity. I would get rid of it and retag existing questions having to have .

Migration of MSO links to MSE links
Source Link
Loading
added 314 characters in body
Source Link
Loading
Source Link
Loading