DOCSLIB.ORG

Common Information Model (CIM) Infrastructure

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Common Information Model (CIM) Infrastructure 1 2 Document Number: DSP0004 3 Date: 2008-05-23 4 Version: 2.5.0a 5 Common Information Model (CIM) Infrastructure 6 Document Type: Specification 7 Document Status: Preliminary 8 Document Language: E 9 Common Information Model (CIM) Infrastructure DSP0004 10 Copyright notice 11 Copyright © 2008 Distributed Management Task Force, Inc. (DMTF). All rights reserved. 12 DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems 13 management and interoperability. Members and non-members may reproduce DMTF specifications and 14 documents for uses consistent with this purpose, provided that correct attribution is given. As DMTF 15 specifications may be revised from time to time, the particular version and release date should always be 16 noted. 17 Implementation of certain elements of this standard or proposed standard may be subject to third party 18 patent rights, including provisional patent rights (herein "patent rights"). DMTF makes no representations 19 to users of the standard as to the existence of such rights, and is not responsible to recognize, disclose, 20 or identify any or all such third party patent right, owners or claimants, nor for any incomplete or 21 inaccurate identification or disclosure of such rights, owners or claimants. DMTF shall have no liability to 22 any party, in any manner or circumstance, under any legal theory whatsoever, for failure to recognize, 23 disclose, or identify any such third party patent rights, or for such party’s reliance on the standard or 24 incorporation thereof in its product, protocols or testing procedures. DMTF shall have no liability to any 25 party implementing such standard, whether such implementation is foreseeable or not, nor to any patent 26 owner or claimant, and shall have no liability or responsibility for costs or losses incurred if a standard is 27 withdrawn or modified after publication, and shall be indemnified and held harmless by any party 28 implementing the standard from any and all claims of infringement by a patent owner for such 29 implementations. 2 Version 2.5.0a DSP0004 Common Information Model (CIM) Infrastructure 30 CONTENTS 31 1 Scope .................................................................................................................................................... 9 32 2 Normative References........................................................................................................................... 9 33 2.1 Approved References ............................................................................................................... 10 34 2.2 References under Development ............................................................................................... 10 35 2.3 Other References...................................................................................................................... 11 36 3 Terms and Definitions.......................................................................................................................... 11 37 3.1 Keywords .................................................................................................................................. 11 38 3.2 Terms........................................................................................................................................ 11 39 4 Symbols and Abbreviated Terms......................................................................................................... 15 40 5 Meta Schema ...................................................................................................................................... 16 41 5.1 Definition of the Meta Schema.................................................................................................. 17 42 5.2 Data Types................................................................................................................................ 22 43 5.3 Supported Schema Modifications ............................................................................................. 28 44 5.4 Class Names............................................................................................................................. 29 45 5.5 Qualifiers................................................................................................................................... 30 46 6 Managed Object Format...................................................................................................................... 55 47 6.1 MOF Usage............................................................................................................................... 56 48 6.2 Class Declarations.................................................................................................................... 56 49 6.3 Instance Declarations ............................................................................................................... 56 50 7 MOF Components ............................................................................................................................... 56 51 7.1 Keywords .................................................................................................................................. 56 52 7.2 Comments................................................................................................................................. 56 53 7.3 Validation Context..................................................................................................................... 57 54 7.4 Naming of Schema Elements ................................................................................................... 57 55 7.5 Class Declarations.................................................................................................................... 57 56 7.6 Association Declarations .......................................................................................................... 62 57 7.7 Qualifier Declarations................................................................................................................ 64 58 7.8 Instance Declarations ............................................................................................................... 65 59 7.9 Method Declarations................................................................................................................. 68 60 7.10 Compiler Directives................................................................................................................... 69 61 7.11 Value Constants........................................................................................................................ 69 62 7.12 Initializers .................................................................................................................................. 71 63 8 Naming ................................................................................................................................................ 72 64 8.1 Background............................................................................................................................... 73 65 8.2 Weak Associations: Supporting Key Propagation .................................................................... 76 66 8.3 Naming CIM Objects................................................................................................................. 77 67 9 Mapping Existing Models into CIM...................................................................................................... 81 68 9.1 Technique Mapping .................................................................................................................. 81 69 9.2 Recast Mapping........................................................................................................................ 82 70 9.3 Domain Mapping....................................................................................................................... 84 71 9.4 Mapping Scratch Pads.............................................................................................................. 85 72 10 Repository Perspective ....................................................................................................................... 85 73 10.1 DMTF MIF Mapping Strategies................................................................................................. 86 74 10.2 Recording Mapping Decisions .................................................................................................. 87 75 ANNEX A (normative) MOF Syntax Grammar Description........................................................................ 90 76 ANNEX B (informative) CIM Meta Schema ............................................................................................... 95 77 ANNEX C (normative) Units..................................................................................................................... 102 78 C.1 Programmatic Units ................................................................................................................ 102 79 C.2 Value for Units Qualifier.......................................................................................................... 107 80 ANNEX D (informative) UML Notation..................................................................................................... 109 Version 2.5.0a 3 Common Information Model (CIM) Infrastructure DSP0004 81 ANNEX E (normative) Unicode Usage ...................................................................................................
Load more

