(file) Return to CIM_ConcreteDependency.mof CVS log (file) (dir) Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Core

File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Core / CIM_ConcreteDependency.mof (download)
Revision: 1.1.2.2, Wed Feb 15 17:46:13 2012 UTC (12 years, 4 months ago) by karl
Branch: TASK-PEP317_pullop-branch
CVS Tags: TASK_PEP317_1JUNE_2013, TASK-PEP317_pullop-merged_out_to_branch, TASK-PEP317_pullop-merged_in_from_branch, PREAUG25UPDATE, POSTAUG25UPDATE
Changes since 1.1.2.1: +45 -0 lines
BUG#: 99999
TITLE: Task317 Branch -- pull operations. Sync to head of tree

DESCRIPTION: Sync the branch back to the head of cvs tree

// Copyright (c) 2005 DMTF.  All rights reserved.
// <change cr="SysDevCR00711.001" type ="change">Update of
// descriptions based on Tech Edit review.</change>
// <change cr="ArchCR00066.004" type="add">Add UmlPackagePath
// qualifier values to CIM Schema.</change>
// ==================================================================
//  CIM_ConcreteDependency
// ==================================================================
   [Association, Version ( "2.10.0" ), 
    UMLPackagePath ( "CIM::Core::CoreElements" ), 
    Description ( 
       "CIM_ConcreteDependency is a generic association used to "
       "establish dependency relationships between ManagedElements. It "
       "is defined as a concrete subclass of the abstract "
       "CIM_Dependency class, to be used in place of many specific "
       "subclasses of Dependency that add no semantics, that is "
       "subclasses that do not clarify the type of dependency, update "
       "cardinalities, or add or remove qualifiers. Note that when you "
       "define additional semantics for Dependency, this class must "
       "not be subclassed. Specific semantics continue to be defined "
       "as subclasses of the abstract CIM_Dependency. "
       "ConcreteDependency is limited in its use as a concrete form of "
       "a general dependency. \n"
       "\n"
       "It was deemed more prudent to create this concrete subclass "
       "than to change Dependency from an abstract to a concrete "
       "class. Dependency already had multiple abstract subclasses in "
       "the CIM Schema, and wider industry usage and impact could not "
       "be anticipated." )]
class CIM_ConcreteDependency : CIM_Dependency {

      [Override ( "Antecedent" ), 
       Description ( 
          "Antecedent represents the independent object in this association."
           )]
   CIM_ManagedElement REF Antecedent;

      [Override ( "Dependent" ), 
       Description ( 
          "Dependent represents the object that is dependent on the "
          "Antecedent." )]
   CIM_ManagedElement REF Dependent;


};

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2