OMG本体定义元模型V1.1英文版

需积分: 9 157 浏览量更新于2023-05-30 评论收藏 3.46MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

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.

资源详情

资源评论

资源推荐

Date: September 2014

Ontology Definition Metamodel

Version 1.1

OMG Document Number: formal/2014-09-02

Standard Document URL: http://www.omg.org/spec/ODM/1.1/

Normative Machine Consumable Files:

http://www.omg.org/spec/ODM/20131101/ODM-metamodels.xmi

http://www.omg.org/spec/ODM/20131101/RDFProfile.xmi

http://www.omg.org/spec/ODM/20131101/OWLProfile.xmi

http://www.omg.org/spec/ODM/20131101/RDFLibrary.xmi

http://www.omg.org/spec/ODM/20131101/XSDLibrary.xmi

http://www.omg.org/spec/ODM/20131101/OWLLibrary.xmi

USE OF SPECIFICATION - TERMS, CONDITIONS & NOTICES

The material in this document details an Object Management Group specification in accordance with the terms, conditions and

notices set forth below. This document does not represent a commitment to implement any portion of this specification in any

company's products. The information contained in this document is subject to change without notice.

LICENSES

The companies listed above have granted to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid up,

worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version.

Each of the copyright holders listed above has agreed that no person shall be deemed to have infringed the copyright in the

included material of any such copyright holder by reason of having used the specification set forth herein or having conformed any

computer software to the specification.

Subject to all of the terms and conditions below, the owners of the copyright in this specification hereby grant you a fully-paid up,

non-exclusive, nontransferable, perpetual, worldwide license (without the right to sublicense), to use this specification to create and

distribute software and special purpose specifications that are based upon this specification, and to use, copy, and distribute this

specification as provided under the Copyright Act; provided that: (1) both the copyright notice identified above and this permission

notice appear on any copies of this specification; (2) the use of the specifications is for informational purposes and will not be

copied or posted on any network computer or broadcast in any media and will not be otherwise resold or transferred for

commercial purposes; and (3) no modifications are made to this specification. This limited permission automatically terminates

without notice if you breach any of these terms or conditions. Upon termination, you will destroy immediately any copies of the

specifications in your possession or control.

PATENTS

The attention of adopters is directed to the possibility that compliance with or adoption of OMG specifications may require use of

an invention covered by patent rights. OMG shall not be responsible for identifying patents for which a license may be required by

any OMG specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its

attention. OMG specifications are prospective and advisory only. Prospective users are responsible for protecting themselves

against liability for infringement of patents.

GENERAL USE RESTRICTIONS

Any unauthorized use of this specification may violate copyright laws, trademark laws, and communications regulations and

covered by copyright herein may be reproduced or used in any form or by any means--graphic, electronic, or mechanical,

including photocopying, recording, taping, or information storage and retrieval systems--without permission of the copyright

owner.

DISCLAIMER OF WARRANTY

WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN

ERRORS OR MISPRINTS. THE OBJECT MANAGEMENT GROUP AND THE COMPANIES LISTED ABOVE MAKE

NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING

BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF

MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT

SHALL THE OBJECT MANAGEMENT GROUP OR ANY OF THE COMPANIES LISTED ABOVE BE LIABLE FOR

ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL,

RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY

ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF

THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The entire risk as to the quality and performance of software developed using this specification is borne by you. This

disclaimer of warranty constitutes an essential part of the license granted to you to use this specification.

RESTRICTED RIGHTS LEGEND

Use, duplication or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c) (1) (ii) of The

Rights in Technical Data and Computer Software Clause at DFARS 252.227-7013 or in subparagraph (c)(1) and (2) of the

Commercial Computer Software - Restricted Rights clauses at 48 C.F.R. 52.227-19 or as specified in 48 C.F.R. 227-7202-2 of

the DoD F.A.R. Supplement and its successors, or as specified in 48 C.F.R. 12.212 of the Federal Acquisition Regulations and

its successors, as applicable. The specification copyright owners are as indicated above and may be contacted through the

Object Management Group, 109 Highland Avenue, Needham, MA 02494, U.S.A.

