Internet-Draft                                                Ryan Moats
draft-moats-dmtf-application-ldap-00.txt
draft-moats-dmtf-application-ldap-01.txt                Gerald Maziarski
Expires in six months                                               AT&T
                                                          John Strassner
                                                           cisco Systems
                                                            October
                                                           December 1999

          LDAP Schema for the DMTF Application CIM v2.1 Model
           Filename: draft-moats-dmtf-application-ldap-00.txt draft-moats-dmtf-application-ldap-01.txt

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

Abstract

   This draft presents a LDAP schema for the DMTF CIM Application model
   version 2.2 [4].

1. Introduction

   This draft presents a LDAPv3 [1,2] schema for the DMTF CIM
   Application model.  Associations are mapped using a combination of
   auxiliary classes and DIT structure rules.  Where auxiliary classes
   are used, name form and DIT content rules are specified.

2. Differences between this schema

   This document is not a product of the DMTF, and represents the source view
   of the authors.

INTERNET DRAFTLDAP Schema for the DMTF Application CIM model v2.1
ModelDecember 1999

2. Modifications to cimAssociationInstance

   The only issue in core mapping this model [5] defined cimAssociationInstance as a helper
   class.  To support the auxiliary classes, the following classes
   should be added to LDAP is that there is an
   attribute definition collision between this model and cimAssociationInstance's content rule:

      cim22DirectorySpecificationFileAuxClass
      cim22ActionSequenceAuxClass
      cim22SoftwareFeatureSoftwareElementsAuxClass
      cim22ToDirectorySpecificationAuxClass
      cim22FromDirectorySpecificationAuxClass
      cim22ToDirectoryActionAuxClass
      cim22FromDirectoryActionAuxClass
      cim22SoftwareFeatureSAPImplementationAuxClass
      cim22ApplicationSystemSoftwareFeatureAuxClass
      cim22InstalledSoftwareElementAuxClass

   Also, the system
   model.  The attribute codeSet is following structure rules defined with different syntax in
   both models, so codeSet in this model has been renamed codeSetString. here need to be added to
   the structure rule for cimAssociationInstance:  <sr25>, <sr26>,
   <sr27>, <sr28>,

3. Class Definitions

   For efficiency in the LDAP representation, associations are specified
   as a combination of auxiliary classes and DIT structure rules.
   Attribute definitions for each class are presented with the object
   class.  Other definitions are also provided when necessary.

   This approach minimizes the number of DN pointers stored in the
   schema, but some pointer dereferencing is necessary.  While not
   explicitly stated in the definitions below, we assume that all
   attributes with DN support the matching rule defined in [3].
   Attribute names for DN pointers also follow the convention that a
   single pointer's name ends in "Ref", while an array of pointers' name
   ends in "Refs".

   Note: all attribute, object class, and name form OIDs are place
   holders, and syntax OIDs in definitions have been replaced by names
   for clarity.

3.1 dmtfApplicationSystem cim22ApplicationSystem

   This class represents an application or a software system that
   supports a particular business function and that can be managed as
   independent units. The dmtfSoftwareFeature cim22SoftwareFeature class allows such a
   system to be decomposed into its functional pieces.  The software
   features for a particular application or software system are located
   using
   dmtfApplicationSystemSoftwareFeatureAuxClass. cim22ApplicationSystemSoftwareFeatureAuxClass.

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

      ( <oid-oc231> <oid-oc96> NAME 'dmtfApplicationSystem' 'cim22ApplicationSystem'
        DESC 'represents 'The cim22ApplicationSystem class is used to represent an
              application or a software system that supports a particular
              business function and that can be managed as an independent units.'
              units. Such a system can be decomposed into its functional
              components using the cim22SoftwareFeature class. The
              software features for a particular application or software
              system are located using the
              cim22ApplicationSystemSoftwareFeature association.'
        SUP dmtfSystem cim22System
      )

   The following content rule specifies the auxiliary classes that may
   be attached to cim22ApplicationSystem.

      ( <oid-oc96> NAME 'cim22ApplicationSystemContentRule'
        DESC 'The auxiliary classes that may be attached to
              cim22ApplicationSystem'
        AUX (cim22ApplicationSystemSoftwareFeatureAuxClass)
      )

