Return to Core27_Capabilities.mof CVS log

Up to [Pegasus] / pegasus / Schemas / CIMPrelim271

PEP#: 215
TITLE: Remove old schemas

DESCRIPTION:

Removing old, unneeded schema files from the repository:

CIM 2.7
CIM 2.7.1 Preliminary
CIM 2.8 Preliminary
CIM 2.9 Preliminary

// ===================================================================
// Title:       Core Capabilities 2.7
// Filename:    Core27_Capabilities.mof
// Version:     2.7.0
// Release:     Preliminary 
// Date:        07/01/02
// ===================================================================
// Copyright 2002 Distributed Management Task Force, Inc. (DMTF).
// All rights reserved.  
// DMTF is a not-for-profit association of industry members dedicated 
// to promoting enterprise and systems management and interoperability. 
// DMTF specifications and documents may be reproduced for uses
// consistent with this purpose by members and non-members, 
// provided that correct attribution is given. 
// As DMTF specifications may be revised from time to time, 
// the particular version and release date should always be noted.
//
// Implementation of certain elements of this standard or proposed 
// standard may be subject to third party patent rights, including 
// provisional patent rights (herein "patent rights"). DMTF makes 
// no representations to users of the standard as to the existence 
// of such rights, and is not responsible to recognize, disclose, or
// identify any or all such third party patent right, owners or 
// claimants, nor for any incomplete or inaccurate identification or 
// disclosure of such rights, owners or claimants. DMTF shall have no 
// liability to any party, in any manner or circumstance, under any 
// legal theory whatsoever, for failure to recognize, disclose, or 
// identify any such third party patent rights, or for such party's
// reliance on the standard or incorporation thereof in its product, 
// protocols or testing procedures. DMTF shall have no liability to 
// any party implementing such standard, whether such implementation 
// is foreseeable or not, nor to any patent owner or claimant, and shall 
// have no liability or responsibility for costs or losses incurred if 
// a standard is withdrawn or modified after publication, and shall be
// indemnified and held harmless by any party implementing the 
// standard from any and all claims of infringement by a patent owner 
// for such implementations.
//
// For information about patents held by third-parties which have 
// notified the DMTF that, in their opinion, such patent may relate to 
// or impact implementations of DMTF standards, visit 
// http://www.dmtf.org/about/policies/disclosures.php.
// ===================================================================
// Description: The Core Model defines basic management concepts. 
//              This file defines the management concepts related 
//              to the Capabilities of a ManagedElement.
//
//              The object classes below are listed in an order that
//              avoids forward references. Required objects, defined 
//              by other working groups, are omitted.
// ==================================================================
// Change Log for v2.7
// CR 730 - Introduce Capabilites and ElementCapabilities
// ==================================================================

#pragma locale ("en_US")


// ==================================================================
// Capabilities
// ================================================================== 
[Abstract, Experimental, Version ("2.7.0"), Description ( 
    "Capabilities is an abstract class whose subclasses "
    "describe abilities and/or potential for use. For "
    "example, one may describe the maximum number of VLANs that "
    "can be supported on a system using a subclass of "
    "Capabilities. Capabilities are tied to the elements "
    "which they describe using the ElementCapabilities "
    "association. Note that the cardinality of the ManagedElement "
    "reference is Min(1), Max(1). This cardinality mandates the "
    "instantiation of the ElementCapabilities association for the "
    "referenced instance of Capabilities.  ElementCapabilities "
    "describes the existence requirements and context for the "
    "referenced instance of ManagedElement.  Specifically, the "
    "ManagedElement MUST exist and provides the context for the "
    "Capabilities.  Note that Capabilities do not indicate "
    "what IS configured or operational, but what CAN or CANNOT "
    "exist, be defined or be used. Note that it is possible to "
    "describe both supported and excluded abilities and functions "
    "(both capabilities and limitations) using this class.") ]
class CIM_Capabilities : CIM_ManagedElement { 

    [Key, Description (
        "InstanceID opaquely identifies a unique instance of "
        "Capabilities.  The InstanceID must be unique within a "
        "namespace. In order to ensure uniqueness, the value of "
        "InstanceID SHOULD be constructed in the following manner: \n"
        "<Vendor ID><ID> \n"
        "   <Vendor ID> MUST include a copyrighted, trademarked "
        "or otherwise unique name that is owned by the business "
        "entity or a registered ID that is assigned to the business "
        "entity that is defining the InstanceID. (This is similar to "
        "the <Schema Name>_<Class Name> structure of Schema class "
        "names.) The purpose of <Vendor ID> is to ensure that <ID> "
        "is truly unique across multiple vendor implementations. "
        "If such a name is not used, the defining entity MUST assure "
        "that the <ID> portion of the Instance ID is unique when "
        "compared with other instance providers. For DMTF defined "
        "instances, the <Vendor ID> is 'CIM'. \n"
        "   <ID> MUST include a vendor specified unique "
        "identifier.") ]        
    string InstanceID;
    
    [Override ("ElementName"), Required, Description (
        "The user friendly name for this instance of Capabilities. "
        "In addition, the user friendly name can be used as a "
        "index property for a search of query.  (Note:  Name "
        "does not have to be unique within a namespace.)") ]
    string ElementName;
};
 
 
// ===================================================================
// ElementCapabilities
// ===================================================================
[Association, Experimental, Version ("2.7.0"), Description (
    "ElementCapabilities represents the association between "
    "ManagedElements and their Capabilities.  "
    "Note that the cardinality of the ManagedElement "
    "reference is Min(1), Max(1). This cardinality mandates the "
    "instantiation of the ElementCapabilities association for the "
    "referenced instance of Capabilities.  ElementCapabilities "
    "describes the existence requirements and context for the "
    "referenced instance of ManagedElement.  Specifically, the "
    "ManagedElement MUST exist and provides the context for the "
    "Capabilities.") ]
class CIM_ElementCapabilities {
    
    [Key, Min(1), Max(1), Description (
        "The managed element.") ]
    CIM_ManagedElement REF ManagedElement;
    
    [Key, Description (
        "The Capabilities object associated with the element.") ]
    CIM_Capabilities REF Capabilities;
};


// ===================================================================
// end of file
// ===================================================================