文件名称：OMG 本体定义元模型 V1.1 英文版
文件大小：3.46MB
文件格式：PDF
更新时间：2022-09-18 08:30:20
OMG 业务建模 架构
Ontology Definition Metamodel V1.1.pdf There are several compliance points distinguished for the Ontology Definition Metamodel. These include: 1. None or Not Compliant, meaning that the application in question is not compliant with a particular metamodel, as defined by the metamodel itself, the abstract syntax, well-formedness rules, semantics, and notation specified for a particular package or set of packages. 2. Compliant, meaning that the implementation fully complies with the abstract syntax, well-formedness rules, semantics and notation of a particular package or set of packages. 3. Interchange, indicating that the implementation provides compliance as specified in [2], and can exchange metamodel instances using ODM package conformant XMI. There are several possible entry points for implementations that want to provide/claim minimal compliance with the ODM. These require compliance with one of the following base metamodel packages: • RDFBase Metamodel Package (RDFBase is a sub package of the Resource Description Framework (RDF) Metamodel Package). • Topic Maps (TM) Metamodel Package. • Common Logic (CL) Metamodel Package. For a given implementation to claim ODM compliance, it must be Compliant, as defined in 2, above, with one of these three packages. There are several compliance options available to vendors for the RDF Metamodel Package. These include: • RDFBase Only - as implied above, this package contains the set of elements requ ired for core RDF support, such as is necessary to support a triple store implementation; the focu s here is on the set of constructs defined in the RDF Concepts and Abstract Syntax [RDF Concepts] document. • RDFBase + RDFWeb - provides core RDF support and fits these concepts to the World Wide Web. • RDFBase + RDFS - moves the implementation focus from core RDF to RDF Schema, as specified in [RDF Schema]. • RDF - meaning, the implementation supports all of the concepts defined in the three sub packages, which represents RDF Schema fitted to the Web. There are two possible compliance points for the OWL Metamodel Package. Each of these requires support for the entire RDF package, including the RDFWeb component. They include: • OWLBase + OWLDL - focus is on a description logics application that constrains an ontology in turn for DL decidability. • OWLBase + OWLFull - focus is on more expressive applications rather than on decidability of entailment. The complete set of ODM compliance options is summarized in Table 2.1.