A while ago we ran an experiment to see if it would be helpful to adopt a Sci-fi and Fantasy-inspired approach to tagging continuities where every question has a franchise tag and questions that focus mostly on a single series would additionally carry a series tag. That experiment was started in A certain multivariate experiment: Testing changes to series tags based on story continuity.
Under the terms of that experiment, we were going to do SF&F-style tagging for Full Metal Alchemist, where every question has the fma-series tag and questions focusing on a specific continuity would also carry a tag for that continuity (e.g. fullmetal-alchemist-2003). We were going to do single tags for the Dragon Ball series, if a question only concerns DBZ, it has the dragon-ball-z tag, and if it concerns the entire franchise (e.g. something like "Why is Goku's hair so spiky?", since Goku's hair appears in every Dragon Ball series), it would have the dragon-ball-series tag only.
It seems like this user was trying to apply the rules we were using for fma-series to the dragon-ball-series tag. I, at least, was also confused about this point and ignorantly approved a few of these edits, but when they kept on coming I started skipping them so that another member of the community could double check. (Plus, bumping a ton of old posts to the front page for a tag edit isn't cool; a few is fine, but more than three or four is a little excessive.)
As far as I can tell, we never did come to a conclusion about which tag scheme we were going to adopt. The way we were tagging Dragon Ball questions was basically the system we already had, so we should probably collect opinions from people who participated in the Full Metal Alchemist tags under this system about whether they think it would be good to adopt it for other series with several different continuities.
(For the record, at the time I supported the scheme we were using for Full Metal Alchemist. I still think it works really well for cases like Sci-fi and Fantasy where you have huge franchises with multiple independent works, but it is pretty high maintenance.)