我应该对分层标签使用哪种用户级抽象？
通过用户级抽象，我的意思是我应该如何称呼它们以及我应该使用什么样的图标在 UI 中表示它？ 现在大多数用户应该熟悉标签的概念，但我不太确定分层标签是否熟悉，标签的抽象也不完全适合。
我所拥有的实际上是介于文件夹和标签之间的东西，因为每个子标签都是其父标签的适当子集。 要获取文件夹标签事物的内容，您需要获取其内容及其子文件夹标签事物的内容，并递归地执行此操作。 在某种程度上，它们就像（这里是我在提问过程中部分回答了我自己的问题）类别。 你们觉得将它们称为类别怎么样？ 既然类别是一个抽象概念而不是一个可以成形的物理对象，你会给它什么样的图标？
（如果需要，可以维基）
编辑：为了澄清，我正在寻找的是像莎莉阿姨这样的最终用户的抽象，可以轻松掌握这个概念。 理想情况下，还有一个可以轻松与该概念相关联的图形表示（图标）。
Edit2：我忘记提及的一件事是，一个项目可以存在于多个类别中（就像 Google Doc 允许您将文档添加到多个文件夹一样）。 我想我已经把它们称为类别了。 它恰好适合您可以用它们做的一切。 某些东西可以属于多个类别，子类别是有意义的，人们通常创建的大多数子类别都适合一种“是”关系（例如，Windows 用户可能会说“我的文档”文件夹中有一个名为“简历”的文件夹，因为简历是一个文档，如果您将文件夹视为类别，那么它也位于“我的文档”中是有意义的）
我仍然没有弄清楚的是图标（我 99% 确定我将使用一些一种 TreeView 来显示它们）我想我可以只使用一个文件夹图标，也许是一个自定义的类似文件夹的图标，除非其他人有更好的主意。 谷歌称它们为文件夹，所以我想这不会太糟糕吧？
为了进一步澄清，我的目标受众将是技术足够的人，知道如何下载和安装应用程序，但仅此而已。
By user-level abstraction I mean what should I call them and what kind of icon should I use to represent it in the UI? The concept of tags should be familiar to most users right now, but I'm not so sure hierarchical tags are, nor does the abstraction of tags completely fit.
What I have is actually something between folders and tags, in that each subtag is a proper subset of its parents. To get the contents of a folder-tag-thing you take its contents plus the contents of its sub-folder-tag-things and do that recursively. In a way they're like (and here's where I just partially answered my own question in the process of asking it) categories. What do you guys think of calling them categories? What kind of icon would you give it, since a category is an abstract concept rather than a physical object that can take a shape?
(Can wiki if requested)
Edit: For clarification, what I'm looking for is an abstraction for an end-user like Aunt Sally that easily grasp the concept. Ideally there is also a graphical representation (an icon) that can be easily associated with that concept.
Edit2: One thing I did forget to mention is that an item can exist in more than on category (much like how Google Doc allows you to add an document to multiple folders). I guess I've kind sold myself on calling them categories. It just fits everything you can do with them. Something can belong to a more than one category, subcategories make sense, most subcategories people normally create lend themselves to an is-a relationship (for example, a Windows user might have say a folder called resumes in their My Documents folder, because a resume is a document, it would make sense that it's in My Documents as well if you think of the folders as categories)
What I still haven't figured out is the icon (I'm 99% sure I'm going to be using some kind of TreeView to display them in) I could just use a folder icon I suppose, maybe a custom folder-like icon unless anyone else has a better idea. Google calls them folders, so I guess it can't be too bad right?
To clarify further, my target audience will be people technical enough to know how to download and install the app, but that's about it.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
如果您的目标受众是技术人员，那么树视图和/或文件夹是抽象分层数据的常用方法。 它们都是复合模式的变体。
不过，在后谷歌时代，我倾向于认为层次分类不如平面标签/标签空间与快速搜索相结合那么重要。 恕我直言，如果数据集的大小很大（例如，> 1000 个文档/元素），那么分层分类的开销会压倒将文档放入漂亮的整齐类别的名义好处。
如果您的目标受众是非技术人员，那么根据我的经验，非技术用户不会获得层次结构，也不会花时间找出多个级别的分类。
If your target audience is technical then TreeViews and/or Folders are common ways of abstracting hierarchical data. They're all variants of the Composite pattern.
In the post-google era though, I've tended to consider hierarchical categorization less important than a flat tag/label space combined with a very fast search. IMHO if the size of the dataset is large (e.g., > 1000 documents/elements) then the overhead of hierarchical categorization overwhelms the nominal benefit of having documents placed into nice neat categories.
If your target audience is non-technical then it's been my experience that non-technical users do not get hierarchies and won't take the time to to figure out more than a single level of categorization.
对我来说，答案来自 Opera Desktop Team 博客（以及 Dotclear 的博客，它使用了相同的约定，感谢他们我也发现了它）：
tag:subtag-
CSS:font当您单击 CSS:font 时，您知道它是更大 CSS 标记的一部分。 标签页面应该有一个文本，指示父标签可用（或者您可以自己找到它，在维基百科上可以通过直接 URL 操作找到它）。
我有在 WordPress 上进行的讨论。
For me, the answer comes from the Opera Desktop Team blog (as well as Dotclear’s blog, which used the same convention and thanks to whom I discovered it too):
tag:subtag-
CSS:fontWhen you click on the CSS:font, you know it is part of a larger CSS tag. The tag page should have a text indicating that a parent tag is available (or you can find it by yourself, much on Wikipedia with direct URL manipulation).
I have a discussion running on WordPress.
您可以使用“捆绑包”（如 del.ico.us 所做的那样）。 我不确定超过一级对标签是否有意义。
You could use "bundles" (as del.ico.us does). I am not sure if more than one level is meaningful for tags though.
标签“细节”怎么样？ 由于子标签是真子集，因此可以将其视为将详细信息应用于标签......
How about a tag "detail"? Since a subtag is a proper subset, it can be thought of as applying detail to a tag...
对我来说这听起来像是一个大纲。
有大纲标记语言 (OML)。
It sounds like an outline to me.
There's the Outline Markup Language (OML).