(file) Return to CIM_SystemSpecificCollection.mof CVS log (file) (dir) Up to [OMI] / omi / share / networkschema

 1 krisbash 1.1 // Copyright (c) 2008 DMTF.  All rights reserved.
 2                 [Version ( "2.19.0" ), 
 3                  UMLPackagePath ( "CIM::Core::Collection" ), 
 4                  Description ( 
 5                     "SystemSpecificCollection represents the general concept of a "
 6                     "collection that is scoped (or contained) by a System. It "
 7                     "represents a Collection that has meaning only in the context "
 8                     "of a System, a Collection whose elements are restricted by the "
 9                     "definition of the System, or both of these types of "
10                     "Collections. This meaning is explicitly described by the "
11                     "(required) association, HostedCollection. \n"
12                     "An example of a SystemSpecificCollection is a Fibre Channel "
13                     "zone that collects network ports, port groupings, and aliases "
14                     "(as required by a customer) in the context of an AdminDomain. "
15                     "The Collection is not a part of the domain, but merely an "
16                     "arbitrary grouping of the devices and other Collections in the "
17                     "domain. In other words, the context of the Collection is "
18                     "restricted to the domain, and its members are also limited by "
19                     "the domain." )]
20              class CIM_SystemSpecificCollection : CIM_Collection {
21              
22 krisbash 1.1       [Key, Override ( "InstanceID" ), 
23                     Description ( 
24                        "Within the scope of the instantiating Namespace, "
25                        "InstanceID opaquely and uniquely identifies an instance "
26                        "of this class. To ensure uniqueness within the "
27                        "NameSpace, the value of InstanceID should be constructed "
28                        "using the following \'preferred\' algorithm: \n"
29                        "<OrgID>:<LocalID> \n"
30                        "Where <OrgID> and <LocalID> are separated by a colon "
31                        "\':\', and where <OrgID> must include a unique name. It "
32                        "can be a copyrighted, trademarked, or otherwise unique "
33                        "name that is owned by the business entity that is "
34                        "creating or defining the InstanceID. Or, it could be a "
35                        "registered ID that is assigned to the business entity by "
36                        "a recognized global authority.(This requirement is "
37                        "similar to the <Schema Name>_<Class Name> structure of "
38                        "Schema class names.) In addition, to ensure uniqueness "
39                        "<OrgID> must not contain a colon (\':\'). When using "
40                        "this algorithm, the first colon to appear in InstanceID "
41                        "must appear between <OrgID> and <LocalID>. \n"
42                        "<LocalID> is chosen by the business entity and should "
43 krisbash 1.1           "not be re-used to identify different underlying "
44                        "(real-world) elements. If the above \'preferred\' "
45                        "algorithm is not used, the defining entity must ensure "
46                        "that the resulting InstanceID is not re-used as any of "
47                        "InstanceIDs produced by this or other providers for the "
48                        "NameSpace of this instance. \n"
49                        "For DMTF-defined instances, the \'preferred\' algorithm "
50                        "must be used with the <OrgID> set to \'CIM\'." )]
51                 string InstanceID;
52              
53              
54              };

ViewCVS 0.9.2