Everybody starts somewhere. Starting is the important part. :-)

It's great that you're thinking about these issues. In most cases, if you want to recommend improving tags, you need to lay out the case more fully. Describe how the tag is currently used and the problems associated with that usage. Suggest a comprehensive plan for how to deal with all of the needed changes -- what new tags are needed, what usage gets changed to what new tag, etc.

General learning (and idle curiosity) are off-topic unless the community makes an exception because there is a clear nexus to something on-topic. That's why I suggested earlier to try to reframe your question with some context that relates it to an on-topic issue.

That's different from internal information like why a company made a decision a certain way, or the trade craft they might have used to accomplish something, which they don't publicize (even if the information is available somewhere). What is clearly on topic here is solving user problems with a personal computer. The underlying principles can be relevant to solving the problem or understanding the solutions. "Proprietary-type" information generally isn't required to solve issues that are on-topic for the site, or the associated solutions aren't really on-topic here. (cont'd)

Actually, we may not know definitively that it is proprietary, so that answer could also be "wrong". :-) It may have been disclosed publicly somewhere and just not well known. We occasionally get questions that I think are proprietary information and it turns out somebody here just happens to know the answer. In thinking about whether a question is on topic, I differentiate general knowledge from knowledge that seems likely to be proprietary. General knowledge is the "underlying principles", stuff anyone has access to. (cont'd)

True, and people ask whatever they want to know. Then the users here, in their great collective knowledge and wisdom, either answer or close the question.

True, it can be a general learning question, but those are off-topic per the Help section except in limited cases where the community makes an exception. To be such an exception, among other criteria, it has to be something knowable and demonstrable, within scope, etc.; for example knowledge that underlies or is closely tied to an on-topic issue, is publicly available, can be looked up and verified, can be well explained within the intended scope of an answer, etc. Proprietary details aren't general learning. That's where allquixotic's answer comes in. Couldn't have said it better myself. :-)

Franck, I was one of the close voters. BlueJeans is an Internet video conferencing service. To me, the internal algorithms they use for estimating participation is part of their system design and operating policy rather than something a user does on their computer. I just don't see it as on-topic (unless you can tie it in better in the question to a user issue that can be solved or definitively explained by our users).

With certain topics like Excel, people tend to follow the general tag rather than every version tag, so there's value in including both the general tag and the specific version (but not tagging with every version). An additional tag for the OP's version is more important if that is an old version that might not support features or functions offered in solutions, or a new version that might enable a solution that wouldn't work in an old version. It also facilitates testing solutions for validation and diagnostics against the OP's version.

This kind of tagging guidance has been discussed a lot in the past. Here are some links to relevant discussion (and these links contain more links: meta.superuser.com/questions/12291/the-scope-of-the-windows-‌​tag, meta.superuser.com/questions/9198/…