类别也是可浏览的，每个类别只具有一个父类别。
Categories are also browsable, with each having only one parent category.
平原对象定位使得在父类别预计的地方使用派生的任何类。
Plain object orientation makes it possible to use any derived classes in places where the parent class is expected.
由于文档和其他类别可以继承父类别的标记，从而产生一个完整的层次结构。
Both documents and other categories can be tagged with a parent category, resulting in a complete hierarchy.
这样，分类法就拥有了一个根类别，它可以是其他许多类别的父类别。
The taxonomy then holds a root category, which can be the parent of a number of other categories. So from the top-down, this is how OmniFind 8.2.1 appears to the connector developer.
Parentcategory(父类别)——包含这个术语的类别。
通过一个简单的向导，您能够为这个类别选择父类别，并且为这个类别命名。
This takes you through a simple wizard where you can choose the parent category and a name for the new one.
它是精确开发商有责任确保它是安全的地方父类别预计使用派生的任何类。
It's a precise developer's responsibility to ensure that it's safe to use any derived class in places where the parent class is expected.
这将让您看到一个简单的向导，您可以在该向导中选择新类别的父类别和名字。
This takes you through a simple wizard, where you can choose the parent category and a name for the new one.
简单地说，利斯科夫原则指出应该始终是安全的在父类别预计的任何地方使用子类。
In a nutshell, the Liskov principle states that it should always be safe to use a subclass in any place where the parent class is expected.
还需注意，关键词类别存储在维表CATEGORY中，在这个表中，每个类别指向它的父类别。
Also note that the keyword categories are stored in the dimension table category, where each category points to its parent category within this table.
TaxonomyBrowser提供了一个类别的层次结构；每个类别可以访问自己的父类别和子类别。
The TaxonomyBrowser provides a hierarchy for categories; each category has access to its parent category, as well as its child categories.
请注意，一般来说，衍生类别会比它们衍生来源的类别还不可靠，虽然某些情况下它们会共用父类别的识别。
Note that, in general, derived classes can be less trustworthy than the class they derive from, though in some cases they share the parent class's identity.
派生的类重写的方法，只是添加更多的应该补充了基类的功能，像是一种特殊情况的所有父不会不会的父类别和更多。
More interestingly, it also reads better, because a precondition lets you clearly state just what's required instead of testing against what isn't desirable.
我之所以选用了这种方法(参见清单5)是因为在本例中这些类别链接的父组件是固定的，并且也是预先定义了的。
I choose this method (see Listing 5) because the parent of the category links is fixed and predefined in the example.
在普通的类别层次结构中，同一父类的兄弟类别之间的混淆关系是对称的，但事实上类别之间的混淆关系不是对称的。
In the general hierarchical structure, confusion relationship among brother classes that have the same parent class is symmetrical. But in fact that's not the case.
在普通的类别层次结构中，同一父类的兄弟类别之间的混淆关系是对称的，但事实上类别之间的混淆关系不是对称的。
In the general hierarchical structure, confusion relationship among brother classes that have the same parent class is symmetrical. But in fact that's not the case.
应用推荐