3.2 dmtfSoftwareElement cim22SoftwareElement

   This class decomposes a dmtfSoftwareFeature cim22SoftwareFeature object into a set of
   individually manageable or deployable parts for a particular
   platform. A software element's underlying hardware architecture and
   operating system uniquely identifies its platform.  As such, to
   understand the details of how the functionality of a particular
   software feature is provided on a particular platform, the
   dmtfSoftwareElement
   cim22SoftwareElement objects referenced by
   dmtfSoftwareFeatureSoftwareElementAuxClass
   cim22SoftwareFeatureSoftwareElementAuxClass are organized in disjoint
   sets based on the targetOperatingSystem property. A
   dmtfSoftwareElement
   cim22SoftwareElement object captures the management details of a part
   or component in one of four states characterized by the
   SoftwareElementState property.

      ( <oid-at552> <oid-at171> NAME 'softwareElementState' 'cimSoftwareElementState'
        DESC ' The SoftwareElementState is defined in this model to
               identify various states of a software elements life
               cycle. - A software element in the deployable state
               describes the details necessary to successful distribute
               it and the details (conditions and actions) required to
               create a software element in the installable state (i.e,
               the next state). - A software element in the installable
               state describes the details necessary to successfully
               install it and the details (conditions and actions
               required to create a software element in the executable
               state (i.e., the next state). - A software element in the

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

               executable state describes the details necessary to
               successfully start it and the details (conditions and
               actions required to create a software element in the
               running state (i.e., the next state). - A software element
               in the running state describes the details necessary to
               monitor and operate on a start element.  May be used as an
               RDN.  Allowed values are: "Deployable", "Installable",
               "Executable", "Running".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at553> <oid-at172> NAME 'softwareElementID' 'cimSoftwareElementID'
        DESC ' This is an identifier for this software element and is
               designed to be used with other keys to
               create a unique representation of this SoftwareElement.
               May be used as an RDN.'
        SYNTAX string{256} SINGLE-VALUE
      )

      ( <oid-at554> <oid-at173> NAME 'targetOperatingSystem' 'cimTargetOperatingSystem'
        DESC ' The Target Operating System property allows the provider
               to specify the operating system environment. The value of
               this property does not ensure binary executable. Two other
               pieces of information are needed. First, the version of
               the OS needs to be specified. using the OS Version
               Check. The second piece of information is the architecture
               the OS runs on. This information is capture with the
               ArchitectureCheck class. The combination of these
               constructs allows the provider to clearly identify the
               level of OS required for a particular software element.
               May be used as an RDN.  Allowed values are: "Unknown",
               "Other", "MACOS", "ATTUNIX", "DGUX", "DECNT", "Digital
               Unix", "OpenVMS", "HPUX", "AIX", "MVS", "OS400", "OS/2",
               "JavaVM", "MSDOS", "WIN3x", "WIN95", "WIN98", "WINNT",
               "WINCE", "NCR3000", "NetWare", "OSF", "DC/OS", "Reliant
               UNIX", "SCO UnixWare", "SCO OpenServer", "Sequent",
               "IRIX", "Solaris", "SunOS", "U6000", "ASERIES",
               "TandemNSK", "TandemNT", "BS2000", "LINUX", "Lynx",
               "XENIX", "VM/ESA", "Interactive UNIX", "BSDUNIX",
               "FreeBSD", "NetBSD", "GNU Hurd", "OS9", "MACH Kernel",
               "Inferno", "QNX", "EPOC", "IxWorks", "VxWorks", "MiNT",
               "BeOS", "HP MPE", "NextStep", "PalmPilot", "Rhapsody".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at555> <oid-at174> NAME 'otherTargetOS' 'cimOtherTargetOS'
        DESC ' The otherTargetOS property records the manufacturer and
               operating system type for a software element when the

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

               targetOperatingSystem property has a value of 1 ("Other")
               For all other values of TargetOperatingSystem, the
               OtherTargetOS property is to be NULL.'
        SYNTAX string{64} SINGLE-VALUE
      )

      ( <oid-at556> <oid-at175> NAME 'buildNumber' 'cimBuildNumber'
        DESC 'The internal identifier for this compilation of this
              software element.'
        SYNTAX string{64} SINGLE-VALUE
      )

      ( <oid-at442> <oid-at176> NAME 'codeSetString' 'cimCodeSet'
        DESC 'Array defining the character sets'
        SYNTAX string{64} SINGLE-VALUE
      )

      ( <oid-at557> <oid-at177> NAME 'identificationCode' 'cimIdentificationCode'
        DESC ' The value of this property is the manufacturer's
               identifier for this software element. Often this will be a
               stock keeping unit (SKU) or a part number.'
        SYNTAX string{64} SINGLE-VALUE
      )

      ( <oid-at558> <oid-at178> NAME 'languageEdition' 'cimLanguageEdition'
        DESC 'The value of this property identifies the language edition
              of this software element. The language codes defined in ISO
              639 should be used. Where the software element represents
              multi-lingual or international version of a product, the
              string multilingual should be used.'
        SYNTAX string{32} SINGLE-VALUE
      )

      ( <oid-oc232> <oid-oc97> NAME 'dmtfSoftwareElement' 'cim22SoftwareElement'
        DESC 'decomposes 'The cim22SoftwareElement class is used to decompose a dmtfSoftwareFeature
              cim22SoftwareFeature object into a set of individually
              manageable or deployable parts for a particular platform.' platform. A
              software element's platform is uniquely identified by its
              underlying hardware architecture and operating system (for
              example Sun Solaris on Sun Sparc or Windows NT on
              Intel). As such, to understand the details of how the
              functionality of a particular software feature is provided
              on a particular platform, the cim22SoftwareElement objects
              referenced by cim22SoftwareFeatureSoftwareElement
              associations are organized in disjoint sets based on the
              TargetOperatingSystem property. A cim22SoftwareElement
              object captures the management details of a part or
              component in one of four states characterized by the

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

              SoftwareElementState property.'
        SUP dmtfLogicalElement
        MUST (name cim22LogicalElement
        MAY (cimName $ version cimVersion $ softwareElementState cimSoftwareElementState $ softwareElementID
             cimSoftwareElementID $
           targetOperatingSystem cimTargetOperatingSystem $ otherTargetOS
             cimOtherTargetOS $ manufacturer cimManufacturer $ cimBuildNumber $
             cimSerialNumber $ cimCodeSet $ cimIdentificationCode $
             cimLanguageEdition)
      )

      ( <oid-nf27> NAME 'cim22SoftwareElementNameForm'
        OC cim22SoftwareElement
        MUST (orderedCimModelPath)
      )

      ( <sr27> NAME 'cim22SoftwareElementStructureRule'
        FORM cim22SoftwareElementNameForm
      )

   The following content rule specifies the auxiliary classes that may
   be attached to cim22SoftwareElement.

      ( <oid-oc97> NAME 'cim22SoftwareElementContentRule'
        DESC 'The auxiliary classes that may be attached to
              cim22SoftwareElement'
        AUX (cim22SoftwareFeatureSoftwareElementsAuxClass $
             cim22InstalledSoftwareElementAuxClass $
             cim22LogicalIdentityAuxClass $ cim22CollectedMSEsAuxClass $
           buildNumber
             cim22ElementConfigurationAuxClass $ serialNumber
             cim22ElementSettingAuxClass $ codeSetString cim22DependencyAuxClass $ identificationCode
             cim22ProvidesServiceToElementAuxClass $
           languageEdition)
             cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
      )

3.3 dmtfSoftwareFeature cim22SoftwareFeature

   This class defines a particular function or capability of a product
   or application system. It captures the level of granularity that is
   significant to a consumer or user of a product rather than the units
   that reflect how the product is built or packaged, which is captured
   using the dmtfSoftwareElement cim22SoftwareElement class. When a software feature can
   exist on multiple platforms or operating systems (for example, a
   client component of a three tiered client/server applications might
   run on Solaris, Windows NT, and Windows 95), a software feature is a
   collection of all the software elements for these different
   platforms. Here, the users of the model must be aware of this since
   typically they will be interested in a sub-collection of the software
   elements required for a particular platform. Software Features are
   always defined in the context of a dmtfProduct cim22Product class using DIT

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

   structure rules since features are delivered through products.
   Optionally, software features from one or more products can be
   organized into application systems using the
   dmtfApplicationSystemSoftwareFeatureAuxClass
   cim22ApplicationSystemSoftwareFeatureAuxClass object.  it reuses
   identifyingNumber, vendor, version, and name and defines productName.

      ( <oid-at559> <oid-at179> NAME 'productName' 'cimProductName'
        DESC 'Commonly used Product name.  May be used as an RDN.' name'
        SYNTAX string{256} string SINGLE-VALUE
      )

      ( <oid-oc233> <oid-oc98> NAME 'dmtfSoftwareFeature' 'cim22SoftwareFeature'
        DESC 'defines 'The cim22SoftwareFeature class defines a particular function
              or capability of a product or application system.'
        SUP dmtfLogicalElement
        MUST (identifyingNumber $ productName $ vendor $ version $ name)
      )

   While system. This
              class in intended to capture the level of granularity that
              is meaningful to a variety consumer or user of attributes may a product rather
              than the units that reflect how the product is built or
              packaged. The latter detailed is captured using a
              cim22SoftwareElement class. When a software feature can
              exist on multiple platforms or operating systems (for
              example, a client component of a three tiered client/server
              applications might run on Solaris, Windows NT, and Windows
              95), a software feature is a collection of all the software
              elements for these different platforms. In this case, the
              users of the model must be used as RDN, aware of this situation since
              typically they will be interested in a sub-collection
              of the following
   structural rules software elements required for a particular
              platform. Software Features are recommended.

      ( 28 NAME 'dmtfSoftwareFeatureStructureRule1'
        FORM dmtfSoftwareFeatureNameForm1 always defined in the
              context of a cim22Product class using the
              cim22ProductSoftwareFeature association since features are
              delivered through products. Optionally, software features
              from one or more products can be organized into application
              systems using the cim22ApplicationSystemSoftwareFeature
              association.'
        SUP 30 31 cim22LogicalElement
        MUST (cimIdentifyingNumber $ cimProductName $ cimVendor $
              cimVersion)
        MAY (cimName)
      )

      ( <oid-nf28> NAME 'dmtfSoftwareFeatureNameForm1' 'cim22SoftwareFeatureNameForm'
        OC dmtfSoftwareFeature cim22SoftwareFeature
        MUST (name) (orderedCimModelPath)
      )

      ( 29 <sr28> NAME 'dmtfSoftwareFeatureStructureRule2' 'cim22SoftwareFeatureStructureRule'
        FORM dmtfSoftwareFeatureNameForm2 cim22SoftwareFeatureNameForm
        SUP 30 31
      )

      ( <oid-nf29> NAME 'dmtfSoftwareFeatureNameForm2'
        OC dmtfSoftwareFeature
        MUST (identifyingNumber)
      )

      ( 30 NAME 'dmtfProductStructureRule1'
        FORM dmtfProductNameForm1
      )

      ( <oid-nf30> NAME 'dmtfProductNameForm1'
        OC dmtfProduct
        MUST (name)
      )

      ( 31 NAME 'dmtfProductStructureRule2'
        FORM dmtfProductNameForm2 <sr6>
      )

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

   The following content rule specifies the auxiliary classes that may
   be attached to cim22SoftwareFeature.

      ( <oid-nf31> <oid-oc98> NAME 'dmtfProductNameForm2'
        OC dmtfProduct
        MUST (identifyingNumber) 'cim22SoftwareFeatureContentRule'
        DESC 'The auxiliary classes that may be attached to
              cim22SoftwareFeature'
        AUX (cim22SoftwareFeatureSoftwareElementsAuxClass $
             cim22SoftwareFeatureServiceImplementationAuxClass $
             cim22SoftwareFeatureSAPImplementationAuxClass $
             cim22ApplicationSystemSoftwareFeatureAuxClass $
             cim22LogicalIdentityAuxClass $ cim22CollectedMSEsAuxClass $
             cim22ElementConfigurationAuxClass $
             cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
             cim22ProvidesServiceToElementAuxClass $
             cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
      )

3.4 dmtfCheck cim22Check

   A Check is a condition or characteristic that is expected to be true
   in an environment defined or scoped by an instance of a
   dmtfComputerSystem.
   cim22ComputerSystem. They are associated with a particular software
   element and are organized into one of two groups using the Phase
   property.  Conditions that are expected to be satisfied when a
   software element is in a particular environment are known as in-state
   conditions. Conditions that need to be satisfied to transition the
   current software element to its next state are known as next-state
   conditions.

   it reuses name, version, softwareElementState, softwareElementID,
   targetOperatingSystem, description, and caption.  It also defines
   checkID, phase and checkMode.

      ( <oid-at560> <oid-at180> NAME 'checkID' 'cimCheckID'
        DESC 'An identifier used in conjunction with other keys to
              uniquely identify the check.  May be used as an RDN.' check'
        SYNTAX string{256} string SINGLE-VALUE
      )

      ( <oid-at561> <oid-at181> NAME 'checkMode' 'cimCheckMode'
        DESC 'The CheckMode property is used to show indicate whether the
              condition is expected to exist or not exist in the
              environment. When the value is True, the condition is
              expected to exist (e.g., a file is expected to be on a
              system) so invoke() is expected to return True. When the
              value is False, the condition is not expect to exist (e.g.,
              a file is not to be on a system) so invoke is expected to
              return false.' false'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at562> <oid-oc99> NAME 'phase'
        DESC ' The Phase property shows whether 'cim22Check'

INTERNET DRAFTLDAP Schema for the referenced check
            is an in-state check or a next-state check.  Allowed
            values are: "In-State", "Next-State".'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc234> NAME 'dmtfCheck' DMTF Application CIM v2.1
ModelDecember 1999

        DESC 'A Check is a condition or characteristic that is expected
              to be true in an environment defined or scoped by an
              instance of a dmtfComputerSystem.' cim22ComputerSystem. The checks associated
              with a particular software element are organized into one
              of two groups using the Phase property of the
              cim22SoftwareElementChecks association. Conditions that are
              expected to be satisfied when a software element is in a
              particular environment are known as in-state
              conditions. Conditions that need to be satisfied in order
              to transition the current software element to its next
              state are known as next-state conditions A
              cim22ComputerSystem object represents the environment in
              which cim22SoftwareElements are already installed or in
              which cim22SoftwareElements will be installed. For the case
              in which a software element is already installed, the
              cim22InstalledSoftwareElement association is used to
              identify the cim22ComputerSystem object that represents the
              "environment". When a software elements is being
              distributed and installed on a different computer system,
              the cim22ComputerSystem object for the targeted system is
              the environment.'
        SUP top ABSTRACT
        MUST (name (orderedCimModelPath)
        MAY (cimName $ version cimVersion $ softwareElementState cimSoftwareElementState $ softwareElementID
             cimSoftwareElementID $
           targetOperatingSystem cimTargetOperatingSystem $ checkID
             cimCheckID $ description cimDescription $ caption cimCaption $
           checkMode)
      )

   While various attributes of dmtfCheck may be used as RDNs, the
   following structural rules are recommended.

      ( 32 NAME 'dmtfCheckStructureRule1'
        FORM dmtfCheckNameForm1
        SUP 34 35 cimCheckMode)
      )

      ( <oid-nf32> <oid-nf25> NAME 'dmtfCheckNameForm1' 'cim22CheckNameForm'
        OC dmtfCheck cim22Check
        MUST (name) (orderedCimModelPath)
      )

      ( 33 <sr25> NAME 'dmtfCheckStructureRule1' 'cim22CheckStructureRule'
        FORM dmtfCheckNameForm1 cim22CheckNameForm
        SUP 34 35
      )

      ( <oid-nf33> NAME 'dmtfCheckNameForm1'
        OC dmtfCheck
        MUST (checkID)
      )

      ( 34 NAME 'dmtfSoftwareElementStructureRule1'
        FORM dmtfSoftwareElementNameForm1
      )

      ( <oid-nf34> NAME 'dmtfSoftwareElementNameForm1'
        OC dmtfSoftwareElement
        MUST (name)
      )

      ( 35 NAME 'dmtfSoftwareElementStructureRule2'
        FORM dmtfSoftwareElementNameForm2
      )

      ( <oid-nf35> NAME 'dmtfSoftwareElementNameForm2'
        OC dmtfSoftwareElement
        MUST (softwareElementID) <sr27>
      )

3.5 dmtfDirectorySpecification cim22DirectorySpecification

   A directory specification captures the major directory structure of a
   software element and organizes the files of a software element into
   manageable units that can be relocated on a computer system.

   it defines the attributes directoryType, directoryPath.

      ( <oid-at563> <oid-at182> NAME 'directoryType' 'cimDirectoryType'
        DESC 'The DirectoryType property characterizes the type of
              directory being described.  Allowed values are: "Product
           base directory", "Product executable directory", "Product
           library directory", "Product configuration directory",
           "Product include directory", "Product working directory",
           "Product log directory", "Shared base directory", "Shared
           executable directory", "Shared library directory", "Shared
           include directory", "System base directory", "System
           executable directory", "System library directory", "System
           configuration directory", "System include directory",
           "System log directory", "Other".' described.'
        SYNTAX integer SINGLE-VALUE

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

      )

      ( <oid-at564> <oid-at183> NAME 'directoryPath' 'cimDirectoryPath'
        DESC 'The DirectoryPath property is used to capture the name of a
              directory. The value supplied by an application provider is
              actually a default or recommended path name. The value can
              be changed for a particular environment.'
        SYNTAX string{1024} string SINGLE-VALUE
      )

      ( <oid-oc235> <oid-oc100> NAME 'dmtfDirectorySpecification' 'cim22DirectorySpecification'
        DESC 'The dmtfDirectorySpecification cim22DirectorySpecification class captures the major
              directory structure of a software element. it This class is
              used to organize the files of a software element into
              manageable units that can be relocated on a computer
              system.'
        SUP dmtfCheck
        MUST (directoryType cim22Check
        MAY (cimDirectoryType $ cimDirectoryPath)
      )

   The following content rule specifies the auxiliary classes that may
   be attached to cim22DirectorySpecification.

      ( <oid-oc100> NAME 'cim22DirectorySpecificationContentRule'
        DESC 'The auxiliary classes that may be attached to
              cim22DirectorySpecification'
        AUX (cim22DirectorySpecificationFileAuxClass $
             cim22ToDirectorySpecificationAuxClass $ directoryPath)
             cim22FromDirectorySpecificationAuxClass)
      )

3.6 dmtfArchitectureCheck cim22ArchitectureCheck

   Architecture checks specify the hardware platform a software element
   can run on. Its attributes are compared with the corresponding
   processor attributes.  As long as there is at least one processor
   that satisfies the details of the condition, the check is satisfied.

      ( <oid-at565> <oid-at184> NAME 'architectureType' 'cimArchitectureType'
        DESC 'The ArchitectureType property identifies a particular type
              of architecture or architecture family that is required to
              properly execute a particular software element. The intent
              is to capture the details about the machine instructions
              exploited by the executables of the software element.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc236> <oid-oc101> NAME 'dmtfArchitectureCheck' 'cim22ArchitectureCheck'

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

        DESC 'specifies 'The Architecture Check specifies the hardware platform a
              software element can run
           on.' on. The details of this checks are
              compared with the corresponding details found in a
              cim22Processor object referenced by a
              cim22ComputerSystemProcessor association for the
              cim22ComputerSystem object that describes the
              environment. As long as there is at least one cim22Processor
              that satisfies the details of the condition, the check is
              satisfied. In other words, all the processors on the
              relevant computer system do not need to satisfy the
              condition. There needs to be at least one.'
        SUP dmtfCheck
        MUST (architectureType) cim22Check
        MAY (cimArchitectureType)
      )

3.7 dmtfMemoryCheck cim22MemoryCheck

   Memory checks specifiy specify the minimum amount of memory that a system must
   have available. When an operating system has more free physical
   memory than the value specified in MemorySize, the condition is
   satisfied.

      ( <oid-at566> <oid-at185> NAME 'memorySize' 'cimMemorySize'
        DESC 'The amount of memory that needs to exist on a computer
              system for a software element to executing properly.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc237> <oid-oc102> NAME 'dmtfMemoryCheck' 'cim22MemoryCheck'
        DESC 'specifies 'The MemoryCheck specifies a condition for the minimum
              amount of memory that needs to be available on a system.'
              system. The amount is specified in the MemorySize
              property. The details of this checks are compared with the
              value of the FreePhysicalMemory property of the
              cim22OperatingSystem object referenced by an InstalledOS
              association for the cim22ComputerSystem object that
              describes the environment. When the value of
              FreePhyscalMemory property is greater than or equal to the
              value specified in MemorySize, the condition is satisfied.'
        SUP dmtfCheck
        MUST (memorySize) cim22Check
        MAY (cimMemorySize)
      )

3.8 dmtfDiskSpaceCheck cim22DiskSpaceCheck

   Disk space checks specify the minimum amount of disk space that a
   system must have available. When a file system have more available
   space than the value specified in availableDiskSpace, the condition

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

   is satisfied.

      ( <oid-at567> <oid-at186> NAME 'availableDiskSpace'
        DESC 'Amount of disk space needed.' 'cimAvailableDiskSpace'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc238> <oid-oc103> NAME 'dmtfDiskSpaceCheck' 'cim22DiskSpaceCheck'
        DESC 'specifies 'The Disk Space Check the amount of disk space the needs to
              be available on the system.' system. The amount is specified in the
              AvailableDiskSpace property. The details of this checks are
              compared with the value of the AvailableSpace property of
              the cim22FileSystem object associated with the
              cim22ComputerSystem object that describes the
              environment. When the value of AvailableSpace property is
              greater than or equal to the value specified in
              AvailableDiskSpace, the condition is satisfied.'
        SUP dmtfCheck
        MUST (availableDiskSpace) cim22Check
        MAY (cimAvailableDiskSpace)
      )

3.9 dmtfSwapSpaceCheck cim22SwapSpaceCheck

   Swap space checks specify the minimum amount of swap space that a
   system must have available.  When a system have more swap space
   available that the value in swapSpaceSize, the condition is
   satisfied.

      ( <oid-at568> <oid-at187> NAME 'swapSpaceSize' 'cimSwapSpaceSize'
        DESC 'specifies 'The SwapSpaceSize property specifies the minimum number of
              Kilo bytes of swap space that needs to be available on the
              target system.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc239> <oid-oc104> NAME 'dmtfSwapSpaceCheck' 'cim22SwapSpaceCheck'
        DESC 'specifies 'The Swap Space Check specifies the amount of swap space
              that needs to be available on the system.' system. The amount is
              specified in the SwapSpaceSize property. The details of
              this checks are compared with the corresponding details
              found in a cim22OperatingSystem object referenced by
              InstalledOS association for the cim22ComputerSystem object
              describing the environment. When the value of
              TotalSwapSpaceSize property is greater than or equal to the
              value specified in SwapSpacesize, the condition is
              satisfied.'
        SUP dmtfCheck
        MUST (swapSpaceSize) cim22Check
        MAY (cimSwapSpaceSize)
      )

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

3.10 dmtfOSVersionCheck cim22OSVersionCheck

   This class specifies the versions of the OS that can support this
   software element. This check can be for a specific, minimum, maximum
   or a range of releases of an OS. To specify a specific version the
   minimum and maximum versions must be the same. To specify a minimum,
   the minimum version needs only be specified. To specify a maximum
   version, the maximum version needs only be specified. To specify a
   range both minimum and maximum version need to be specified.

      ( <oid-at188> NAME 'cimMinimumVersion'
        DESC 'Minimum version of required operating system. The
   targetOperatingSystem attributes value is
              encoded as <major>.<minor>.<revision> or
              <major>.<minor><letter revision> '
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at189> NAME 'cimMaximumVersion'
        DESC 'Maximum version of the owning SoftwareElement required operating system. The value is
              encoded as <major>.<minor>.<revision> or
              <major>.<minor><letter revision> '
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-oc105> NAME 'cim22OSVersionCheck'
        DESC 'The OS Version Check class specifies the versions of the OS
              that can support this software element. This check can be
              for a specific, minimum, maximum or a range of releases of
              an OS. To specify a specific version the minimum and
              maximum versions must be the same. To specify a minimum,
              the minimum version needs only be specified. To specify a
              maximum version, the maximum version needs only be
              specified. To specify a range both minimum and maximum
              version need to be specified. The type of operating system. system
              is specified in the TargetOperatingSystem property of the
              owning SoftwareElement. The details of this checks are
              compared with the corresponding details found in a
   dmtfOperatingSystem
              cim22OperatingSystem object referenced by dmtfInstalledOSAuxClass. InstalledOS
              association for the cim22ComputerSystem object that
              describes the environment. As long as there is at least one dmtfOperatingSystem object
              cim22OperatingSystem that satisfies the details of the
              condition, the check is satisfied. In other words, all the
              operating systems on the relevant computer system do not
              need to satisfy the condition. There needs to be at least
              one. Also, note the the oSType attribute OSType property of the dmtfOperatingSystem
              cim22OperatingSystem class must match the type of the targetOperatingSystem property.

      ( <oid-at569> NAME 'minimumVersion'
        DESC 'Minimum version of required operating system. The value is
           encoded as <major>.<minor>.<revision> or
           <major>.<minor><letter revision>.'
        SYNTAX string{64} SINGLE-VALUE
      )

      ( <oid-at570> NAME 'maximumVersion'
        DESC 'Maximum version of required operating system. The value is
           encoded as <major>.<minor>.<revision> or
           <major>.<minor><letter revision>.'
        SYNTAX string{64} SINGLE-VALUE
      )

      ( <oid-oc240> NAME 'dmtfOSVersionCheck'
        DESC 'specifies the versions of the OS that can support this
           software element.'
              TargetOperatingSystem property.'
        SUP dmtfCheck
        MUST (minimumVersion cim22Check

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

        MAY (cimMinimumVersion $ maximumVersion) cimMaximumVersion)
      )

3.11 dmtfSoftwareElementVersionCheck cim22SoftwareElementVersionCheck

   This class specifies a type of software element that must exist in
   the environment. This check can be for a specific, minimum, maximum
   or a range of versions. To specify a specific version the lower and
   upper versions must be the same. To specify a minimum the lower
   version needs only be specified. To specify a maximum version the
   upper version needs only be specified. To specify a range both upper
   and lower version need to be specified. The details of this checks
   are compared with the corresponding details found in a
   dmtfSoftwareElement
   cim22SoftwareElement object referenced by an InstalledSoftwareElement
   association for the dmtfComputerSystem cim22ComputerSystem object. As long as there is
   at least one dmtfSoftwareElement cim22SoftwareElement that satisfies the details of the
   condition, the check is satisfied.

      ( <oid-at571> <oid-at190> NAME 'softwareElementName' 'cimSoftwareElementName'
        DESC 'The name of the software element being checked.'
        SYNTAX string{256} string SINGLE-VALUE
      )

      ( <oid-at572> <oid-at191> NAME 'lowerSoftwareElementVersion' 'cimLowerSoftwareElementVersion'
        DESC 'The minimum version of a software elements being checked.'
        SYNTAX string{64} string SINGLE-VALUE
      )

      ( <oid-at573> <oid-at192> NAME 'upperSoftwareElementVersion' 'cimUpperSoftwareElementVersion'
        DESC 'The maximum version of a software elements being checked.'
        SYNTAX string{64} string SINGLE-VALUE
      )

      ( <oid-at574> <oid-at193> NAME 'softwareElementStateDesired' 'cimSoftwareElementStateDesired'
        DESC 'The state of the software element being checked.  Allowed
           values are: "Deployable", "Installable", "Executable",
           "Running".' checked.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at575> <oid-at194> NAME 'targetOperatingSystemDesired' 'cimTargetOperatingSystemDesired'
        DESC 'The target operating system of the software element being
           checked.  Allowed values are: "Unknown", "Other", "MACOS",
           "ATTUNIX", "DGUX", "DECNT", "Digital Unix", "OpenVMS",
           "HPUX", "AIX", "MVS", "OS400", "OS/2", "JavaVM", "MSDOS",
           "WIN3x", "WIN95", "WIN98", "WINNT", "WINCE", "NCR3000",
           "NetWare", "OSF", "DC/OS", "Reliant UNIX", "SCO UnixWare",
           "SCO OpenServer", "Sequent", "IRIX", "Solaris", "SunOS",
           "U6000", "ASERIES", "TandemNSK", "TandemNT", "BS2000",
           "LINUX", "Lynx", "XENIX", "VM/ESA", "Interactive UNIX",
           "BSDUNIX", "FreeBSD", "NetBSD", "GNU Hurd", "OS9", "MACH
           Kernel", "Inferno", "QNX", "EPOC", "IxWorks", "VxWorks",
              "MiNT", "BeOS", "HP MPE", "NextStep", "PalmPilot",
           "Rhapsody".'
              checked.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc241> <oid-oc106> NAME 'dmtfSoftwareElementVersionCheck' 'cim22SoftwareElementVersionCheck'
        DESC 'specifies 'The Software Element Version Check class specifies a type
              of software element that must exist in the
           environment.'
              environment. This check can be for a specific, minimum,

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

              maximum or a range of versions. To specify a specific
              version the lower and upper versions must be the same. To
              specify a minimum the lower version needs only be
              specified. To specify a maximum version the upper version
              needs only be specified. To specify a range both upper and
              lower version need to be specified. The details of this
              checks are compared with the corresponding details found in
              a cim22SoftwareElement object referenced by an
              InstalledSoftwareElement association for the
              cim22ComputerSystem object. As long as there is at least one
              cim22SoftwareElement that satisfies the details of the
              condition, the check is satisfied. In other words, all the
              software elements on the relevant computer system do not
              need to satisfy the condition. There needs to be at least
              one.'
        SUP dmtfCheck
        MUST (softwareElementName cim22Check
        MAY (cimSoftwareElementName $ lowerSoftwareElementVersion cimLowerSoftwareElementVersion $
           upperSoftwareElementVersion
             cimUpperSoftwareElementVersion $ softwareElementStateDesired
             cimSoftwareElementStateDesired $
           targetOperatingSystemDesired)
             cimTargetOperatingSystemDesired)
      )

3.12 dmtfFileSpecification cim22FileSpecification

   A dmtfFileSpecification cim22FileSpecification object identifies a file that is either to
   be on or off the system. DmtfDirectorySpecificationFileAuxClass cim22DirectorySpecificationFileAuxClass
   identifies the directory the file is to be located in.

      ( <oid-at576> <oid-at195> NAME 'fileName' 'cimFileName'
        DESC 'Either the name of the file or the name of the file with a
              directory prefix.'
        SYNTAX string{1024} string SINGLE-VALUE
      )

      ( <oid-at577> <oid-at196> NAME 'createTimeStamp' 'cimCreateTimeStamp'
        DESC 'The creation date and time of the file.'
        SYNTAX generalizedTime SINGLE-VALUE
      )

      ( <oid-at578> <oid-at197> NAME 'fileSize'
        DESC 'Size of the File in bytes..' 'cimFileSize'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at579> <oid-at198> NAME 'checkSum' 'cimCheckSum'
        DESC 'The File Checksum property is a checksum calculated as the
              16-bit sum of the first 32 bytes of the file.'
        SYNTAX integer SINGLE-VALUE
      )

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

      ( <oid-at580> <oid-at199> NAME 'cRC1' 'cimCRC1'
        DESC 'The File CRC 1 property is the CRC value calculated using
              the middle 512K bytes.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at581> <oid-at200> NAME 'cRC2' 'cimCRC2'
        DESC 'The File CRC 2 is the CRC value for the middle 512K bytes
              with a offset modulo 3 to the start of the file of zero.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-at582> <oid-at201> NAME 'mD5Checksum' 'cimMD5Checksum'
        DESC 'The MD5 algorithm is a well-known algorithm for computing a
              128-bit checksum for any file or object. The likelihood of
              two different files producing the file.' same MD5 checksum is very
              small (about 1 in 2^64), and as such, the MD5 checksum of a
              file can be used to construct a reliable content identifier
              that is very likely to uniquely identify the file. The
              reverse is also true. If two files have the same MD5
              checksum, it is very likely that the files are
              identical. For purposes of MOF specification of the MD5
              property, the MD5 algorithm always generates a 32 character
              string. For example: The string abcdefghijklmnopqrstuvwxyz
              generates the string c3fcd3d76192e4007dfb496cca67e13b. See
              http://www. rsa.com/pub/rfc1321.txt for details on the
              implementation of the MD5 algorithm.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-oc242> <oid-oc107> NAME 'dmtfFileSpecification' 'cim22FileSpecification'
        DESC 'identifies 'A cim22FileSpecification identifies a file that is either to
              be on or off the system.' system. The file is to be located in the
              directory identified by the DirectorySpecificationFile
              associations. When the invoke() method is used, it is
              expected that it will use the combination of information
              provided to check for the file existence. Therefore, any of
              the properties with a NULL value are not checked. So, if
              only the Name and the MD5 properties have values, they are
              the only ones consider by the invoke() method.'
        SUP dmtfCheck
        MUST (fileName cim22Check
        MAY (cimFileName $ createTimeStamp cimCreateTimeStamp $ fileSize cimFileSize $ checkSum
             cimCheckSum $ cRC1 cimCRC1 $
           cRC2 cimCRC2 $ mD5Checksum) cimMD5Checksum)
      )

   The following content rule specifies the auxiliary classes that may
   be attached to cim22FileSpecification.

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

      ( <oid-oc107> NAME 'cim22FileSpecificationContentRule'
        DESC 'The auxiliary classes that may be attached to
              cim22FileSpecification'
        AUX (cim22DirectorySpecificationFileAuxClass)
      )

3.13 dmtfVersionCompatibilityCheck cim22VersionCompatibilityCheck

   This class specifies whether it is permissible to create the next
   state of a software element. It defines the attributes
   allowDownVersion, allowMultipleVersions, and reinstall.

      ( <oid-at583> <oid-at202> NAME 'allowDownVersion' 'cimAllowDownVersion'
        DESC 'The AllowDownVersion property shows indicates that this software
              element can transition to its next state even if a higher
              or latter later version of the software element already exists in
              the environment.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at584> <oid-at203> NAME 'allowMultipleVersions' 'cimAllowMultipleVersions'
        DESC 'The AllowMultipleVersions option controls the ability to
              configure multiple versions of a product on a system.'
              SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-at585> <oid-at204> NAME 'reinstall' 'cimReinstall'
        DESC 'The Reinstall property shows indicates that this software element
              can transition to its next state even if a software element
              of the same version already exists in the environment.'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc243> <oid-oc108> NAME 'dmtfVersionCompatibilityCheck' 'cim22VersionCompatibilityCheck'
        DESC 'specifies 'The VersionCompatibilityCheck class specifies whether it is
              permissible to create the next state of a software
              element.'
        SUP dmtfCheck
        MUST (allowDownVersion cim22Check
        MAY (cimAllowDownVersion $ allowMultipleVersions cimAllowMultipleVersions $ reinstall)
             cimReinstall)
      )

3.14 dmtfAction cim22Action

   This abstract class represents an operation that is part of a process to
   either create a SoftwareElement in its next state or to eliminate the
   SoftwareElement in the current state. It uses the attributes
   name, version, softwareElementState, softwareElementID,
   targetOperatingSystem, actionID, direction, caption, and description.

      ( <oid-at586> <oid-at205> NAME 'actionID' 'cimActionID'

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

        DESC 'The ActionID property is a unique identifier assigned to a
              particular action for a software element.  May be used as an
RDN.' element.'
        SYNTAX string{256} SINGLE-VALUE
      )

      ( <oid-at587> <oid-at206> NAME 'direction' 'cimDirection'
        DESC 'The Direction property is used to show indicate whether a
              particular action object Actionobject is part of a sequence of actions to
              transition the currentsoftware element to its next state,
              such as Install or to remove the current software element,
              such as Uninstall.  Allowed values are: "Install",
           "Uninstall".' Uninstall.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc244> <oid-oc109> NAME 'dmtfAction' 'cim22Action'
        DESC 'an 'A cim22Action is an operation that is part of a process to
              either create a SoftwareElement in its next state or to
              eliminate the SoftwareElement in the current state.'
        SUP top ABSTRACT
        MUST (name (orderedCimModelPath)
        MAY (cimName $ version cimVersion $ softwareElementState cimSoftwareElementState $ softwareElementID
             cimSoftwareElementID $
           targetOperatingSystem cimTargetOperatingSystem $ actionID
             cimActionID $ direction cimDirection $ caption cimCaption $
           description) cimDescription)
      )

   Although a variety of attributes may be used as RDNs, the following
   structural rules are recommended:

      ( 36 <oid-nf26> NAME 'dmtfActionStructureRule1'
        FORM dmtfActionNameForm1
        SUP 34 35
      )
      ( <oid-nf36> NAME 'dmtfActionNameForm1' 'cim22ActionNameForm'
        OC dmtfAction cim22Action
        MUST (name) (orderedCimModelPath)
      )

      ( 37 <sr26> NAME 'dmtfActionStructureRule2' 'cim22ActionStructureRule'
        FORM dmtfActionNameForm1 cim22ActionNameForm
        SUP 34 35 <sr27>
      )

   The following content rule specifies the auxiliary classes that may
   be attached to cim22Action.

      ( <oid-nf37> <oid-oc109> NAME 'dmtfActionNameForm2'
        OC dmtfAction
        MUST (actionID) 'cim22ActionContentRule'
        DESC 'The auxiliary classes that may be attached to cim22Action'
        AUX (cim22ActionSequenceAuxClass)
      )

3.15 dmtfDirectoryAction cim22DirectoryAction

   This abstract class manages directories to be managed. Creation of directories
   is handled by dmtfCreateDirectoryAction cim22CreateDirectoryAction and removal is handled by dmtfRemoveDirectoryAction.
   cim22RemoveDirectoryAction.

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

      ( <oid-at588> <oid-at207> NAME 'directoryName'
        DESC 'The name of the directory.' 'cimDirectoryName'
        SYNTAX string{1024} string SINGLE-VALUE
      )

      ( <oid-oc245> <oid-oc110> NAME 'dmtfDirectoryAction' 'cim22DirectoryAction'
        DESC 'used 'The DirectoryAction is an class that is used for
              directories to be managed.' managed. Creation of directories is
              handled by the CreateDirectoriesAction and removal is
              handled by the RemoveDirectory action.'
        SUP dmtfAction ABSTRACT
        MUST (directoryName) cim22Action
        MAY (cimDirectoryName)
      )

   The following content rule specifies the auxiliary classes that may
   be attached to cim22DirectoryAction.

      ( <oid-oc110> NAME 'cim22DirectoryActionContentRule'
        DESC 'The auxiliary classes that may be attached to
              cim22DirectoryAction'
        AUX (cim22ToDirectoryActionAuxClass $
             cim22FromDirectoryActionAuxClass)
      )

3.16 dmtfCreateDirectoryAction cim22CreateDirectoryAction

   This class creates empty directories for dmtfSoftwareElement cim22SoftwareElement objects
   to be installed locally.

      ( <oid-oc246> <oid-oc111> NAME 'dmtfCreateDirectoryAction' 'cim22CreateDirectoryAction'
        DESC 'creates 'The CreateDirectory action creates empty directories for
              SoftwareElements to be installed locally.'
        SUP dmtfDirectoryAction cim22DirectoryAction
      )

3.17 dmtfRemoveDirectoryAction cim22RemoveDirectoryAction

   This class removes directories for dmtfSoftwareElement cim22SoftwareElement objects.

      ( <oid-at589> <oid-at208> NAME 'mustBeEmpty'
        DESC 'shows whether the directory must be empty (TRUE) to be
           removed' 'cimMustBeEmpty'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc247> <oid-oc112> NAME 'dmtfRemoveDirectoryAction' 'cim22RemoveDirectoryAction'
        DESC 'removes 'The RemoveDirectoryAction removes directories for
              SoftwareElements.'
        SUP dmtfDirectoryAction
        MUST (mustBeEmpty) cim22DirectoryAction
        MAY (cimMustBeEmpty)
      )

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

3.18 dmtfFileAction cim22FileAction

   This abstract class allows an implementor to locate files that already exist
   on the users machine, and move or copy those files to a new location.

      ( <oid-oc248> <oid-oc113> NAME 'dmtfFileAction' 'cim22FileAction'
        DESC 'allows an implementor 'The cim22FileAction allows the author to locate files that
              already exist on the users machine, and move or copy those
              files to a new location.'
        SUP dmtfAction ABSTRACT cim22Action
      )

   The following content rule specifies the auxiliary classes that may
   be attached to cim22FileAction.

      ( <oid-oc113> NAME 'cim22FileActionContentRule'
        DESC 'The auxiliary classes that may be attached to
              cim22FileAction'
        AUX (cim22FromDirectorySpecificationAuxClass $
             cim22FromDirectoryActionAuxClass)
      )

3.19 dmtfCopyFileAction cim22CopyFileAction

   This class specifies files that exist on a computer system, and to
   move or copy those files to a new location.

      ( <oid-at590> <oid-at209> NAME 'source'
        DESC 'source location' 'cimSource'
        SYNTAX string{1024} string SINGLE-VALUE
      )

      ( <oid-at591> <oid-at210> NAME 'destination'
        DESC 'destination location' 'cimDestination'
        SYNTAX string{1024} string SINGLE-VALUE
      )

      ( <oid-at592> <oid-at211> NAME 'deleteAfterCopy'
        DESC 'boolean indicating if the file should be moved (true)' 'cimDeleteAfterCopy'
        SYNTAX boolean SINGLE-VALUE
      )

      ( <oid-oc249> <oid-oc114> NAME 'dmtfCopyFileAction' 'cim22CopyFileAction'
        DESC 'specifies 'The cim22CopyFileAction specifies files that exist on a
              computer system, and to move or copy those files to a new location.'
              location. The to/from information for the copy is specified
              using either the ToDirectorySpecification/
              FromDirectorySpecification or the ToDirectoryAction/
              FromDirectoryAction associations. The first set is
              used when the source and/or the target are to exist before
              any actions are taken. The second set is used when the

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

              source and/or target are created as a part of a previous
              action. In the latter case, the action to create the
              directory must occur prior to the CopyFileAction object.'
        SUP dmtfFileAction
        MUST (source cim22FileAction
        MAY (cimSource $ cimDestination $ destination cimDeleteAfterCopy)
      )

   The following content rule specifies the auxiliary classes that may
   be attached to cim22CopyFileAction.

      ( <oid-oc114> NAME 'cim22CopyFileActionContentRule'
        DESC 'The auxiliary classes that may be attached to
              cim22CopyFileAction'
        AUX (cim22ToDirectorySpecificationAuxClass $ deleteAfterCopy)
             cim22ToDirectoryActionAuxClass)
      )

3.20 dmtfRemoveFileAction cim22RemoveFileAction

   This class uninstalls files, specified in the file attribute.

      ( <oid-at593> <oid-at212> NAME 'file'
        DESC 'file to be removed' 'cimFile'
        SYNTAX string{1024} string SINGLE-VALUE
      )

      ( <oid-oc250> <oid-oc115> NAME 'dmtfRemoveFileAction' 'cim22RemoveFileAction'
        DESC 'uninstalls files' 'The RemoveFileAction uninstalls files.'
        SUP dmtfFileAction
        MUST (file) cim22FileAction
        MAY (cimFile)
      )

3.21 dmtfRebootAction cim22RebootAction

   This class causes a reboot of the system where the software element
   is installed.

      ( <oid-oc251> <oid-oc116> NAME 'dmtfRebootAction' 'cim22RebootAction'
        DESC 'Causes 'The RebootAction Causes a reboot of the system where the
              SoftwareElement is installed.'
        SUP dmtfAction cim22Action
      )

3.22 dmtfExecuteProgram cim22ExecuteProgram

   This class causes files to be executed on the system where the
   dmtfSoftwareElement
   cim22SoftwareElement object is installed.  It uses the attributes
   programPath and commandLine.

      ( <oid-at594> <oid-at213> NAME 'programPath'
        DESC 'Path to 'cimProgramPath'

INTERNET DRAFTLDAP Schema for the executable' DMTF Application CIM v2.1
ModelDecember 1999

        SYNTAX string{1024} string SINGLE-VALUE
      )

      ( <oid-at595> <oid-at214> NAME 'commandLine' 'cimCommandLine'
        DESC 'A string that is invocable on a system command line.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-oc252> <oid-oc117> NAME 'dmtfExecuteProgram' 'cim22ExecuteProgram'
        DESC 'causes 'The ExecuteProgram causes files to be executed on the
              system where the SoftwareElement is installed.'
        SUP dmtfAction
        MUST (programPath cim22Action
        MAY (cimProgramPath $ commandLine) cimCommandLine)
      )

3.23 dmtfSettingCheck cim22SettingCheck

   This class specifies information needed to check a particular setting
   file for a specific entry that contains a value that is equal to, or
   contains, the value specified. All compares are case insensitive.

      ( <oid-at596> <oid-at215> NAME 'sectionKey' 'cimSectionKey'
        DESC 'Key of section containing the settings to be checked.'
        SYNTAX string{256} SINGLE-VALUE
      )

      ( <oid-at597> <oid-at216> NAME 'entryName' 'cimEntryName'
        DESC 'Name of the Entry to be checked.' checked'
        SYNTAX string{256} SINGLE-VALUE
      )

      ( <oid-at598> <oid-at217> NAME 'entryValue' 'cimEntryValue'
        DESC 'Value to be checked that is associated with the named
              entry.'
        SYNTAX string SINGLE-VALUE
      )

      ( <oid-at599> <oid-at218> NAME 'checkType' 'cimCheckType'
        DESC 'This specifies the way the setting value should be
           compared.  Allowed values are:  "Matches", "Contains".' compared.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc253> <oid-oc118> NAME 'dmtfSettingCheck' 'cim22SettingCheck'
        DESC 'specifies 'This class specifies information needed to check a
              particular setting file for a specific entry that contains
              a value that is equal to, or contains, the value specified.'
              specified. All compares are assumed to be case insensitive.'
        SUP dmtfCheck
        MUST (sectionKey cim22Check

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

        MAY (cimSectionKey $ entryName cimEntryName $ entryValue cimEntryValue $ checkType
             cimCheckType $ fileName) cimFileName)
      )

3.24 dmtfModifySettingAction cim22ModifySettingAction

   This class specifies the information to be used to change a
   particular setting file for a specific entry with a specific value.
   All additions are case sensitive while removes are case insensitive.

      ( <oid-at600> <oid-at219> NAME 'actionType' 'cimActionType'
        DESC 'Type of action to be performed on the specified setting
              entry. Create - Creates the specified entry. Delete -
              Deletes the specified entry. Append - Append to the end of
              the specified entry. Remove - Remove the value from the
              specified entry.  Allowed values are: "Create", "Delete",
           "Append", "Remove".' entry.'
        SYNTAX integer SINGLE-VALUE
      )

      ( <oid-oc254> <oid-oc119> NAME 'dmtfModifySettingAction' 'cim22ModifySettingAction'
        DESC 'specifies 'This class specifies the information to be used to change modify a
              particular setting file for a specific entry with a specif1ic value.'
              specific value. The value specified is created as a new
              entry or appends to, replaces, removes from, or deletes the
              specified entry. All additions are assumed to be case
              sensitive. Removes are assumed to be case insensitive.'
        SUP dmtfAction
        MUST (sectionKey cim22Action
        MAY (cimSectionKey $ entryName cimEntryName $ entryValue cimEntryValue $ fileName cimFileName $
           actionType)
             cimActionType)
      )

3.25 dmtfDirectorySpecificationFileAuxClass cim22DirectorySpecificationFileAuxClass

   This class identifies the directory that contains the file being
   specified by referencing the dmtfDirectorySpecification cim22DirectorySpecification class.

      ( <oid-at601> <oid-at220> NAME 'dmtfDirectorySpecificationRef'
        DESC 'The directory specification' 'cimDirectorySpecificationRef'
        SYNTAX DN SINGLE-VALUE
      )

      ( <oid-at602> <oid-at221> NAME 'dmtfFileSpecificationRefs'
        DESC 'File Specifications' 'cimFileSpecificationRef'
        SYNTAX DN
      )

      ( <oid-oc255> <oid-oc120> NAME 'dmtfDirectorySpecificationFileAuxClass' 'cim22DirectorySpecificationFileAuxClass'
        DESC 'identifies 'The cim22DirectorySpecificationFile association identifies
              the directorythat contains the file being specified by
              referencing the dmtfDirectorySpecification cim22DirectorySpecification class.'

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

        SUP top AUXILIARY
        MUST (dmtfDirectorySpecificationRef
        MAY (cimDirectorySpecificationRef $ dmtfFileSpecificationRefs) cimFileSpecificationRef)
      )

3.26 dmtfActionSequenceAuxClass

   dmtfActionSequenceAuxClass cim22ActionSequenceAuxClass

   cim22ActionSequenceAuxClass defines a series of operations that
   either transitions the software element, referenced by
   dmtfSoftwareElementActionsAuxClass,
   cim22SoftwareElementActionsAuxClass, to its next state or removes the
   software element from its current environment. The action classes
   participating in this association must have the same value for the
   direction property since they are either part of a sequence to
   transition a software element into its next state or to uninstall a
   software element. The next-state actions and uninstall actions
   associated with a particular software element must be a continuos continuous
   sequence. Since the action sequence is an association the loops on
   the action class with roles for the 'prior' action and 'next' action
   in a sequence, the need for a continous continuous sequence implies: (1)Within
   the set of next-state or uninstall actions, there is one and only one
   action that does not have an instance of the ActionSequence
   association referencing it in the 'next' role. This is the first
   action in the sequence. (2) Within the set of next-state or uninstall
   actions, there is one and only one action that does not have an
   instance of the ActionSequence association referencing it in the
   'prior' role. This is the last action in the sequence. (3) All other
   actions within the set of next-state and uninstall actions must
   participate in two instances of the ActionSequence association, one
   in a prior role and one in the next role.

      ( <oid-at603> <oid-at222> NAME 'nextActionRef'
        DESC 'next action' 'cimNextRef'
        SYNTAX DN SINGLE-VALUE
      )

      ( <oid-at604> <oid-at223> NAME 'priorActionRef'
        DESC 'next action' 'cimPriorRef'
        SYNTAX DN SINGLE-VALUE
      )

      ( <oid-oc256> <oid-oc121> NAME 'dmtfActionSequenceAuxClass' 'cim22ActionSequenceAuxClass'
        DESC 'used 'The cim22ActionSequence association is used to define a
              series of operations that either transitions the software
              element, referenced by the
           dmtfSoftwareElementActions cim22SoftwareElementActions
              association, to its next state or removes the software
              element from its current
           environment.' environment. The Action classes
              participating in this association must have the same value
              for the Direction property since they are either part of a
              sequence to transition a software element into its next
              state or to uninstall a software element. The next-state
              actions and uninstall actions associated with a particular

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

              software element must be a continuous sequence. Since the
              ActionSequence is an association the loops on the Action
              class with roles for the "prior" action and "next" action
              in a sequence, the need for a continuous sequence implies:
              (1)Within the set of next-state or uninstall actions, there
              is one and only one action that does not have an instance
              of the ActionSequence association referencing it in the
              "next" role. This is the first action in the sequence. (2)
              Within the set of next-state or uninstall actions, there is
              one and only one action that does not have an instance of
              the ActionSequence association referencing it in the
              "prior" role. This is the last action in the sequence. (3)
              All other actions within the set of next-state and
              uninstall actions must participate in two instances of the
              ActionSequence association, one in a prior role and one in
              the next role. Both attributes point to cim22Action objects.'
        SUP top AUXILIARY
        MUST (nextActionRef
        MAY (cimNextRef $ priorActionRef) cimPriorRef)
      )

3.27 dmtfSoftwareFeatureSoftwareElementsAuxClass cim22SoftwareFeatureSoftwareElementsAuxClass

   This auxiliary class identifies the software elements that make up a
   particular software feature. In it, groupComponentRefs point to
   dmtfSoftwareFeature objects and partComponentRefs point to
   dmtfSoftwareElement objects.

      ( <oid-oc257> <oid-oc122> NAME 'dmtfSoftwareFeatureSoftwareElementsAuxClass' 'cim22SoftwareFeatureSoftwareElementsAuxClass'
        DESC 'identifies 'The SoftwareFeatureSoftwareElements associations identifies
              the software elements that make up a particular software feature.'
              feature. Attribute cimGroupComponentRef points to
              cim22SoftwareFeature and attribute cimPartComponentRef points
              to cim22SoftwareElement.'
        SUP dmtfComponentAuxClass AUXILIARY cim22ComponentAuxClass
        MAY (cimGroupComponentRef $ cimPartComponentRef)
      )

3.28 dmtfToDirectorySpecificationAuxClass cim22ToDirectorySpecificationAuxClass

   This auxiliary class identifies the target directory for the file
   action and assumes that the target directory already existed. This
   association cannot exist with a dmtfToDirectoryActionAuxClass cim22ToDirectoryActionAuxClass since
   a file action can only involve a single target directory.

      ( <oid-at605> <oid-at224> NAME 'dmtfDirectorySpecificationRef'
        DESC 'directory specification indicating the destination' 'cimDestinationDirectoryRef'
        SYNTAX DN SINGLE-VALUE
      )

      ( <oid-at606> <oid-at225> NAME 'dmtfCopyFileActionRefs'
        DESC 'List of copy file actions' 'cimFileNameRef'
        SYNTAX DN

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

      )

      ( <oid-oc258> <oid-oc123> NAME 'dmtfToDirectorySpecificationAuxClass' 'cim22ToDirectorySpecificationAuxClass'
        DESC 'identifies 'The ToDirectorySpecification association identifies the
              target directory for the file action.' action. When this association
              is used, the assumption is that the target directory
              already existed. This association cannot exist with a
              ToDirectoryAction association since a file action can only
              involve a single target directory. Attribute
              cimDestinationDirectoryRef points to
              cim22DirectorySpecification and attribute cimFileNameRef
              points to cim22CopyFileAction.'
        SUP top AUXILIARY
        MUST (dmtfDirectorySpecificationRef
        MAY (cimDestinationDirectoryRef $ dmtfCopyFileActionRefs) cimFileNameRef)
      )

3.29 dmtfFromDirectorySpecificationAuxClass cim22FromDirectorySpecificationAuxClass

   This auxiliary class identifies the source directory for the file
   action and assumed that the source directory already existed. This
   association cannot exist with a dmtfFromDirectoryActionAuxClass cim22FromDirectoryActionAuxClass
   since a file action can only involve single source directory.

      ( <oid-at607> <oid-at226> NAME 'dmtfFileActionRefs'
        DESC 'a list of file actions' 'cimSourceDirectoryRef'
        SYNTAX DN
      )

      ( <oid-oc259> <oid-oc124> NAME 'dmtfFromDirectorySpecificationAuxClass' 'cim22FromDirectorySpecificationAuxClass'
        DESC 'identifies 'The FromDirectorySpecification association identifies the
              source directory for the file action.' action. When this association
              is used, the assumption is that the source directory
              already existed. This association cannot exist with a
              FromDirectoryAction association since a file action can
              only involve single source directory. Attribute
              cimSourceDirectoryRef points to cim22DirectorySpecification
              and cimFileNameRef points to cim22FileAction.'
        SUP top AUXILIARY
        MUST (dmtfDirectorySpecificationRef
        MAY (cimSourceDirectoryRef $ dmtfFileActionRefs) cimFileNameRef)
      )

3.30 dmtfToDirectoryActionAuxClass cim22ToDirectoryActionAuxClass

   This auxiliary class identifies the target directory for the file
   action and assumes that a previos previous action creates the target
   directory This association cannot exist with a
   dmtfToDirectorySpecificationAuxClass
   cim22ToDirectorySpecificationAuxClass since a file action can only
   involve a single target directory.

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

      ( <oid-at608> NAME 'dmtfDirectoryActionRef'
        DESC 'directory action reference'
        SYNTAX DN SINGLE-VALUE
      )

      ( <oid-oc260> <oid-oc125> NAME 'dmtfToDirectoryActionAuxClass' 'cim22ToDirectoryActionAuxClass'
        DESC 'identifies 'The ToDirectoryAction association identifies the target
              directory for the file action.' action. When this association is
              used, the assumption is that the target directory was
              created by a previous action. This association cannot exist
              with a ToDirectorySpecification association since a file
              action can only involve a single target
              directory. Attribute cimDestinationDirectoryRef points to
              cim22DirectoryAction and attribute cimFileNameRef
              points to cim22CopyFileAction.'
        SUP top AUXILIARY
        MUST (dmtfDirectoryActionRef
        MAY (cimDestinationDirectoryRef $ dmtfCopyFileActionRefs) cimFileNameRef)
      )

3.31 dmtfFromDirectoryActionAuxClass cim22FromDirectoryActionAuxClass

   This auxiliary class identifies the source directory for the file
   action and assumes that a previous action creates the source
   directory.  It cannot exist with a
   dmtfFromDirectorySpecificationAuxClass
   cim22FromDirectorySpecificationAuxClass since a file action can only
   involve a single source directory.

      ( <oid-oc261> <oid-oc126> NAME 'dmtfFromDirectoryActionAuxClass' 'cim22FromDirectoryActionAuxClass'
        DESC 'identifies 'The FromDirectoryAction association identifies the source
              directory for the file action.' action. When this association is
              used, the assumption is that the source directory was
              created by a previous action. This association cannot exist
              with a FromDirectorySpecification association since a file
              action can only involve a single source
              directory. Attribute cimSourceDirectoryRef points to
              cim22DirectoryAction and cimFileNameRef points to
              cim22FileAction.'
        SUP top AUXILIARY
        MUST (dmtfDirectoryActionRef
        MAY (cimSourceDirectoryRef $ dmtfFileActionRefs) cimFileNameRef)
      )

3.32 dmtfSoftwareFeatureServiceImplementationAuxClass cim22SoftwareFeatureServiceImplementationAuxClass

   This auxiliary class relates a service and how it is implemented in
   software and has a many-to-many cardinality.  A service may be
   provided by more than one software feature, operating in conjunction
   and, any software feature may provide more than one service. If
   different implementations of a service exist, each of these
   implementations are individual instantiations of the dmtfService cim22Service
   object. These individual instantiations would then have associations
   to the unique implementations.

      ( <oid-oc262> <oid-oc127> NAME 'dmtfSoftwareFeatureServiceImplementationAuxClass'

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

        'cim22SoftwareFeatureServiceImplementationAuxClass'
        DESC 'relation 'An association between a Service and how it is implemented
              in
           software.' software. The cardinality of this association is
              many-to-many. A Service may be provided by more than one
              SoftwareFeature, operating in conjunction. And, any
              software Feature may provide more than one Service. When
              multiple SoftwareFeatures are associated with a single
              Service, it is assumed that these elements operate in
              conjunction to provide the Service. If different
              implementations of a Service exist, each of these
              implementations would result in individual instantiations
              of the Service object. These individual instantiations
              would then have associations to the unique
              implementations. Attribute cimAntecendentRef points to
              cim22SoftwareFeature and attribute cimDependentRef points to
              cim22Service.'
        SUP dmtfDependencyAuxClass AUXILIARY cim22DependencyAuxClass
        MAY (cimAntecedentRef $ cimDependentRef)
      )

3.33 dmtfSoftwareFeatureSAPImplementationAuxClass cim22SoftwareFeatureSAPImplementationAuxClass

   This auxiliary class represents the relationship between a eervice service
   access point and how it is implemented in software. The cardinality
   of this association is many-to-many. A SAP may be provided by more
   than one SoftwareFeature, operating in conjunction. And, any
   SoftwareFeature may provide more than one ServiceAccessPoint. a When
   many SoftwareFeatures are associated with single SAP, it is assumed
   that these elements operate in conjunction to provide the
   AccessPoint. If different implementations of a SAP exist, each of
   these implementations would result in individual instantiations of
   the ServiceAccessPoint object. These individual instantiations would
   then have associations to the unique implementations.

      ( <oid-oc263> <oid-oc128> NAME 'dmtfSoftwareFeatureSAPImplementationAuxClass' 'cim22SoftwareFeatureSAPImplementationAuxClass'
        DESC 'relationship 'An association between a ServiceAccessPoint and how it is
              implemented in software.' software. The cardinality of this association
              is many-to-many. A SAP may be provided by more than one
              SoftwareFeature, operating in conjunction. And, any
              SoftwareFeature may provide more than one
              ServiceAccessPoint. a When many SoftwareFeatures are
              associated with single SAP, it is assumed that these
              elements operate in conjunction to provide the
              AccessPoint. If different implementations of a SAP exist,
              each of these implementations would result in individual
              instantiations of the ServiceAccessPoint object. These
              individual instantiations would then have associations to
              the unique implementations. Attribute cimAntecendentRef

INTERNET DRAFTLDAP Schema for the DMTF Application CIM v2.1
ModelDecember 1999

              points to cim22SoftwareFeature and attribute cimDependentRef
              points to cim22ServiceAccessPoint.'
        SUP dmtfDependency AUXILIARY cim22DependencyAuxClass
        MAY (cimAntecedentRef $ cimDependentRef)
      )

3.34 dmtfApplicationSystemSoftwareFeatureAuxClass cim22ApplicationSystemSoftwareFeatureAuxClass

   This auxiliary class identifies the software features, which may be
   part of different products, that make up a particular application
   system.

      ( <oid-oc264> <oid-oc129> NAME 'dmtfApplicationSystemSoftwareFeatureAuxClass' 'cim22ApplicationSystemSoftwareFeatureAuxClass'
        DESC 'identifies 'The ApplicationSystemSoftwareFeature associations
              identifies the software features that make up a particular
              application system.' system. The software features can be part of
              different products. Attribute cimGroupComponentRef points
              to cim22ApplicationSystem and attribute cimPartComponentRef
              points to cim22SoftwareFeature.'
        SUP dmtfSystemComponentAuxClass AUXILIARY cim22SystemComponentAuxClass
        MAY (cimGroupComponentRef $ cimPartComponentRef)
      )

3.35 dmtfInstalledSoftwareElementAuxClass cim22InstalledSoftwareElementAuxClass

   This auxiliary class allows one to identify the computer system a
   particular software element is installed on.

      ( <oid-at609> name 'dmtfSoftwareElementRefs' <oid-at227> NAME 'cimSoftwareRef'
        DESC 'references 'References the software elements element that are installed' is installed.'
        SYNTAX DN
      )

      ( <oid-at610> name 'dmtfComputerSystemRef' <oid-at228> NAME 'cimSystemRef'
        DESC 'references 'References the computer system hosting a particular
              software element' element.'
        SYNTAX DN SINGLE-VALUE
      )

      ( <oid-oc265> name 'dmtfInstalledSoftwareElementAuxClass' <oid-oc130> NAME 'cim22InstalledSoftwareElementAuxClass'
        DESC 'identifies 'The InstalledSoftwareElement association allows one to to
              identify the Computer System a particular Software element
              is installed on.' on. Attribute cimSoftwareRef points to
              cim22SoftwareElement and attribute cimSystemRef points to
              cim22ComputerSystem.'
        SUP top AUXILIARY
        MUST (dmtfSoftwareElementRefs
        MAY (cimSoftwareRef $ dmtfComputerSystemRef)

4. DIT Content Rules

   The following DIT Content Rules apply to objects in this schema.
   These content rules reference not only auxiliary classes in this
   draft but auxiliary classes from other DMTF schemata [5, 6, 7, 8, 9]

      ( <oid-oc231> NAME 'dmtfApplicationSystemContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfApplicationSystem class'
        AUX (dmtfApplicationSystemSoftwareFeatureAuxClass)
      )

      ( <oid-oc232> NAME 'dmtfSoftwareElementContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfSoftwareElement class'
        AUX (dmtfDeviceSoftwareAuxClass $
          dmtfSoftwareFeatureSoftwareElementsAuxClass)
      )

      ( <oid-oc233> NAME 'dmtfSoftwareFeatureContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfSoftwareFeature class'
        AUX (dmtfOperatingSystemSoftwareFeatureAuxClass $
          dmtfSoftwareFeatureSoftwareElementsAuxClass $
          dmtfSoftwareFeatureServiceImplementationAuxClass $
          dmtfSoftwareFeatureSAPImplementationAuxClass $
          dmtfApplicationSystemSoftwareFeatureAuxClass)
      )

      ( <oid-oc235> NAME 'dmtfDirectorySpecificationContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfDirectorySpecification class'
        AUX (dmtfDirectorySpecificationFileAuxClass $
          dmtfToDirectorySpecificationAuxClass $
          dmtfFromDirectorySpecificationAuxClass)
      )

      ( <oid-oc242> NAME 'dmtfFileSpecificationContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfFileSpecification class'
        AUX (dmtfDirectorySpecificationFileAuxClass) cimSystemRef)
      )

      ( <oid-oc244> NAME 'dmtfActionContentRule'
        DESC 'shows what auxiliary classes may go with the dmtfAction
           class'
        AUX (dmtfActionSequenceAuxClass)
      )
      ( <oid-oc245> NAME 'dmtfDirectoryActionContentRule'
        DESC 'shows what auxiliary classes may go with the
           dmtfDirectoryAction class'
        AUX (dmtfToDirectoryActionAuxClass $
          dmtfFromDirectoryActionAuxClass)
      )

      ( <oid-oc248> NAME 'dmtfFileActionContentRule'
        DESC 'shows what auxiliary classes may go with the dmtfFileAction
           class'
        AUX (dmtfFromDirectorySpecificationAuxClass $
          dmtfFromDirectoryActionAuxClass)
      )

      ( <oid-oc249> NAME 'dmtfCopyFileActionContentRule'
        DESC 'shows what auxiliary classes may go with

INTERNET DRAFTLDAP Schema for the
           dmtfCopyFileAction class'
        AUX (dmtfToDirectorySpecificationAuxClass $
          dmtfToDirectoryActionAuxClass)
      )

5. DMTF Application CIM v2.1
ModelDecember 1999

4. References

   Request For Comments (RFC) and Internet Draft documents are available
   from numerous mirror sites.

         [1]         M. Wahl, T. Howes, S. Kille, "Lightweight Directory
                     Access Protocol (v3)," RFC 2251, Decemeber December 1997.

         [2]         M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight "Light-
                     weight Directory Access Protocol (v3): Attribute
                     Syntax Defini-
            tions," Definitions," RFC 2252, December 1997.

         [3]         Ryan Moats, Gerald Maziarski, John Strassner,
                     "Extensible Match Rule to Dereference Pointers",
                     Internet Draft (work in progress), June 1999.

         [4]         DMTF, "CIM Application Model, v2.2".

         [5]         Ryan Moats, Gerald Maziarski, John Strassner, "LDAP
                     Schema for the DMTF Core CIM v2.2 Model", September 1999.

[6]         Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
            for the DMTF Device CIM Model", September 1999.

[7]         Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
            for the DMTF Network CIM Model", October 1999.

[8]         Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
            for the DMTF System CIM Model", October 1999.

[9]         Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
            for the DMTF Physical CIM Model", October Internet
                     Draft (work in progress), December 1999.

6.

5. Author's Addresses

   Ryan Moats               Jerry Maziarski           John Strassner
   15621 Drexel Circle      Room C3-3Z01              Cisco Systems, Bldg 1
   Omaha, NE 68135          200 S. Laurel Ave.        170 West Tasman Drive
   USA                      Middletown, NJ 07748      San Jose, CA 95134
   E-mail: jayhawk@att.com  USA                       E-mail:
johns@cisco.com
                            E-mail: gfm@qsun.att.com