I had deleted this answer shortly after posting it. At the time I felt my suggestion for the description of table was a bit convoluted. However I still think that keeping low quality tags that are very general is an option that should be taken seriously, so I have undeleted my answer. When reading it please do not bother yourself too much with the details.
Introduction
I agree with Szabolcs points. In fact, I am in favour of preserving all the tags.
I feel the word table in the context of Mathematica is a bit ambiguous. On one hand, we have the meaning of table as a 2D sheet of information to be read or even altered by humans. On the other, we have the meaning that comes from the function Table
. This is the main motivation for my suggestion.
Suggestion
I have written this in such a way that we can vote for it. More motivation, examples and considerations are further below. Please disregard these in voting.
Concept table
This information could be added to the /info page of table
We understand under a table an expression that is either the result of a typical use of Table
, or an expression that looks like a 2D list and which is meant to be displayed, for example using TableForm
. An example of the latter kind of expression would be {{name,weight},{john, 60},{mary, 50}}
, which is not an expression typically generated by Table
.
Questions that should be tagged with table are questions in which a table plays a central role, or the use of the function Table
plays a central role.
It is acceptable to tag questions about fine tuned formatting of a table with table, even though it is preferable to (re)tag such questions with grid.
If the question is about data structures, the tag array is preferred.
If the question is not about the generation of a table, but rather the use of it, it may be preferable to tag as matrix or tensor. Do this in case the table is in fact a matrix/tensor and built-in functions that deal specifically with such expressions (like Dot) are used.
Tag wiki (description) table
Tag questions in which either 1) the function Table
plays a central role, 2) a nested list plays a central role or 3) a two dimensional expression that is meant to be displayed, for example using TableForm, plays a central role.
Examples table
An example of a question where the use of Table
plays a central role would be this and maybe even this (even though ParallelTable
is used instead of Table
). Especially because the idiom If[cond, return, Sequence@@{}]
is used, where Sequence@@{}
is equivalent to Mr.Wizards vanishing function. This shows that Table
is more flexible than one might think.
this is an example of a question in which a central role is played by an extreme of the set of expressions that the description of table above encompasses.
More examples where the use of Table
could be nontrivial is where the side effects of Table
are important, or when we want to use Table
inside Compile
.
Tag wiki (description) array
This tag is reserved for questions about the data structure array. Simply using the function Array does not justify using this tag.
Note: Unfortunately, I am not sure if tag wikis can be bold
Motivation
The reason to make the tag table encompass a broad class of expressions is to avoid mistagging. To see that mistagging is a problem, think about how many times the tag bugs is incorrectly used. One reason to make table a general tag and array a more specific tag, is that Table
is used much more often than Array
, and consequently table is used more often than array. This is convenient, as array is also the name of the Array data structure, which is an important concept IMO.
Considerations
We should probably also provide text for the /info page of array. This should especially make clear that table can be used as an alternative.
I would suggest also writing the word reserved in the tag wiki (description) of bugs in bold (if this is possible).