1 krisbash 1.1 // Copyright (c) 2008 DMTF.  All rights reserved.
 2                 [Abstract, Version ( "2.19.0" ), 
 3                  UMLPackagePath ( "CIM::Core::Settings" ), 
 4                  Description ( 
 5                     "CIM_SettingData is used to represent configuration and and "
 6                     "operational parameters for CIM_ManagedElement instances. There "
 7                     "are a number of different uses of CIM_SettingData supported in "
 8                     "the model today. Additional uses may be defined in the future.\n"
 9                     "Instances of CIM_SettingData may represent Aspects of a "
10                     "CIM_ManagedElement instance. This is modeled using the "
11                     "CIM_SettingsDefineState association. CIM_SettingData may be "
12                     "used to define capabilities when associated to an instance of "
13                     "CIM_Capabilities through the CIM_SettingsDefineCapabilities "
14                     "association. \n"
15                     "Instances of CIM_SettingData may represent different types of "
16                     "configurations for a CIM_ManagedElement, including persistent "
17                     "configurations, in progress configuration changes, or "
18                     "requested configurations. The CIM_ElementSettingData "
19                     "association is used to model the relationship between a "
20                     "CIM_SettingData instance and the CIM_ManagedElement for which "
21                     "it is a configuration. \n"
22 krisbash 1.1        "When an instance of CIM_SettingData represents a "
23                     "configuration, the current operational values for the "
24                     "parameters of the element are reflected by properties in the "
25                     "Element itself or by properties in its associations. These "
26                     "properties do not have to be the same values that are present "
27                     "in the SettingData object. For example, a modem might have a "
28                     "SettingData baud rate of 56Kb/sec but be operating at "
29                     "19.2Kb/sec. \n"
30                     "Note: The CIM_SettingData class is very similar to "
31                     "CIM_Setting, yet both classes are present in the model because "
32                     "many implementations have successfully used CIM_Setting. "
33                     "However, issues have arisen that could not be resolved without "
34                     "defining a new class. Therefore, until a new major release "
35                     "occurs, both classes will exist in the model. Refer to the "
36                     "Core White Paper for additional information. SettingData "
37                     "instances can be aggregated together into higher- level "
38                     "SettingData objects using ConcreteComponent associations." )]
39              class CIM_SettingData : CIM_ManagedElement {
40              
41                    [Key, Override ( "InstanceID" ), 
42                     Description ( 
43 krisbash 1.1           "Within the scope of the instantiating Namespace, "
44                        "InstanceID opaquely and uniquely identifies an instance "
45                        "of this class. To ensure uniqueness within the "
46                        "NameSpace, the value of InstanceID should be constructed "
47                        "using the following \"preferred\" algorithm: \n"
48                        "<OrgID>:<LocalID> \n"
49                        "Where <OrgID> and <LocalID> are separated by a colon "
50                        "(:), and where <OrgID> must include a copyrighted, "
51                        "trademarked, or otherwise unique name that is owned by "
52                        "the business entity that is creating or defining the "
53                        "InstanceID or that is a registered ID assigned to the "
54                        "business entity by a recognized global authority. (This "
55                        "requirement is similar to the <Schema Name>_<Class Name> "
56                        "structure of Schema class names.) In addition, to ensure "
57                        "uniqueness, <OrgID> must not contain a colon (:). When "
58                        "using this algorithm, the first colon to appear in "
59                        "InstanceID must appear between <OrgID> and <LocalID>. \n"
60                        "<LocalID> is chosen by the business entity and should "
61                        "not be reused to identify different underlying "
62                        "(real-world) elements. If the above \"preferred\" "
63                        "algorithm is not used, the defining entity must assure "
64 krisbash 1.1           "that the resulting InstanceID is not reused across any "
65                        "InstanceIDs produced by this or other providers for the "
66                        "NameSpace of this instance. \n"
67                        "For DMTF-defined instances, the \"preferred\" algorithm "
68                        "must be used with the <OrgID> set to CIM." )]
69                 string InstanceID;
70              
71                    [Required, Override ( "ElementName" ), 
72                     Description ( 
73                        "The user-friendly name for this instance of SettingData. "
74                        "In addition, the user-friendly name can be used as an "
75                        "index property for a search or query. (Note: The name "
76                        "does not have to be unique within a namespace.)" )]
77                 string ElementName;
78              
79              
80              };