Recommended publications
  • American National Dictionary for Information Processing
    NAT L INST OF STAND & TECH R.j^C. NIST X3/TR-1—77 PUBLICATIONS -SniDB 517103 1977 SEPTEMBER X3 TECHNICAL REPORT Adopted tor Use by the Federal Government AMERICAN NATIONAL DICTIONARY FOR INFORMATION PROCESSING FIPS 11-1 See Notice on Inside Front Cover M AMERICAN NATIONAL STANDARDS COMMITTEE X3 — COMPUTERS & INFORMATION PROCESSING JKm - ■ PRsA2> tlD II- I iq-n ab( TTTli This DICTIONARY has been adopted for Federal Government use as a basic reference document to promote a common understanding of information processing terminology. Details concerning the specific use of this DICTIONARY are contained in Federal Information Processing Standards Publication 11-1, DICTIONARY FOR INFORMATION PROCESSING For a complete list of publications avail¬ able in the FIPS Series, write to the Office of ADP Standards Management, Institute for Computer Sciences and Technology, National Bureau of Stan¬ dards, Washington, D C 20234 f-^oftH Qvlas vi StzaiiTft DEC 7 1378 X3/TR-1-77 not (\ Cc - ;<£ 1977 September SKI American National Dictionary for Information Processing American National Standards Committee X3 — Computers and Information Processing Secretariat: Computer and Business Equipment Manufacturers Association Published by Computer and Business Equipment Manufacturers Association 1828 L Street NW, Washington DC 20036 202/466-2299 Copyright © 1977 by Computer and Business Equipment Manufacturers Association All rights reserved. Permission is herby granted for quotation, with accreditation to "American National Dictionary for Information Processing, X3/TR-1-77". of up to fifty terms and their definitions. Other than such quotation, no part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher.
    [Show full text]
  • Wmlscript Specification Approved Version 04-Nov-1999
    WMLScript Specification Approved Version 04-Nov-1999 Wireless Application Protocol WMLScript Language Specification Version 1.1 Disclaimer: This document is subject to change without notice. Approved Version 04-Nov-1999 Page 2(132) 1. CONTENTS 1 . ................................................................................................................................................Scope 7 2 . ...............................................................................................................................Document Status 8 2.1 Copyright Notice..................................................................................................................... 8 2.2 Errata ..................................................................................................................................... 8 2.3 Comments .............................................................................................................................. 8 3 . ........................................................................................................................................References 9 3.1 Normative references ............................................................................................................. 9 3.2 Informative References .......................................................................................................... 9 4 . ............................................................................................................ Definitions and abbreviations 10 4.1 Definitions
    [Show full text]
  • WAP-193 101-Wmlscript-20010928
    Specification Information Note WAP-193_101-WMLS-20010928-a Version 28-Sept-2001 for Wireless Application Protocol WAP-193-WMLS-20001025-a WMLScript Specification Version 25-Oct-2000 A list of errata and updates to this document is available from the WAP Forum TM Web site, http://www.wapforum.org/, in the form of SIN documents, which are subject to revision or removal without notice. © 2001, Wireless Application Forum, Ltd. All rights reserved. Terms and conditions of use are available from the WAP ForumÔ Web site at http://www.wapforum.org/what/copyright.htm. You may use this document or any part of the document for internal or educational purposes only, provided you do not modify, edit or take out of context the information in this document in any manner. You may not use this document in any other manner without the prior written permission of the WAP Forum™. The WAP Forum authorises you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services offered by you. The WAP Forum™ assumes no responsibility for errors or omissions in this document. In no event shall the WAP Forum be liable for any special, indirect or consequential damages or any damages whatsoever arising out of or in connection with the use of this information. WAP Forum TM members have agreed to use reasonable endeavors to disclose in a timely manner to the WAP Forum the existence of all intellectual property rights (IPR’s) essential to the present document.
    [Show full text]
  • Real Time 3-D Graphics Processing Hardware Design Using Field- Programmable Gate Arrays
    REAL TIME 3-D GRAPHICS PROCESSING HARDWARE DESIGN USING FIELD- PROGRAMMABLE GATE ARRAYS. by James Ryan Warner B. S. in Computer Engineering, Pennsylvania State University, 1999 Submitted to the Graduate Faculty of Swanson School of Engineering in partial fulfillment of the requirements for the degree of Master of Science in Electrical Engineering University of Pittsburgh 2008 i UNIVERSITY OF PITTSBURGH SWANSON SCHOOL OF ENGINEERING This thesis was presented by James Ryan Warner It was defended on September 18, 2008 and approved by Dr. Alexander Jones, Assistant Professor, Department of Electrical and Computer Engineering Dr. Allen Cheng, Assistant Professor, Department of Electrical and Computer Engineering Thesis Advisor: Dr. James T. Cain, Professor Emeritus, Department of Electrical and Computer Engineering ii Copyright © by James Ryan Warner 2008 iii REAL TIME 3-D GRAPHICS PROCESSING HARDWARE DESIGN USING FIELD- PROGRAMMABLE GATE ARRAYS James Ryan Warner, M.S. University of Pittsburgh, 2008 Three dimensional graphics processing requires many complex algebraic and matrix based operations to be performed in real-time. In early stages of graphics processing, such tasks were delegated to a Central Processing Unit (CPU). Over time as more complex graphics rendering was demanded, CPU solutions became inadequate. To meet this demand, custom hardware solutions that take advantage of pipelining and massive parallelism become more preferable to CPU software based solutions. This fact has lead to the many custom hardware solutions that are available today. Since real time graphics processing requires extreme high performance, hardware solutions using Application Specific Integrated Circuits (ASICs) are the standard within the industry. While ASICs are a more than adequate solution for implementing high performance custom hardware, the design, implementation and testing of ASIC based designs are becoming cost prohibitive due to the massive up front verification effort needed as well as the cost of fixing design defects.
    [Show full text]
  • Bits, Data Types, and Operations What Does the Computer Understand?
    Computer Programming Programming Language • Is telling the computer how to do something • Wikipedia Definition: Applies specific programming languages to solve specific computational problems with solutions Bits, Data Types, and Operations High-level Programming Language • A programming language with strong abstraction from the details of the computer Isolates the execution semantics of a computer architecture comparedtd to assem bl/lbly/low-lllevel • Advantage: Makes the process of developing a program simpler Based on slides © McGraw-Hill and more understandable Additional material © 2004/2005 Lewis/Martin Edited by Diana Palsetia What does the Computer Understand? What does the Computer process & store? At the lowest level, a computer has electronic “plumbing” An electronic device can represent uniquely only one Operates by controlling the flow of electrons through very fast of two things tiny electronic devices called transistors Each “0” and Each “1” is referred to as a Binary Digit or Bit Fundament unit of information storage The devices react to presence or absence of voltage To represent more things we need more bits Could react actual voltages but designing electronics then becomes complex E.g. 2 bits can represent four unique things: 00, 01, 10, 11 k bits can distinguish 2k distinct items Symbolically we represent Combination binary bits together can represent some 1. Presence of voltage as “1” information or data. E.g. 01000001 can be 2. Absence of voltage as “0” 1. Decimal value 65 2. Alphabet (or character) ‘A’ in
    [Show full text]
  • Demonstrate an Understanding of the Handling of Error in a Computer Programming Environment 115359
    DEMONSTRATE AN UNDERSTANDING OF THE HANDLING OF ERROR IN A COMPUTER PROGRAMMING ENVIRONMENT 115359 PURPOSE OF THE UNIT STANDARD This unit standard is designed to provide credits towards the mathematical literacy requirements of the NQF at level 4. The essential purposes of the mathematical literacy requirements are that, as the learner progresses with confidence through the levels, the learner will grow in: An insightful use of mathematics in the management of the needs of everyday living to become a self-managing person. An understanding of mathematical applications that provide insight into the learner's present and future occupational experiences and so develop into a contributing worker. The ability to voice a critical sensitivity to the role of mathematics in a democratic society and so become a participating citizen. Qualifying learners are able to: Explain different errors found in the computer programming environment , and differentiate it from mistakes. Demonstrate how calculation errors are induced in the computer. Demonstrate how computer errors can be minimised. The performance of all elements is to a standard that allows for further learning in this area. LEARNING ASSUMED TO BE IN PLACE AND RECOGNITION OF PRIOR LEARNING The credit value is based on the assumption that people starting to learn towards this unit standard are: Competent in Mathematical Literacy and Communications at NQF level 3. Competent in demonstrating an understanding of the use of different number bases and measurement units and an awareness of error in the context of relevant calculations (SAQA ID = 9010). UNIT STANDARD RANGE This unit standard covers: Approximation in relation to the use of computing technologies, the distinction between exact and approximate answers in a variety of problem settings.
    [Show full text]
  • CIMM::Arrayvalue
    1 2 Document Number: DSP0004 3 Date: 2012-05-29 4 Version: 3.0.0b 5 6 Common Information Model (CIM) Metamodel THIS DOCUMENT IS A WORK IN PROGRESS VERSION. This document is subject to change at any time without further notice. It expires on: 10/30/2012 Provide any comments through the DMTF Feedback Portal: http://www.dmtf.org/standards/feedback IMPORTANT: This specification is not a standard. It does not necessarily reflect the views of the DMTF or all of its members. Because this document is a Work in Progress, this specification may still change, perhaps profoundly. This document is available for public review and comment until the stated expiration date. 7 Document Type: Specification Document Status: Work In Progress Specification Document Language: US-EN DMTF Confidential Common Information Model (CIM) Metamodel DSP0004 Copyright Notice 8 9 DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems 10 management and interoperability. Members and non-members may reproduce DMTF specifications and 11 documents, provided that correct attribution is given. As DMTF specifications may be revised from time to 12 time, the particular version and release date should always be noted. 13 Implementation of certain elements of this standard or proposed standard may be subject to third party 14 patent rights, including provisional patent rights (herein "patent rights"). DMTF makes no representations 15 to users of the standard as to the existence of such rights, and is not responsible to recognize, disclose, 16 or identify any or all such third party patent right, owners or claimants, nor for any incomplete or 17 inaccurate identification or disclosure of such rights, owners or claimants.
    [Show full text]