Article Description: the difference between a label and a tag. |
The question of the difference between tag and label was raised in the description and the general description last year, when the conclusion was not clear enough, presumably "tag is a generic description, and label is description". Recently, "Do" product feeling not deep, but "with" the touch of products, let me seem ...
The question of the difference between tag and label was raised in the description and The general description last year, when the conclusion was not clear enough, presumably "tag is a generic description, and label is description". Recently, "Do" product feeling is not deep, but "with" the touch of the product, let me seem more clear the difference between tag and label. For example, you might encounter a situation like this:
- NetEase Mailbox "Speed 3.0" and "Simple 3.0" What is the difference?
- Taobao sellers backstage, "The shopkeeper recommended" and "window Recommendation" What is the difference?
I understand that "speed" and "simplicity" in the mailbox are related words, because "simple" so "speed", they are not a peer relationship, so as a side item will have to communicate the problem. I understand that Taobao sellers backstage in the "shopkeeper recommended" and "window Recommendation" user understanding is one thing, is "window recommendation" of the goods is not "shopkeeper" recommended it? So it is also easy to create ambiguity when describing a function.
The above two questions may need to the corresponding product more familiar person only then knew, believed that everybody will soon think oneself has used the product the similar doubt. This kind of problem is quite common, its root lies in the generalization of the content deviation, but obviously this problem is not tag, in the content organization category that should be what? The answer is label, in addition to product description, its application scope also involves the function name, module name, navigation name, guide text and so on scene.
Also in the design perspective, we often want to break the head to describe a product function, either for more accurate, or to better understand, the premise is tightly around our core user base. If the product is primarily for advanced users, it requires an accurate and professional description and requires a hardening of terminology; if it's primarily for beginners, then you need a rough and folk description to try to avoid terminology.
In fact, we all know that the same products to take into account the two types of users is not realistic, the common approach is a partial version. Of course, the name of the version is returned to the "description" of the topic, a good version name is the key to success (refer to the previous NetEase email example). The general system's understanding of the hierarchy may be "elementary, intermediate, advanced" three categories, but can be combined with the business type to customize more "moving" description, such as I think Taobao Wang Pu "primary version" is called "Entrepreneurial support version" is a good idea, very direct to impress the user. Or, let's refer to the Win7 about the six different levels of "beginner, home, home, professional, Enterprise, flagship," for each typical user and scenario.
Basic can be understood as, from the product's initial "product name" to "Product name", and then "function module name" And so on, in fact, need to do a serious label. Therefore, there is no departure from the "Pan description, description" Of the view, I think "label is a description" of the conclusion is relatively accurate. Tag write more content, do not repeat the elaboration. In a further comprehensive comparison, I think there are three significant differences between tag and label:
- Label is its own, tag is attached;
- Label emphasis is a sign, tag emphasis is a mark;
- The label indicates the attribution between the information, and the difference between the tag difference information.
Of course, it's best to have a Chinese counterpart. Tag called "tag" in the translation of basic no problem, and peer understanding is also relatively unified. The Chinese translation of label is considered to be more suitable for "marking", the description is more accurate (in fact, this generalization is also the process of doing label), and also with "tag" very good partner up. So, there's this picture shared at the UCD2010 Annual Meeting :
To start to mention "NetEase mailbox" and "Taobao sellers backstage" of those two issues, to provide two points of thought. "NetEase Mailbox" of the speed version, simple version of the reservation "Speed version" can be, "default" should also be changed to "Standard Version", and should be the default "Speed version" (recommended). Taobao sellers backstage, "The shopkeeper recommended" and "window Recommendation" These two functions merged into the "shopkeeper recommended", and then further subdivided the recommended to reach the "search results page, shop and Merchandise page" of the two types of channels.