Similarly, I use daml: ObjectProperty to define properties.
类似地，我使用daml：ObjectProperty定义特性。
Listing 2 is a DAML + OIL schema for the issue tracker similar to Listing 1.
清单2是类似于清单1的问题跟踪程序的DAML +OIL模式。
Now I'll complete the definition of the issue tracker schema, in RDFS and DAML + OIL form.
现在，我将以RDFS和DAML +OIL形式完成问题跟踪程序模式的定义。
Otherwise, there are no surprises in this schema, so let's move on to a look at the DAML+OIL version.
除此之外，在这一模式中没有什么值得奇怪的，好了，让我们继续了解DAML+OIL 版本。
It is defined as a subclass of an anonymous in-line resource, which in turn is of type daml: Restriction.
它被定义为匿名内联资源的子类，而匿名内联资源类型又是daml： Restriction的类型。
As standard practice, I import the core DAML + OIL schema, adding definitions for DAML + OIL-specific resources.
作为标准实践，我导入核心DAML +OIL模式，为特定于DAML +OIL的资源添加定义。
This is a special DAML + OIL mechanism that allows you to define rules according to the properties instances have, and the values of those properties.
这是一个特殊的DAML +OIL机制，它允许您根据实例具有的特性以及这些特性的值来定义规则。
This is a DAML convention that describes the document and specifies the schema (hence the empty rdf:about, which sets the document itself as the subject).
这是一个DAML约定，它描述文档、确定模式（因此使用空的rdf:about ，它将文档本身设置为主题）。
The DAML + OIL schema is actually what is being used in RDFInference.org applications, and is what we'll use as the basis of continuing work in this column.
DAML +OIL模式实际上就是在RDFInference.org应用程序中所使用的那种模式，而且我们也将它用作本专栏继续下去的基础。
RDFS is still the simplest and most pervasive choice, but DAML + OIL has many things to recommend it: not just the additional features, but the cleaner core semantics as well.
RDFS仍然是最简单、最普遍的选择，但是DAML +OIL有许多好的方面，还是值得推荐：不仅是额外的功能，而且还包括更清晰的核心语义。
RDFS is still the simplest and most pervasive choice, but DAML + OIL has many things to recommend it: not just the additional features, but the cleaner core semantics as well.
RDFS仍然是最简单、最普遍的选择，但是DAML +OIL有许多好的方面，还是值得推荐：不仅是额外的功能，而且还包括更清晰的核心语义。
应用推荐