TRADEMARKS

IMM®, MDA®, Model Driven Architecture®, UML®, UML Cube logo®, OMG Logo®, CORBA® and XMI® are

registered trademarks of the Object Management Group, Inc., and Object Management Group™, OMG™ , Unified Modeling

Language™, Model Driven Architecture Logo™, Model Driven Architecture Diagram™, CORBA logos™, XMI Logo™,

CWM™, CWM Logo™, IIOP™ , MOF™ and OMG Interface Definition Language (IDL)™ are trademarks of the Object

Management Group. All other products or company names mentioned are used for identification purposes only, and may be

trademarks of their respective owners.

COMPLIANCE

The copyright holders listed above acknowledge that the Object Management Group (acting itself or through its designees) is

and shall at all times be the sole entity that may authorize developers, suppliers and sellers of computer software to use

certification marks, trademarks or other special designations to indicate compliance with these materials.

Software developed under the terms of this license may claim compliance or conformance with this specification if and only if

the software compliance is of a nature fully matching the applicable compliance points as stated in the specification. Software

developed only partially matching the applicable compliance points may claim only that the software was based on this

specification, but may not claim compliance or conformance with this specification. In the event that testing suites are

implemented or approved by Object Management Group, Inc., software developed using this specification may claim

compliance or conformance with the specification only if the software satisfactorily completes the testing suites.

Ontology Definition Metamodel (ODM), v1.1 i

Table of Contents

Preface ................................................................................................................ ix

1 Scope ...............................................................................................................1

2 Conformance ................................................................................................... 2

3 Normative References .....................................................................................3

4 Terms and Definitions ...................................................................................... 5

5 Symbols ...........................................................................................................8

6 Additional Information ...................................................................................... 9

6.1 Changes to Adopted OMG Specifications ..........................................................9

6.2 How to Read This Specification ........................................................................10

6.3 Proof of Concept ...............................................................................................10

6.4 Acknowledgments .............................................................................................11

7 Usage Scenarios and Goals ..........................................................................13

7.1 Introduction .......................................................................................................13

7.2 Perspectives .....................................................................................................13

7.2.1 Model-Centric Perspectives .......................................................................................... 14

7.2.2 Application-Centric Perspectives .................................................................................. 15

7.3 Usage Scenarios ...............................................................................................16

7.4 Business Applications .......................................................................................17

7.4.1 Run Time Interoperation ............................................................................................... 17

7.4.2 Application Generation ................................................................................................. 18

7.4.3 Ontology Lifecycle ........................................................................................................ 19

7.5 Analytic Applications .........................................................................................20

7.5.1 Emergent Property Discovery ....................................................................................... 20

7.5.2 Exchange of Complex Data Sets .................................................................................. 20

7.6 Engineering Applications ..................................................................................21

7.6.1 Information Systems Development ............................................................................... 21

7.6.2 Ontology Engineering ................................................................................................... 21

7.7 Goals for Generic Ontologies and Tools ...........................................................22

8 Design Principles ...........................................................................................25

剩余361页未读，继续阅读

三断笛

粉丝: 62
资源: 38

会员权益专享

OMG 本体定义元模型 V1.1 英文版

评论0

会员权益专享

最新资源

OMG 本体定义元模型 V1.1 英文版

评论0

发布订阅协议v1.1（DDS）

The OMG SysML™ v1.1

OMG 统一建模语言（UML） V2.51 英文版

OMG 系统建模语言 (OMG SysML™) 1.6.pdf 英文版

OMG“元对象机制”详细解读，英文原版

mda-模型驱动体系结构_PPT

有没系统介绍MDA的MOF资料？

最新版 OMG 可执行uml 标准 fUML VER 1.3

isa-sp95标准内容

the import org.omg cannot be resolved

Overview of the OMG Data Distribution Service

OpenDDS_V3.12最新中文版

MBSE实践之建模语言SysML

使用SysML进行需求建模

SysML实践指南第二版第五章SysML语言框架

UML与形式化建模方法 PDF电子书

CORBA NotificationService

springboot整合flowable教程

会员权益专享

最新资源