I think they should, 2010/2007/2003 (can't recall) use a different type of field, even though they are the same field. I'd say create a tag, ClientPeoplePicker with a description that it is 2013/2016 specific.
If we are going to differentiate on product versions, we should be able to have version specific tags for aspects that are functionally different but ...
I really appreciate your concern here moe. If you have the reputation, the only thing you can do is to edit the question back and remove the tag. I wish there's a way to see who approved the edits and who hasn't BEFORE you make your decision.
I can't say I'm 100% sure I haven't approved these kinds of edits in the past, but thanks for bringing it to our ...
I too really appreciate the question and suggestions by @Moe and @Mike.
I have reviewed more than 300 edits till now, I always reject those edits which are just not required or does not make post more effective.
When I am confused whether to approve or not, I always choose Skip option.
I believe having score more than 2000 is a kind of responsibility. You ...
I will reject version tag edits if they are the only edit and if they are something that is truely not version specific.
Editing a post to include 2013 tag on a minimal download question. Approved.
Editing a post to include 2013 tag on a claims question. Rejected.
I agree with Mike on the following, as it seems like the only action we currently are able to do:
the only thing you can do is to edit the question back and remove the tag
Recently I've done some edits on questions, some of them obviously necessary, some for clarification and some which might have done a significant change on the body text although ...
This has some legacy to it, and I don't see them as wrong, for several reasons.
The sharepoint-enterprise, has its counterpart in both sharepoint-foundation and sharepoint-standard. In the old 2010-version of SharePoint it was possible to use the free version SharePoint foundation only. And up until today we can still use SharePoint-standard instead of a ...
It is off topic, It seeming always pops back up because people keep asking questions. We close them off topic, they eventually expire and the tag goes away, only to pop back up again because someone asks a question and tags it as such.
Thank you for readdressing this. Version tags wouldn't be a problem if users know that tags are for specific items. They use the tags to post more info about the environment they are using. Since there is no ideal and obvious way of posting the version, tags seem like the way to go for a new user. It would even go up to the point of putting a "Windows Server ...
I personally feel that rest-api is a great tag for this.
Maybe it is a good idea to think about merging the two tags above though? This tag combined with a statement about what SharePoint version is in question should be well enough to scope this type of question.
It is not possible to delete tags. But, tags that are not used by any questions will be deleted in about 24 hours.
So I propose that you edit the question, to replace the tag with disposing. If the edit is accepted the tag should self-destruct :)