Return to
CIM_XML_Mapping20.htm
CVS log
Up to [Pegasus] / dmtfdocs
|
Return to
CIM_XML_Mapping20.htm
CVS log
|
Up to [Pegasus] / dmtfdocs
|
|
File: [Pegasus] / dmtfdocs / CIM_XML_Mapping20.htm
(download)
/
(as text)
Revision: 1.1, Wed Sep 5 23:20:21 2001 UTC (22 years, 8 months ago) by karl Branch: MAIN CVS Tags: HEAD Import |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Specification for the Representation of CIM in XML</TITLE>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type>
<META content="MSHTML 5.00.2014.210" name=GENERATOR>
<LINK TYPE="text/css" REL=STYLESHEET href="cimxml.css"></LINK>
</HEAD>
<BODY>
<DL>
<DD>
<P class=CenterTitle>Distributed Management Task Force,
Inc.</P>
<P class=BigCenterTitle>Specification for the
Representation of CIM in XML</P>
<P class=CenterTitle>Version 2.0</P>
<P class=CenterTitle>July 20<SUP>th</SUP>, 1999</P>
<P align=justify>Technical inquiries and editorial
comments should be directed in writing to:</P>
<P align=center>Distributed Management Task Force, Inc.
(DMTF)</P>
<P align=center>c/o <A href="http://www.mkinc.com/"
>MacKenzie Kesselring, Inc.</A> <BR
>200 SW Market Street, Suite 450, <BR
>Portland, OR 97201 <BR>(503)
225-0725 <BR>(503) 225-0765 (fax) <BR
>email: <A href="mailto://dmtf-info@dmtf.org" >dmtf-info@dmtf.org</A> </P>
<H3>Participants</H3>
<DIR>
<DIR>
<P>This list shows the names of the companies and
organizations that have participated in the Distributed Management Task Force -
CIM TDC XML Sub-Committee whose contributions made this document possible.</P>
<UL>
<LI>Agranat Systems
<LI>Hewlett-Packard Company
<LI>Microsoft Corporation
<LI>Tivoli Systems, Inc.
<LI>Customer Support Consortium
<LI>Sun Microsystems, Inc.
<LI>Intel Corporation</LI></UL></DIR></DIR>
<H3>Change History</H3>
<DIV align=center>
<TABLE border=1 class=ChangeHistory>
<TBODY>
<TR>
<TD width="17%">Version 1.0a</TD>
<TD width="30%">Tuesday, July 14th, 1998</TD>
<TD width="52%">First Draft Release</TD></TR>
<TR>
<TD>Version 1.0b</TD>
<TD>Friday August 7th, 1998</TD>
<TD>Draft Release</TD></TR>
<TR>
<TD>Version 1.0c</TD>
<TD>Friday August 28th, 1998</TD>
<TD>Updated Version during Company review</TD></TR>
<TR>
<TD>Version 1.0</TD>
<TD>Tuesday, September 15th, 1998</TD>
<TD>Final version</TD></TR>
<TR>
<TD>Version 1.0.1</TD>
<TD>Friday, January 22nd, 1999</TD>
<TD>METHOD subelement removed from
ASSOCIATION.INSTANCE</TD></TR>
<TR>
<TD>Version 1.1a</TD>
<TD>Wednesday, April 28th, 1999</TD>
<TD>Changes for support of HTTP protocol</TD></TR>
<TR>
<TD>Version 2.0b</TD>
<TD>May 7th, 1999</TD>
<TD>Updates after first Working Group Review</TD></TR>
<TR>
<TD>Version 2.0c</TD>
<TD>May 11th, 1999</TD>
<TD>DTD Corrections, changes to DECLGROUP and removal of IMPLICITKEY
element</TD></TR>
<TR>
<TD>Version 2.0d</TD>
<TD>May 20th, 1999</TD>
<TD>Corrected error in definition of LOCALINSTANCEPATH</TD></TR>
<TR>
<TD>Version 2.0e</TD>
<TD>May 25th, 1999</TD>
<TD>
<P>Corrected LOCALNAMESPACEPATH definition<BR>Corrected CIMName entity
definition<BR>Changed LOCAL to PROPAGATED<BR>Added
VALUETYPE attribute to KEYVALUE<BR>Added explanatory text
concerning pragmas</P></TD></TR>
<TR>
<TD>Version 2.0f</TD>
<TD>May 28th, 1999</TD>
<TD>
<P>Corrected VALUE.REFERENCE, KEYVALUE.REFERENCE and
PARAMVALUE.REFERENCE so that they could contain relative and absolute
paths</P></TD></TR>
<TR>
<TD>Version 2.0</TD>
<TD>June 2nd, 1999</TD>
<TD>
<P>Updated document references<BR>Removed references to
CIM_Object</P></TD></TR>
<TR>
<TD></TD>
<TD>July 6th, 1999</TD>
<TD>
<P>Remove INSTANCE attribute from SCOPE element<BR>Simplify method
parameter declaration elements<BR>Replace KEYVALUE.REFERENCE by
VALUE.REFERENCE<BR>Add ARRAYSIZE attribute to
QUALIFIER.DECLARATION<BR>Remove ASSOCIATION elements</P></TD></TR>
<TR>
<TD> </TD>
<TD>July 20th, 1999</TD>
<TD>
<P>Updated IPARAMVALUE and IRETURNVALUE
elements<BR>
Added
VALUE.NAMEDINSTANCE element</P>
</TD></TR></TBODY></TABLE>
<CENTER></CENTER></DIV>
<H3><A name=SecContents>Contents</A></H3>
<DL>
<DD><A href="#SecAbstract" >Abstract</A>
<DD><A href="#SecIntroduction" >1. Introduction</A>
<DL>
<DD><A href="#SecANoteOnRenderingToMOF" >1.1. A Note
on Rendering to MOF</A>
<DD><A href="#SecTerminology" >1.2. Terminology</A>
<DD><A href="#SecStyle" >1.3. Style</A> </DD></DL>
<DD><A href="#SecANoteOnMappingChoices">2. A Note On
Mapping Choices</A>
<DL>
<DD><A href="#SecCIMTerminology">2.1. CIM Terminology</A></DD></DL>
<DD><A href="#SecTheCIMXMLSchemaReference">3. The CIM
XML Schema Reference</A>
<DL>
<DD><A href="#SecEntityDescriptions">3.1. Entity
Descriptions</A>
<DL>
<DD><A href="#SecCIMName">3.1.1. CIMName</A>
<DD><A href="#SecCIMType">3.1.2. CIMType</A>
<DD><A href="#SecQualifierFlavor">3.1.3.
QualifierFlavor</A>
<DD><A href="#SecClassOrigin">3.1.4. ClassOrigin</A>
<DD><A href="#SecPropagated">3.1.5.
Propagated</A>
<DD><A href="#SecArraySize">3.1.6. ArraySize</A>
<DD><A href="#SecSuperClass">3.1.7. SuperClass</A>
<DD><A href="#SecClassName">3.1.8. ClassName</A>
<DD><A href="#SecReferenceClass">3.1.9.
ReferenceClass</A></DD></DL>
<DD><A href="#SecElementDescriptions">3.2. Element
Descriptions</A>
<DL>
<DD><A href="#SecTopLevelElements">3.2.1. Top Level
Elements</A>
<DL>
<DD><A href="#SecCIM">3.2.1. CIM</A></DD></DL>
<DD><A href="#SecDeclarationElements">3.2.2.
Declaration Elements</A>
<DL>
<DD><A href="#SecDECLARATION">3.2.2.1. DECLARATION</A>
<DD><A href="#SecDECLGROUP">3.2.2.2. DECLGROUP</A>
<DD><A href="#SecDECLGROUPWITHNAME">3.2.2.3.
DECLGROUP.WITHNAME</A>
<DD><A href="#SecDECLGROUPWITHPATH">3.2.2.4.
DECLGROUP.WITHPATH</A>
<DD><A href="#SecQUALIFIERDECLARATION">3.2.2.5.
QUALIFIER.DECLARATION</A>
<DD><A href="#SecSCOPE">3.2.2.6. SCOPE</A></DD></DL>
<DD><A href="#SecValueElements">3.2.3. Value
Elements</A>
<DL>
<DD><A href="#SecVALUE">3.2.3.1. VALUE</A>
<DD><A href="#SecVALUEARRAY">3.2.3.2. VALUE.ARRAY</A>
<DD><A href="#SecVALUEREFERENCE">3.2.3.3.
VALUE.REFERENCE</A>
<DD><A href="#SecVALUEREFARRAY">3.2.3.4.
VALUE.REFARRAY</A>
<DD><A href="#SecVALUEOBJECT">3.2.3.5. VALUE.OBJECT</A>
<DD><A href="#SecVALUENAMEDINSTANCE">3.2.3.6. VALUE.NAMEDINSTANCE</A>
<DD><A href="#SecVALUENAMEDOBJECT">3.2.3.7.
VALUE.NAMEDOBJECT</A>
<DD><A href="#SecVALUEOBJECTWITHPATH">3.2.3.8.
VALUE.OBJECTWITHPATH</A>
<DD><A
href="#SecVALUEOBJECTWITHLOCALPATH">3.2.3.9.
VALUE.OBJECTWITHLOCALPATH</A></DD></DL>
<DD><A href="#SecNamingAndLocationElements">3.2.4.
Naming and Location Elements</A>
<DL>
<DD><A href="#SecNAMESPACEPATH">3.2.4.1.
NAMESPACEPATH</A>
<DD><A href="#SecLOCALNAMESPACEPATH">3.2.4.2.
LOCALNAMESPACEPATH</A>
<DD><A href="#SecHOST">3.2.4.3. HOST</A>
<DD><A href="#SecNAMESPACE">3.2.4.4. NAMESPACE</A>
<DD><A href="#SecCLASSPATH">3.2.4.5. CLASSPATH</A>
<DD><A href="#SecLOCALCLASSPATH">3.2.4.6.
LOCALCLASSPATH</A>
<DD><A href="#SecCLASSNAME2">3.2.4.7. CLASSNAME</A>
<DD><A href="#SecINSTANCEPATH">3.2.4.8. INSTANCEPATH</A>
<DD><A href="#SecLOCALINSTANCEPATH">3.2.4.9.
LOCALINSTANCEPATH</A>
<DD><A href="#SecINSTANCENAME">3.2.4.10. INSTANCENAME</A>
<DD><A href="#SecOBJECTPATH" >3.2.4.11. OBJECTPATH</A>
<DD><A href="#SecKEYBINDING" >3.2.4.12. KEYBINDING</A>
<DD><A href="#SecKEYVALUE" >3.2.4.13. KEYVALUE</A></DD></DL>
<DD><A href="#SecObjectDefinitionElements" >3.2.5.
Object Definition Elements</A>
<DL>
<DD><A href="#SecCLASS" >3.2.5.1. CLASS</A><A href="#SecQUALIFIER" >
<DD></A><A href="#SecINSTANCE" >3.2.5.2.
INSTANCE</A><A href="#SecQUALIFIER" ></A><A href="#SecQUALIFIER" >
<DD>3.2.5.3. QUALIFIER</A>
<DD><A href="#SecPROPERTY" >3.2.5.4. PROPERTY</A>
<DD><A href="#SecPROPERTYARRAY" >3.2.5.5.
PROPERTY.ARRAY</A>
<DD><A href="#SecPROPERTYREFERENCE" >3.2.5.6.
PROPERTY.REFERENCE</A><A href="#SecMETHOD" >
<DD>3.2.5.7. METHOD</A>
<DD><A href="#SecPARAMETER" >3.2.5.8. PARAMETER</A>
<DD><A href="#SecPARAMETERREFERENCE" >3.2.5.9.
PARAMETER.REFERENCE</A>
<DD><A href="#SecPARAMETERARRAY" >3.2.5.10.
PARAMETER.ARRAY</A>
<DD><A href="#SecPARAMETERREFARRAY" >3.2.5.11.
PARAMETER.REFARRAY</A></DD></DL>
<DD><A href="#SecMessageElements" >3.2.6. Message
Elements</A>
<DL>
<DD><A href="#SecMESSAGE" >3.2.6.1. MESSAGE</A>
<DD><A href="#SecMULTIREQ" >3.2.6.2. MULTIREQ</A>
<DD><A href="#SecSIMPLEREQ" >3.2.6.3. SIMPLEREQ</A>
<DD><A href="#SecMETHODCALL" >3.2.6.4. METHODCALL</A>
<DD><A href="#SecPARAMVALUE" >3.2.6.5. PARAMVALUE</A>
<DD><A href="#SecIMETHODCALL" >3.2.6.6.
IMETHODCALL</A>
<DD><A href="#SecIPARAMVALUE" >3.2.6.7.
IPARAMVALUE</A>
<DD><A href="#SecMULTIRSP" >3.2.6.8. MULTIRSP</A>
<DD><A href="#SecSIMPLERSP" >3.2.6.9. SIMPLERSP</A>
<DD><A href="#SecMETHODRESPONSE" >3.2.6.10.
METHODRESPONSE</A>
<DD><A href="#SecIMETHODRESPONSE" >3.2.6.11.
IMETHODRESPONSE</A>
<DD><A href="#SecERROR" >3.2.6.12. ERROR</A>
<DD><A href="#SecRETURNVALUE" >3.2.6.13.
RETURNVALUE</A>
<DD><A href="#SecIRETURNVALUE" >3.2.6.14.
IRETURNVALUE</A></DD></DL></DD></DL></DD></DL>
<DD><A href="#SecReferences" >4. References</A> </DD></DL>
<P></P></DD></DL>
<H1><A name=SecAbstract>Abstract</A></H1>
<P>The <A href="http://www.w3.org/TR/REC-xml">Extensible Markup Language</A> (XML) is a simplified subset
of SGML that offers powerful and extensible data modeling capabilities. An <I>XML Document</I> is a collection of data represented in
XML. An <I>XML Schema</I> is a grammar that describes the
format of an XML Document. An XML Document is described as <I>valid</I> if it has an associated XML Schema to which it
conforms.</P>
<P>The <A href="http://dmtf.org/spec/cims.html">Common Information Model</A> (CIM) is an object-oriented
information model defined by the Distributed Management Task Force (DMTF) which
provides a conceptual framework for describing management data.</P>
<P>This document defines a standard for the
representation of Common Information Model (CIM) elements and messages
in XML.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H1><A name=SecIntroduction>1.
Introduction</A></H1>
<P>This document defines an XML grammar, written in DTD
(Document Type Definition), which can be used both to represent CIM declarations
(Classes, Instances and Qualifiers) and CIM Messages for use by the CIM mapping
onto HTTP [9].</P>
<P>For convenience the complete unannotated DTD is
available as a separate document [11].</P>
<P>There are potentially many different ways in which CIM
information could be represented within XML. In the interests of
interoperability between different implementations of CIM there is an obvious
requirement for standardization of this representation. The following criteria
have been applied in the design of the representation presented here:
<UL>
<LI>Fully standardized technologies are used wherever
possible, in preference to Working Drafts. Where use is made of a Working
Draft, the intention is to track the changes to the Working Draft in this
specification.
<LI>Completeness is favored over conciseness (all aspects
of CIM should be modeled). </LI></UL>
<P>Whilst this document makes no restrictions on the use of
this mapping, it is recognized that a number of possible usage scenarios exist
for which the mapping should cater:
<OL>
<LI>XML documents conforming to this mapping that express
CIM declarations should be capable of being rendered or transformed using
standard techniques into other formats. In particular the mapping should
contain sufficient information to be rendered into MOF (Managed Object Format)
syntax [1].
<LI>The mapping should be applicable to the wire-level
representation of CIM Operations defined by the CIM mapping onto
HTTP [9]. </LI></OL>
<P><A href="#SecContents" >Back to contents</A></P>
<H2><A name=SecANoteOnRenderingToMOF>1.1. A Note On Rendering to MOF</A></H2>
<P>Currently the W3C is still investigating the mechanisms
by which XML documents are rendered. The available technologies include CSS
(Cascading Style Sheets) [<A href="#RefCSS1" >6</A>,<A href="#RefCSS2" >7</A>] and XSL (Extensible Style Sheet Language) [<A href="#RefXSL" >8</A>].</P>
<P>CSS is already established in the HTML/SGML domain, but
is limited in the nature of transformations that it can express, being
essentially a formatting technology that can alter the appearance of individual
elements but cannot reorganize them. The XSL proposal attempts to address
the shortcomings of CSS by providing more sophisticated reordering
and formatting capabilities.</P>
<P>The subset of the DTD for CIM presented in this
specification concerned with object declarations (identified by the element <A href="#SecDECLARATION" >DECLARATION</A> ) is intended to allow
expression of CIM objects in XML sufficient for rendering into a number of
formats, of which MOF is one.</P>
<P>The semantic content of a MOF file is fully captured by
the DTD presented herein, so that it is possible to express any MOF conformant
to [1] in an equivalent XML representation using this DTD. This
includes the ability to express any of the standard MOF pragmas defined in [1],
with the exception of the locale and instancelocale pragmas (which is a subject
for further study in the context of localization support within CIM).</P>
<P>Note that the Processing Instruction (PI) mechanism
defined by XML is the means by which bespoke pragmas may be added to an XML
document in an analagous manner to the #pragma extension mechanism defined for
MOF. The format of such PIs is necessarily outside the scope of this
document.</P>
<P>CSS alone is not sufficient to provide a rendering of
CIM XML declarations into MOF. XSL is capable of doing this, but due to
the fact that it is not yet a full W3C recommendation, a standard
stylesheet for MOF cannot be given at this time. Instead it is the
intention to publish a companion document to this document which defines a
MOF stylesheet based on the latest available XSL working draft, and to continue
to track XSL as it evolves to a full recommendation.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H2><A name=SecTerminology>1.2.
Terminology</A></H2>
<P>The key phrases and words MUST, MUST NOT, REQUIRED,
SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY and OPTIONAL in this
document are to be interpreted as described in RFC 2119 [10].</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H2><A name=SecStyle>1.3.
Style</A></H2>
<P>This document uses a number of stylistic conventions to
highlight examples and definitions.</P>
<P>Examples are displayed in this fashion:</P>
<P>
<TABLE class=Example>
<TR>
<TD>This is an example</TD></TR></TABLE></P>
<P>Definitions are illustrated thusly:</P>
<P>
<TABLE class=Definition>
<TR>
<TD>This is a definition</TD></TR></TABLE></P>
<P><A href="#SecContents" >Back to contents</A></P>
<H1><A name=SecANoteOnMappingChoices></A>2. A Note on Mapping Choices</H1>
<P>There are two fundamentally different models for mapping
CIM in XML:
<UL>
<UL>
<LI>A <I>Schema Mapping</I> is one
in which the XML Schema is used to describe the CIM classes, and CIM
Instances are mapped to valid XML Documents for that schema. (Essentially
this means that each CIM class generates its own DTD fragment, the XML
element names of which are taken directly from the corresponding CIM element
names.)
<LI>A <I>Metaschema Mapping</I> is
one in which the XML schema is used to describe the CIM metaschema, and both
CIM classes and instances are valid XML documents for that schema. (In other
words the DTD is used to describe in a generic fashion the notion of a CIM
class or instance. CIM element names are mapped to XML attribute or element
values, rather than XML element names.) </LI></UL></UL>
<P>Although there are obvious benefits to employing a
schema mapping (more validation power, and a slightly more intuitive
representation of CIM in XML), the metaschema mapping is adopted here for the
following reasons:
<UL>
<UL>
<LI>It only requires one standardized metaschema DTD
for CIM, rather than an unbounded number of DTDs. This considerably reduces
the complexity of management and administration of XML mappings.
<LI>XML DTD does not allow an unordered list of
elements. In a static mapping this would mean either:
<UL>
<LI>Fixing an arbitrary order for property, method
and qualifier lists (making it harder for a receiving application to
process), or;
<LI>Defining a very unwieldy mapping which took
account of all list orderings explicitly (and whose size would grow
exponentially with the number of list elements). </LI></UL>
<LI>In a schema mapping, the names of CIM schema
elements (class, property, qualifier and method names) populate the XML
element namespace. In order to replicate the scoping rules on CIM element
names within XML DTD, it would be necessary to employ XML Namespaces [<A href="#NamespaceRef" >3</A>] to define XML Schema to per-property
level of granularity. This would be extremely cumbersome to administer and
process. A metaschema mapping only introduces a small, fixed number of terms
into the XML element namespace (such as "Class", "Instance", "Property", and
so forth). As an alternative to the introduction of additional XML
Namespaces, some renaming of CIM elements could be used (for example,
prefixing a qualifier name with the name of its owning property and its
owning class), but this would result in XML documents that were verbose and
difficult to understand.
<LI>Although a schema mapping could allow XML-based
validation of instances against classes, this would only be possible if the
entire class hierarchy were flattened prior to mapping the CIM Class to an
XML Schema. If this flattening were not performed then inherited properties
may be absent from the DTD, which would cause validation to fail against an
instance that included the value of an inherited property. </LI></UL></UL>
<P><A href="#SecContents" >Back to contents</A></P>
<H2><A name=SecCIMTerminology>2.1. CIM
Terminology</A></H2>
<P>Throught this document the term <EM>CIM Element</EM> is used to describe one of the following
components of the CIM meta-model: Namespace, Class, Property, Method or
Qualifier.</P>
<P>The term <EM>XML Element</EM> is
used to describe a component of XML defined using the ELEMENT construct in DTD.
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H1><A name=SecTheCIMXMLSchemaReference>3. The CIM XML Schema Reference</A></H1>
<H2><A name=SecEntityDescriptions>3.1.
Entity Descriptions</A></H2>
<P>This section describes each of the parameter entities
used in the CIM XML Schema vocabulary. The use of Parameter Entities has been
adopted to highlight common features of the DTD.</P>
<P><A href="#SecContents" >Back to contents</A> </P>
<H3><A name=SecCIMName>3.1.1.
CIMName</A></H3>
<P>The CIMName entity describes the name of a CIM Element
(Class, Instance, Method, Property,Qualifier or Parameter). The value MUST
be a legal CIM element name [1].</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ENTITY % CIMName "NAME
CDATA #REQUIRED"></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H3><A name=SecCIMType>3.1.2.
CIMType</A></H3>
<P>The CIMType entity describes the allowed type
descriptions for a non-reference CIM Property, CIM Qualifier or non-reference
CIM Method Parameter.</P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ENTITY % CIMType "TYPE <BR
>
(boolean|string|char16|uint8|uint16|sint16|uint32|sint32|uint64|sint64|datetime|real32|real64)"></CODE></TD></TR></TBODY></TABLE>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H3><A name=SecQualifierFlavor>3.1.3.
QualifierFlavor</A></H3>
<P>The QualifierFlavor entity describes the flavor settings
for a CIM Qualifier, modeled as XML attributes.</P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ENTITY %
QualifierFlavor "OVERRIDABLE (true|false) 'true'<BR
>
TOSUBCLASS (true|false) 'true'<BR
>
TOINSTANCE (true|false) 'false'<BR
>
TRANSLATABLE
(true|false) 'false'"></FONT></TD></TR></TBODY></TABLE>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H3><A name=SecClassOrigin>3.1.4.
ClassOrigin</A></H3>
<P>The ClassOrigin entity describes the originating Class
of a CIM Property or Method. </P>
<P>The <FONT face="Courier New">CLASSORIGIN </FONT>attribute defines the name of the
originating class (the Class in which the Property or Method was first defined)
of the CIM element represented by the XML element to which the attribute is
attached.</P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ENTITY %
ClassOrigin "CLASSORIGIN CDATA
#IMPLIED"></FONT></TD></TR></TBODY></TABLE>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H3><A name=SecLocal>3.1.5.</A> <A name=SecPropagated>Propagated</A></H3>
<P>The Propagated entity is a convenient shorthand for
the <FONT face="Courier New">PROPAGATED</FONT> attribute,
which may apply to a CIM Property, Method or Qualifier. </P>
<P>This attribute indicates whether the definition of the
CIM Property, Qualifier or Method is local to the CIM Class
(respectively, Instance) in which it appears, or was propagated without
modification from the underlying Subclass (respectively, Class), as defined by
[1]. </P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 id=TABLE6 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ENTITY
% Propagated "PROPAGATED
(true|false) 'false'"></FONT></TD></TR></TBODY></TABLE></P>
<P>Uses of the <FONT face="Courier New">PROPAGATED</FONT> attribute include:</P>
<UL>
<LI>To facilitate the rendering of CIM XML declarations
into MOF syntax, which by convention only describes local overrides in a CIM
Subclass or Instance.
<LI>To filter XML representations of CIM Classes or
Instances so that they can be returned as responses to CIM Operation
requests [9] which require only local elements.</LI></UL>
<P><FONT face=Verdana><A href="#SecContents" >Back to
contents</FONT></A></FONT></P>
<P><A href="#SecContents" ></FONT></A></P>
<H3><A name=SecArraySize>3.1.6.
ArraySize</A></H3>
<P>The ArraySize entity is a convenient shorthand for the
<FONT face="Courier New">ARRAYSIZE</FONT> attribute, which
may apply to a PROPERTY.ARRAY, PARAMETER.ARRAY or PARAMETER.REFARRAY
element.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 id=TABLE1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ENTITY
% ArraySize "ARRAYSIZE
CDATA #IMPLIED"></FONT></TD></TR></TBODY></TABLE></P><FONT face=Verdana>
<P>The <FONT face="Courier New">ARRAYSIZE</FONT> attribute defines the size of the array in
the case that it is constrained to a fixed number of elements. The value of this
attribute (if it is present) must be a positive integer.</P>
<P><A href="#SecContents" >Back to contents</A></P></FONT>
<H3><H3<A name="SecSuperClass">3.1.7.
<A name=SecSuperClass>SuperClass</A> </A></H3><FONT
face=Verdana>
<H3></H3>
<P>The SuperClass entity is a convenient shorthand for
the <FONT face="Courier New">SUPERCLASS</FONT>
attribute.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 id=TABLE1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ENTITY
% SuperClass "SUPERCLASS CDATA
#IMPLIED"></FONT></TD></TR></TBODY></TABLE></P><FONT face=Verdana>
<P>This attribute defines the name of the superclass.
Where it is omitted, it MUST be inferred that the owning element has no
superclass.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H3><A name=SecClassName>3.1.8.
ClassName</A></H3>
<P>The ClassName entity is a convenient shorthand for
the <FONT face="Courier New">CLASSNAME</FONT> attribute.
The value MUST be a legal CIM Class name [1].</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 id=TABLE1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ENTITY
% ClassName "CLASSNAME
CDATA #REQUIRED"></FONT></TD></TR></TBODY></TABLE></P><FONT
face=Verdana>
<P><A href="#SecContents" >Back to contents</A></P>
<H3><A name=SecReferenceClass>3.1.9.
ReferenceClass</A></H3>
<P>The ReferenceClass entity is a convenient shorthand
for the <FONT face="Courier New">REFERENCECLASS</FONT>
attribute. If present, the value MUST be a legal CIM Class name [1].</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 id=TABLE1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ENTITY
% ReferenceClass "REFERENCECLASS CDATA
#IMPLIED"></FONT></TD></TR></TBODY></TABLE></P><FONT face=Verdana>
<P>The value defines the strong type of a CIM reference
type. If absent, it MUST be inferred that the owning element is not a
strong reference type.</P>
<P><A href="#SecContents" >Back to
contents</A></P></FONT></FONT></FONT></FONT>
<H2><A name=SecElementDescriptions>3.2. Element Descriptions</A></H2>
<P>This section describes each of the elements in the CIM
XML Schema.</P>
<H3>3.2.1. <A name=SecTopLevelElements>Top Level Elements</A></H3>
<P>This section defines the root element of the XML Schema
for CIM.</P>
<P><A href="#SecContents" >Back to contents</A></P></FONT>
<H4><A name=SecCIM>3.2.1.1.
CIM</A></H4>
<P>The CIM element is the root element of every XML
Document that is valid with respect to this schema.</P>
<P>Each document takes one of two forms; it either contains
a single <A href="#SecMESSAGE" >MESSAGE</A> element defining a CIM message (to be
used in the HTTP mapping defined in [9]), or it contains a <A href="#SecDECLARATION" >DECLARATION</A> element used to declare a set of
CIM objects.</P>
<TABLE border=1 cellPadding=5 cellSpacing=1 style="LEFT: 10px; TOP: 5907px"
width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT CIM (<A href="#SecMESSAGE" >MESSAGE</A></CODE><FONT
face="Courier New"><FONT size=2
>|<A href="#SecDECLARATION" >DECLARATION</A></FONT></FONT><FONT size=3
><CODE>)><BR
><!ATTLIST CIM<BR
> CIMVERSION CDATA
#REQUIRED <BR
> DTDVERSION CDATA
#REQUIRED></CODE></FONT></TD></TR></TBODY></TABLE>
<P>The <FONT face="Courier New">CIMVERSION</FONT> attribute defines the earliest version of
the CIM Specification to which the XML Document conforms. It MUST be set to
"2.0".</P>
<P>The <FONT face="Courier New">DTDVERSION</FONT> attribute defines the version of the CIM
XML Mapping to which the XML Document conforms. It MUST be set to "2.0" to
conform to this version of the specification.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H3>3.2.2. <A name=SecDeclarationElements>Declaration Elements</A></H3>
<P>This section defines those elements of the Schema that
are concerned with expressing the declaration of CIM objects.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecDECLARATION>3.2.2.1.
DECLARATION</A></H4>
<P>The DECLARATION element defines a set of one or more
declarations of CIM objects. These are partitioned into logical
declaration subsets.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 id=TABLE8 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT </CODE><FONT face="Courier New"
><FONT size=2>DECLARATION
(<A href="#SecDECLGROUP" >DECLGROUP</A>|<A href="#SecDECLGROUPWITHNAME" >DECLGROUP.WITHNAME</A>|<A href="#SecDECLGROUPWITHPATH" >DECLGROUP.WITHPATH</A>)+<CODE
></FONT></FONT>></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecDECLGROUP>3.2.2.2.
DECLGROUP</A></H4>
<P>The DECLGROUP element defines a logical set of
CIM Class, Instance and Qualifier declarations. It MAY
optionally include a <A href="#SecNAMESPACEPATH" >NAMESPACEPATH</A> or <A href="#SecLOCALNAMESPACEPATH" >LOCALNAMESPACEPATH</A> element which, if
present, defines the common namespace in which all objects within the group
are declared.</P>
<P>The objects within the group are CIM
Classes, Instances and Qualifiers. </P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT </CODE><FONT face="Courier New"
><FONT size=2>DECLGROUP
((<A href="#SecLOCALNAMESPACEPATH" >LOCALNAMESPACEPATH</A>|<A href="#SecNAMESPACEPATH" >NAMESPACEPATH</A>)?,<A href="#SecQUALIFIERDECLARATION" >QUALIFIER.DECLARATION</A>*,<A href="#SecVALUEOBJECT" >VALUE.OBJECT</A>*)></FONT></FONT></TD></TR></TBODY></TABLE>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<P><A href="#SecContents" ></FONT></A></P>
<H4>3.2.2.3. <A name=SecDECLGROUPWITHNAME>DECLGROUP.WITHNAME</A></H4>
<P>The DECLGROUP.WITHNAME element defines a logical set of
CIM Class, Instance and Qualifier declarations. It MAY
optionally include a <A href="#SecNAMESPACEPATH" >NAMESPACEPATH</A> or <A href="#SecLOCALNAMESPACEPATH" >LOCALNAMESPACEPATH</A> element which, if
present, defines the common namespace in which all objects within the group
are declared.</P>
<P>The objects within the group are CIM
Classes, Instances and Qualifiers. </P>
<P>This element extends the DECLGROUP element in the sense
that any Instance declaration contains an explicit Instance Name (i.e. a Model
Path in the terms of the CIM specification [1]).</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT </CODE><FONT face="Courier New"
><FONT size=2
>DECLGROUP.WITHNAME ((<A href="#SecLOCALNAMESPACEPATH" >LOCALNAMESPACEPATH</A>|<A href="#SecNAMESPACEPATH" >NAMESPACEPATH</A>)?,<A href="#SecQUALIFIERDECLARATION" >QUALIFIER.DECLARATION</A>*,<CODE
></FONT></FONT><A href="#SecVALUENAMEDOBJECT" >VALUE.NAMEDOBJECT</A>*)></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4>3.2.2.4. <A name=#SecDECLGROUPWITHPATH>DECLGROUP.WITHPATH</A></H4>
<P>The DECLGROUP.WITHPATH element defines a logical set of
CIM Class and Instance declarations. Each object is declared with its
own independent naming and location information. </P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT </CODE><FONT face="Courier New"
><FONT size=2
>DECLGROUP.WITHPATH (<A href="#SecVALUEOBJECTWITHPATH" >VALUE.OBJECTWITHPATH</A>|<A href="#SecVALUEOBJECTWITHLOCALPATH" >VALUE.OBJECT</A><CODE
></FONT></FONT><A href="#SecVALUEOBJECTWITHLOCALPATH" >WITHLOCALPATH</A>)*></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecQUALIFIERDECLARATION>3.2.2.5. QUALIFIER.DECLARATION</A></H4>
<P>The QUALIFIER.DECLARATION element defines a single CIM
Qualifier declaration. </P>
<P>The declaration MAY include a default value. If
the Qualifier has a non-array type, it contains a single <A href="#SecVALUE" >VALUE</A> element representing
the value of the Qualifier. If the Qualifier has an array type, it contains a
single <A href="#SecVALUEARRAY" >VALUE.ARRAY</A> element to represent the
value.</P>
<P>The <A href="#SecSCOPE" >SCOPE</A> subelement, if present, defines the valid
set of scopes for this Qualifier. If absent it implies that there is no
restriction on the scope at which the Qualifier may be applied (so that it has
'any' scope in the terminology of CIM [1]).</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 style="LEFT: 0px; TOP: -1px"
width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT
QUALIFIER.DECLARATION (<A href="#SecSCOPE" >SCOPE</A>?,(<A href="#SecVALUE" >VALUE</A>|<A href="#SecVALUEARRAY" >VALUE.ARRAY</A>)?)><BR
><!ATTLIST QUALIFIER.DECLARATION <BR
> <A href="#SecCIMName" >%CIMName;</A><BR
> <A href="#SecCIMType" >%CIMType;</A>
#REQUIRED <BR
>
ISARRAY (true|false)
#IMPLIED<BR
> <A href="#SecArraySize" >%ArraySize;</A><BR
> <A href="#SecQualifierFlavor" >%QualifierFlavor;</A>></FONT><CODE
> </CODE></TD></TR></TBODY></TABLE><FONT face=Verdana size=2></P></FONT>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the Qualifier,
and the <FONT face="Courier New">TYPE</FONT> and <FONT
face="Courier New">ISARRAY</FONT> attributes together
define the CIM Type. The <FONT face="Courier New">ISARRAY</FONT> attribute MUST be present if
the Qualifier declares no default value, in order to infer whether the
Qualifier has an array type or not. The <FONT face="Courier New">ISARRAY</FONT> attribute SHOULD be absent if the Qualifier
declares a default value, as in this case whether the Qualifier has an array
type can be deduced from whether a VALUE or VALUE.ARRAY element is used to
declare that default; if present its value MUST be consistent with the declared
Qualifier default value.</P>
<P>The <FONT face="Courier New">ARRAYSIZE</FONT> attribute MUST NOT be present if the value
of the <FONT face="Courier New">ISARRAY</FONT> attribute is
<FONT face="Courier New">true</FONT>. If the <FONT
face="Courier New">ARRAYSIZE</FONT> attribute
is present, this indicates that the values taken by this Qualifier MUST be
of the size specified by the value of this attribute.</P>
<P>The flavor attributes declared using the QualifierFlavor
entity define the propogation and override semantics for the Qualifier.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecSCOPE>3.2.2.6.
SCOPE</A></H4>
<P>The SCOPE element defines the scope of a <A href="#SecQUALIFIERDECLARATION" >QUALIFIER.DECLARATION</A> in the case
that there are restrictions on the scope of the Qualifier declaration. </P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 style="LEFT: 0px; TOP: -1px"
width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT SCOPE
EMPTY><BR><!ATTLIST SCOPE <BR
> CLASS
(true|false) 'false'<BR
> ASSOCIATION
(true|false) 'false'<BR
> REFERENCE
(true|false) 'false'<BR
> PROPERTY (true|false)
'false'<BR
> METHOD
(true|false) 'false'<BR
> PARAMETER
(true|false) 'false'<BR
> INDICATION (true|false)
'false'></FONT><CODE>
</CODE></TD></TR></TBODY></TABLE><FONT face=Verdana size=2></P></FONT>
<P>The attributes define which scopes are valid. A
SCOPE element MUST declare at least one attribute with a true value (otherwise
the Qualifier would have no applicable scope). </P>
<P><A href="#SecContents" >Back to contents</A></P>
<H3>3.2.3. <A name=SecVALUEELEMENTS>Value Elements</A></H3>
<P>This section defines those elements of the Schema that
are concerned with expressing the value of CIM objects.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecVALUE>3.2.3.1.
VALUE</A></H4>
<P>The VALUE element is used to define a single (non-array
and non-reference) CIM Property value, CIM Qualifier value, or a CIM Method
Parameter value. </P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 style="LEFT: 10px; TOP: 5960px"
width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT VALUE
(#PCDATA)></CODE></TD></TR></TBODY></TABLE></P>
<P>Values are not type-validatable using DTD, so each value
appears in PCDATA format irrespective of the type. The TYPE attribute of the
parent element will determine the (CIM) type of the value. The format of the
PCDATA content depends on the CIM type, and is described in what follows.</P>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<P><STRONG>String
Values</STRONG></P>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<P>If the CIM type is <FONT face="Courier New"
>string</FONT>, then the PCDATA value MUST be a sequence
of zero or more UCS-2 characters. The value MUST NOT be surrounded by string
delimiter characters (such as double-quote or single-quote). The actual
representation of characters depends on the <FONT face="Courier New"
>encoding</FONT> attribute defined for the <FONT
face="Courier New"><?xml></FONT> processing
instruction. </P>
<P>If this value contains reserved XML characters, then
it MUST be escaped using standard XML character escaping mechanisms.
</P></BLOCKQUOTE>
<P><STRONG>Character
Values</STRONG></P>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<P>If the CIM type is <FONT face="Courier New"
>char</FONT>, then the PCDATA value MUST be a single
UCS-2 character. The value MUST NOT be surrounded by single-quote
characters. If this value is a reserved XML character, then it MUST be
escaped using standard XML character escaping mechanisms. The actual
representation of the character depends on the <FONT face="Courier New"
>encoding</FONT> attribute defined for the <FONT
face="Courier New"><?xml></FONT> processing
instruction.</P></BLOCKQUOTE>
<P><STRONG>Real Values</STRONG></P>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<P>If the CIM type is <FONT face="Courier New"
>real32</FONT> or <FONT face="Courier New"
>real64</FONT>, then the PCDATA value MUST conform to
the following syntax:</P>
<P><FONT face="Courier New"
> [ "+" | "-" ] *decimalDigit "." 1*decimalDigit [
( "e" | "E" ) [ "+" | "-" ] 1*decimalDigit ] </FONT></P>
<P>where <FONT face="Courier New"
>decimalDigit</FONT> is any character from the set
{<FONT face="Courier New">0</FONT>, <FONT
face="Courier New">1</FONT>, <FONT face="Courier New"
>2</FONT>, <FONT face="Courier New"
>3</FONT>, <FONT face="Courier New"
>4</FONT>, <FONT face="Courier New"
>5</FONT>, <FONT face="Courier New"
>6</FONT>, <FONT face="Courier New"
>7</FONT>, <FONT face="Courier New"
>8</FONT>, <FONT face="Courier New"
>9</FONT>}.</P></BLOCKQUOTE>
<P><STRONG>Boolean
Values</STRONG></P>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<P>If the CIM type is <FONT face="Courier New"
>boolean</FONT>, then the PCDATA value MUST be either
<FONT face="Courier New">TRUE</FONT> or <FONT
face="Courier New">FALSE</FONT>. These values MUST
be treated as case-insensitive.</P></BLOCKQUOTE>
<P><STRONG>Integer
Values</STRONG></P>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<P>If the CIM type belongs to the set {<FONT
face="Courier New">uint8</FONT>, <FONT
face="Courier New">uint16</FONT>, <FONT
face="Courier New">uint32</FONT>, <FONT
face="Courier New">uint64</FONT>} then the PCDATA value
MUST be a valid unsigned decimal or hexadecimal value.</P>
<P>If the CIM type belongs to the set {<FONT
face="Courier New">sint8</FONT>, <FONT
face="Courier New">sint16</FONT>, <FONT
face="Courier New">sint32</FONT>, <FONT
face="Courier New">sint64</FONT>} then the PCDATA value
MUST be a valid signed decimal or hexadecimal value.</P>
<P>Decimal values have the format:</P>
<P> <FONT face="Courier New"
>[ "+" | "-" ] ( positiveDecimalDigit *decimalDigit |
"0" )</FONT></P>
<P>Where <FONT face="Courier New"
>decimalDigit</FONT> is as defined above and <FONT
face="Courier New">positiveDecimalDigit </FONT>is any
decimal digit other than <FONT face="Courier New"
>0</FONT>. The leading sign character MUST NOT be
used when the CIM type is unsigned.</P>
<P>Hexadecimal values have the format:</P>
<P><FONT face="Courier New"
> [ "+" | "-" ] ( "0x" | "0X" )
1*hexDigit</FONT></P>
<P>Where hexDigit is either a decimalDigit or a
character from the set {<FONT face="Courier New"
>a</FONT>, <FONT face="Courier New"
>A</FONT>, <FONT face="Courier New"
>b</FONT>, <FONT face="Courier New"
>B</FONT>, <FONT face="Courier New"
>c</FONT>, <FONT face="Courier New"
>C</FONT>, <FONT face="Courier New"
>d</FONT>, <FONT face="Courier New"
>D</FONT>, <FONT face="Courier New"
>e</FONT>, <FONT face="Courier New"
>E</FONT>, <FONT face="Courier New"
>f</FONT>, <FONT face="Courier New"
>F</FONT>}. The leading sign character MUST NOT be used
when the CIM type is unsigned.</P></BLOCKQUOTE>
<P><STRONG>Datetime
Values</STRONG></P>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<P>If the CIM type is <FONT face="Courier New"
>datetime</FONT> then the PCDATA value MUST be a valid
datetime value as defined in detail by the CIM specification [1]. (For
interval values the format is <FONT face="Courier New"
>ddddddddhhmmss.mmmmmm:000</FONT>, and for absolute
values the format is <FONT face="Courier New"
>yyyymmddhhmmss.mmmmmmsutc</FONT>).</P>
<P>The value MUST NOT be surrounded by string
delimiter characters (such as double-quote or
single-quote).</P></BLOCKQUOTE></BLOCKQUOTE>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecVALUEARRAY>3.2.3.2.
VALUE.ARRAY</A></H4>
<P>The VALUE.ARRAY element is used to represent the
value of a CIM Property or Qualifier that has an array type.</P>
<P>CIM arrays are classified as "Bag", "Ordered" or
"Indexed" [1] using the ARRAYTYPE Qualifier. If the array is Ordered or
Indexed then the constituent <A href="#SecVALUE" >VALUE</A> elements MUST appear in the correct
order.</P><CODE>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT VALUE.ARRAY (<A href="#SecVALUE" >VALUE</A>*)></CODE></TD></TR></TBODY></TABLE></CODE>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H4><A name=SecVALUEREFERENCE>3.2.3.3.
VALUE.REFERENCE</A></H4>
<P>The VALUE.REFERENCE element is used to define a single
CIM reference Property value. </P>
<P>If a <A href="#SecLOCALCLASSPATH" >LOCALCLASSPATH</A> or <A href="#SecLOCALINSTANCEPATH" >LOCALINSTANCEPATH</A> subelement is
used, the target object is assumed to be on the same host. If a <A href="#SecCLASSNAME2" >CLASSNAME</A> or <A href="#SecINSTANCENAME" >INSTANCENAME</A> is used,
the target object is assumed to be in the same Namespace.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT VALUE.REFERENCE (<A href="#SecCLASSPATH" >CLASSPATH</A>|<A href="#SecLOCALCLASSPATH" >LOCALCLASSPATH</A>|<A href="#SecCLASSNAME2" >CLASSNAME</A>|<A href="#SecINSTANCEPATH" >INSTANCEPATH</A>|<A href="#SecLOCALINSTANCEPATH" >LOCALINSTANCEPATH</A>|<A href="#SecINSTANCENAME" >INSTANCENAME</A>)></CODE></TD></TR></TBODY></TABLE></FONT></P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecVALUEREFARRAY>3.2.3.4.
VALUE.REFARRAY</A></H4>
<P>The VALUE.REFARRAY element is used to represent the
value of an array of CIM references.</P>
<P>CIM arrays are classified as "Bag", "Ordered" or
"Indexed" [1] using the ARRAYTYPE Qualifier. If the array is Ordered or
Indexed then the constituent <A href="#SecVALUEREFERENCE" >VALUE.REFERENCE</A> elements MUST appear in
the correct order.</P>
<P><CODE>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT VALUE.REFARRAY (<A href="#SecVALUEREFERENCE" >VALUE.REFERENCE</A>*)></CODE></TD></TR></TBODY></TABLE></CODE></P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecVALUEOBJECT>3.2.3.5. </A><A name=SecVALUEOBJECT>VALUE.OBJECT</A></H4>
<P>The VALUE.OBJECT element is used to define a value which
is comprised of a single CIM Class or Instance definition.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT VALUE.OBJECT </CODE><FONT
face="Courier New"><FONT size=2
>(<A href="#SecCLASS" >CLASS</A>|<A href="#SecINSTANCE" >INSTAN</A><CODE
><FONT size=2><A href="#SecINSTANCE" >CE</A></FONT></CODE><CODE
></FONT></FONT>)></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecVALUENAMEDINSTANCE>3.2.3.6. VALUE.NAMEDINSTANCE</A></H4>
<P>The VALUE.NAMEDINSTANCE element is used to define a
value which is comprised of a single named CIM Instance definition.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT VALUE.NAMEDINSTANCE </CODE><FONT
face="Courier New"><FONT size=2
>(<A href="#SecINSTANCENAME" >INSTANCENAME</A>,<A href="#SecINSTANCE" >INSTAN</A><CODE
><FONT size=2><A href="#SecINSTANCE" >CE</A></FONT></CODE><CODE
></FONT></FONT>)></CODE></TD></TR></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A></FONT></P>
<H4><A name=SecVALUEOBJECT>3.2.3.7. </A><A name=SecVALUENAMEDOBJECT>VALUE.NAMEDOBJECT</A> </H4>
<P>The VALUE.NAMEDOBJECT element is used to define a value
which is comprised of a single named CIM Class or Instance definition.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT VALUE.NAMEDOBJECT </CODE><FONT
face="Courier New"><FONT size=2
>(<A href="#SecCLASS" >CLASS</A>|(<A href="#SecINSTANCENAME" >INSTANCENAME</A>,<A href="#SecINSTANCE" >INSTAN</A><CODE><FONT
size=2><A href="#SecINSTANCE" >CE</A></FONT></CODE><CODE
></FONT></FONT>))></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H4><A name=SecVALUELOCOBJ>3.2.3.8.
</A><A name=SecVALUEOBJECTWITHPATH>VALUE.OBJECTWITHPATH</A></H4>
<P>The VALUE.OBJECTWITHPATH element is used to define a
value which is comprised of a single CIM Object (Class or Instance) definition
with additional information that defines the absolute path to that
Object.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT VALUE.OBJECTWITHPATH </CODE><FONT
face="Courier New"><FONT size=2
>((<A href="#SecCLASSPATH" >CLASSPATH</A>,<A href="#SecCLASS" >CLASS</A>)|(<A href="#SecINSTANCEPATH" >INSTANCEPATH</A>,<A href="#SecINSTANCE" >INSTANCE</A>))<CODE
></FONT></FONT>></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H4><A name=SecVALUELOCOBJ>3.2.3.9.
</A><A name=SecVALUEOBJECTWITHLOCALPATH>VALUE.OBJECTWITHLOCALPATH</A></H4>
<P>The VALUE.OBJECTWITHLOCALPATH element is used to define
a value which is comprised of a single CIM Object (Class or Instance) definition
with additional information that defines the local path to that
Object.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT VALUE.OBJECTWITHLOCALPATH
</CODE><FONT face="Courier New"><FONT size=2
>((<A href="#SecLOCALCLASSPATH" >LOCALCLASSPATH</A>,<A href="#SecCLASS" >CLASS</A>)|(<A href="#SecLOCALINSTANCEPATH" >LOCALINSTANCEPATH</A>,<A href="#SecINSTANCE" >INSTANCE</A>))<CODE
></FONT></FONT>></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A></FONT></P>
<H3>3.2.4. <A name=SecNamingAndLocationElements>Naming and Location Elements</A></H3>
<P>This section defines those elements of the Schema that
are concerned with expressing the name and location of CIM objects.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecNAMESPACE>3.2.4.1.
</A><A name=SecNAMESPACEPATH>NAMESPACEPATH</A><A
name=SecNAMESPACE></A></H4>
<P>The NAMESPACEPATH element is used to define a Namespace
Path. It consists of a <A href="#SecHOST" >HOST</A> element and a <A href="#SecLOCALNAMESPACE" >LOCALNAMESPACE</A>
element. </P>
<P>The <A href="#SecNAMESPACE" >NAMESPACE</A> elements MUST appear in heirarchy
order, with the root Namespace appearing first.</P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT NAMESPACEPATH (<A href="#SecHOST" >HOST</A>,<A href="#SecLOCALNAMESPACEPATH" >LOCALNAMESPACEPATH</A>)>
</CODE></TD></TR></TBODY></TABLE>
<P><A href="#SecContents" >Back to contents</A></P>
<H4>3.2.4.2. <A name=SecLOCALNAMESPACEPATH>LOCALNAMESPACEPATH</A></H4>
<P>The LOCALNAMESPACEPATH element is used to define a
local Namespace path (one without a Host component). It consists of one or more
<A href="#SecNAMESPACE" >NAMESPACE</A> elements (one for each namespace in
the path).</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT LOCALNAMESPACEPATH (<A href="#SecNAMESPACE" >NAMESPACE</A>+)>
</CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecHOST>3.2.4.3.
HOST</A></H4>
<P>The HOST element is used to define a single Host. The
element content MUST specify a legal value for a hostname in accordance with the
CIM specification [1].</P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT HOST (#PCDATA)>
</CODE></TD></TR></TBODY></TABLE>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H4><A name=SecNAMESPACE>3.2.4.4.
NAMESPACE</A></H4>
<P>The NAMESPACE element is used to define a single
Namespace component of a Namespace path. </P>
<TABLE border=1 cellPadding=5 cellSpacing=1 id=TABLE2 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT NAMESPACE EMPTY> <BR
><!ATTLIST NAMESPACE<BR
> <A href="#SecCIMName" >%CIMName;</A>> </CODE></TD></TR></TBODY></TABLE>
<P>The <FONT face="Courier New">NAME
</FONT>attribute defines the name of the Namespace. </P>
<P><A href="#SecContents" >Back to contents</A></P></FONT>
<H4><A name=SecCLASSPATH>3.2.4.5.
CLASSPATH</A></H4>
<P>The CLASSPATH element defines the
absolute path to a CIM Class. It is formed from a namespace path and
Class name. </P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT CLASSPATH (<A href="#SecNAMESPACEPATH" >NAMESPACEPATH</A>,<A href="#SecCLASSNAME2" >CLASSNAME</A>)</CODE><CODE
>></CODE></TD></TR></TBODY></TABLE>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecCLASSPATH>3.2.4.6.
</A><A name=SecLOCALCLASSPATH>LOCALCLASSPATH</A></H4>
<P>The LOCALCLASSPATH element defines the a local
path to a CIM Class. It is formed from a local namespace path and Class
name. </P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT LOCALCLASSPATH (<A href="#DefLOCALNAMESPACEPATH" >LOCALNAMESPACEPATH</A>, <A href="#SecCLASSNAME2" >CLASSNAME</A>)</CODE><CODE
>></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecCLASSPATH>3.2.4.7.
</A><A name=SecCLASSNAME2>CLASSNAME</A><A name=SecCLASSPATH></A></H4>
<P>The CLASSNAME element defines the qualifying name of a
CIM Class. </P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT CLASSNAME EMPTY</CODE><CODE
>><BR><!ATTLIST
CLASSNAME<BR
> <A href="#SecCIMName" >%CIMName;</A>></CODE></TD></TR></TBODY></TABLE></P>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the class.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecINSTANCEPATH>3.2.4.8.
INSTANCEPATH</A></H4>
<P>The INSTANCEPATH element defines the absolute path to a
CIM Instance. It is comprised of a Namespace path and an Instance Name
(model path).</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT INSTANCEPATH (<A href="#SecNAMESPACEPATH" >NAMESPACEPATH</A></CODE>,<CODE
><A href="#SecINSTANCENAME" >INSTANCENAME</A>)></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecINSTANCEPATH>3.2.4.9.
</A><A name=SecLOCALINSTANCEPATH>LOCALINSTANCEPATH</A></H4>
<P>The LOCALINSTANCEPATH element defines the local
path to a CIM Instance. It is comprised of a local Namespace path and an
Instance Name (model path).</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT LOCALINSTANCEPATH (<A href="#SecLOCALNAMESPACEPATH" >LOCALNAMESPACEPATH</A></CODE>,<CODE
><A href="#SecINSTANCENAME" >INSTANCENAME</A>)></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecINSTANCEPATH>3.2.4.10.
</A><A name=SecINSTANCENAME>INSTANCENAME</A></H4>
<P>The INSTANCENAME element defines the location of a CIM
Instance within a Namespace (it is referred to in the CIM Specification [1] as a
Model Path). It is comprised of a class name and a key
binding information.</P>
<P>If the Class has a single key property, then a
single <A href="#SecKEYVALUE" >KEYVALUE</A> or <A href="#SecVALUEREFERENCE" >VALUE.REFERENCE</A> subelement may be
used to describe the (necessarily) unique key value without a key name.
Alternatively a single <A href="#SecKEYBINDING" >KEYBINDING</A> sublement may be used instead.</P>
<P>If the Class has more than one key property, then a <A href="#SecKEYBINDING" >KEYBINDING</A> subelement MUST appear for each
key.</P>
<P>If there are no key-bindings specified, the instance is
assumed to be a singleton instance of a keyless Class.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT INSTANCENAME (</CODE><FONT size=2
><FONT face="Courier New"><A href="#SecKEYBINDING" >KEYBINDING</A>*|</FONT><CODE
></FONT><A href="#SecKEYVALUE" >KEYVALUE</A><FONT face="Courier New" size=2
>?|<A href="#SecVALUEREFERENCE" >VALUE.REFERENCE</A></FONT>?)><BR
><!ATTLIST INSTANCENAME<BR
> <A href="#SecClassName" >%ClassName;</A>></CODE></TD></TR></TBODY></TABLE></P>
<P>The <FONT face="Courier New">CLASSNAME</FONT> attribute defines the name of the class
for this path.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecVALUELOCOBJNAME>3.2.4.11. </A><A name=SecOBJECTPATH>OBJECTPATH</A></H4>
<P>The OBJECTPATH element is used to define a full
path to a single CIM Object (Class or Instance).</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT OBJECTPATH </CODE><FONT
face="Courier New"><FONT size=2
>(<A href="#SecINSTANCEPATH" >INSTANCEPATH</A>|<A href="#SecCLASSPATH" >CLASSPATH</A>)<CODE
></FONT></FONT>></CODE></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecKEYBINDING>3.2.4.12.
KEYBINDING</A></H4>
<P>The KEYBINDING element defines a single key
property value binding. </P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 id=TABLE3 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT KEYBINDING (</CODE><FONT
face="Courier New" size=2><A href="#SecKEYVALUE" >KEYVALUE</A><FONT
face="Courier New" size=2>|<A href="#SecVALUEREFERENCE" >VALUE.REFERENCE</A></FONT>)><BR
><!ATTLIST KEYBINDING<BR
> <A href="#SecCIMName" >%CIMName;</A>></FONT></TD></TR></TBODY></TABLE></P>
<P>The <FONT face="Courier New">NAME</FONT> attribute indicates the name of the key
property.</P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecKEYVALUE>3.2.4.13.
KEYVALUE</A></H4>
<P>The KEYVALUE element defines a single property key value
when the key property is a non-reference type. </P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT KEYVALUE (#PCDATA)><BR
><!ATTLIST KEYVALUE<BR
> VALUETYPE
(string|boolean|numeric) 'string'></CODE></TD></TR></TBODY></TABLE></P>
<P>Values are not type-validatable using DTD, so each value
appears in PCDATA format irrespective of the type. The CIM Type of the
underlying key property determines the format of the PCDATA value.
The rules for how the content of this element is formatted depending
on that CIM type are exactly the same as for the <A href="#SecValue" >VALUE</A> element.</P>
<P>The <FONT face="Courier New">VALUETYPE</FONT> attribute provides necessary and
sufficient information regarding the CIM type to allow the transformation of the
key value to and from its' textual equivalent (as part of a text-based CIM
object path, as defined in [1]). The value of this attribute MUST conform
to the following rules:</P>
<UL>
<LI>If the CIM type is string, datetime or char16, then
the value is <FONT face="Courier New">string</FONT>.
<LI>If the CIM type is boolean, then the value is <FONT
face="Courier New">boolean</FONT>.
<LI>Otherwise the value is <FONT face="Courier New"
>numeric</FONT>.</LI></UL>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H3>3.2.5. <A name=SecObjectDefinitionElements>Object Definition Elements</A></H3>
<P>This section defines those elements of the Schema that
are concerned with expressing the definition of CIM objects (Classes,
Instances, Properties, Methods and Qualifiers).</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecCLASS>3.2.5.1.
CLASS</A></H4>
<P>The CLASS element defines a single CIM Class.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT CLASS (<A href="#SecQUALIFIER" >QUALI</A></CODE><FONT
face="Courier New"><FONT size=2
><A href="#SecQUALIFIER" >FIER</A>*,(<A href="#SecPROPERTY" >PROPERTY</A>|<A href="#SecPROPERTYARRAY" >PROPERTY.ARRAY</A>|<A href="#SecPROPERTYREFERENCE" >PROPERTY.REFERENCE</A>)*,<CODE
></FONT></FONT><A href="#SecMETHOD" >METHOD</A>*)><BR
><!ATTLIST CLASS <BR
> <A href="#SecCIMName" >%CIMName;</A><BR
> <A href="#SecSuperClass" >%SuperClass;</A>></CODE></TD></TR></TBODY></TABLE><FONT
face=Verdana size=2></P></FONT>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the Class.</P>
<P>The <FONT face="Courier New">SUPERCLASS</FONT> attribute, if present, defines the name
of the superclass of this class. If absent, it should be inferred that the class
in question has no superclass.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecINSTANCE>3.2.5.2.
INSTANCE</A></H4>
<P>The INSTANCE element defines a single CIM Instance of a
CIM Class.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT INSTANCE (<A href="#SecQUALIFIER" >QUALIFIER</A></CODE><CODE
>*,(<A href="#SecPROPERTY" >PROPERTY</A>|<A href="#SecPROPERTYARRAY" >PROPERTY.ARRAY</A>|<A href="#SecPROPERTYREFERENCE" >PROPERTY.REFERENCE</A></CODE><CODE
>)*)><BR><!ATTLIST
INSTANCE<BR
> <A href="#SecClassName" >%ClassName;</A>></CODE></TD></TR></TBODY></TABLE></P>
<P>The <FONT face="Courier New">CLASSNAME</FONT> attribute defines the name of the CIM
Class of which this is an Instance.</P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecQUALIFIER>3.2.5.3.
QUALIFIER</A></H4>
<P>The QUALIFIER element defines a single CIM Qualifier. If
the Qualifier has a non-array type, it contains a single <A href="#SecVALUE" >VALUE</A> element representing
the value of the Qualifier. If the Qualifier has an array type, it contains a
single <A href="#SecVALUEARRAY" >VALUE.ARRAY</A> element to represent the
value.</P>
<TABLE border=1 cellPadding=5 cellSpacing=1 style="LEFT: 0px; TOP: -1px"
width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT QUALIFIER (<A href="#SecVALUE" >VALUE</A>|<A href="#SecVALUEARRAY" >VALUE.ARRAY</A>)><BR
><!ATTLIST QUALIFIER <BR
> <A href="#SecCIMName" >%CIMName;</A><BR
> <A href="#SecCIMType" >%CIMType;</A>
#REQUIRED <BR
> <A href="#SecPropagated" >%Propagated;</A><BR
> <A href="#SecQualifierFlavor" >%QualifierFlavor;</A>></FONT><CODE
> </CODE></TD></TR></TBODY></TABLE></FONT>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the Qualifier,
and the <FONT face="Courier New">TYPE</FONT> defines the
CIM Type. </P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecPROPERTY>3.2.5.4.
PROPERTY</A></H4>
<P>The PROPERTY element defines a single (non-array) CIM
Property that is not a reference. It contains a single <A href="#SecVALUE" >VALUE</A> element
representing the value of the Property.</P>
<P>If the Property has no assigned value then the <A href="#SecVALUE" >VALUE</A>
element MUST be absent.</P>
<P>CIM Reference Properties are described using the <A href="#SecPROPERTYREFERENCE" >PROPERTY.REFERENCE</A> element.</P></FONT>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT PROPERTY (<A href="#SecQUALIFIER" >QUALIFIER</A>*,<A href="#SecVALUE" >VALUE</A>?)><BR
><!ATTLIST PROPERTY <BR
> <A href="#SecCIMName" >%CIMName;</A><BR
> <A href="#SecCIMType" >%CIMType;</A> #REQUIRED <BR
> <A href="#SecClassOrigin" >%ClassOrigin;</A><BR
> <A href="#SecPropagated" >%Propagated;</A>></FONT><CODE
> </CODE></TD></TR></TBODY></TABLE><FONT face=Verdana size=2></FONT>
<P>The <FONT face="Courier New">NAME
</FONT>attribute defines the name of the Property, and the TYPE defines the CIM
Type. </P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecPROPERTYARRAY>3.2.5.5.
PROPERTY.ARRAY</A></H4>
<P>The PROPERTY.ARRAY element defines a single CIM Property
with an array type. It contains a single <A href="#SecVALUEARRAY" >VALUE.ARRAY</A>
element representing the value of the Property.</P>
<P>If the Property has no assigned value then the <A href="#SecVALUEARRAY" >VALUE.ARRAY</A> element MUST be absent.</P>
<P>There is no element to model a Property that contains an
array of references as this is not a valid Property type according to CIM
[1].</P>
<P></P>
<TABLE border=1 cellPadding=5 cellSpacing=1 id=TABLE7 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><FONT face="Courier New" size=2
><!ELEMENT PROPERTY.ARRAY (<A href="#SecQUALIFIER" >QUALIFIER</A>*,<A href="#SecVALUEARRAY" >VALUE.ARRAY</A>?)><BR
><!ATTLIST PROPERTY.ARRAY <BR
> <A href="#SecCIMName" >%CIMName;</A><BR
> <A href="#SecCIMType" >%CIMType;</A> #REQUIRED <BR
> <A href="#SecArraySize" >%ArraySize;</A> <BR
> <A href="#SecClassOrigin" >%ClassOrigin;</A><BR
> <A href="#SecPropagated" >%Propagated;</A>></FONT>
</CODE></TD></TR></TBODY></TABLE>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the Property, and
the <FONT face="Courier New">TYPE</FONT> defines the CIM
Type.</P>
<P>If the <FONT face="Courier New">ARRAYSIZE</FONT> attribute is not present on a
PROPERTY.ARRAY element within a containing <A href="#SecCLASS" >CLASS</A> or <A href="#SecASSOCIATIONCLASS" >ASSOCIATION.CLASS</A> element, this
indicates that the array is of variable size. </P>
<P>Presence or otherwise of the <FONT
face="Courier New">ARRAYSIZE</FONT> attribute on a
PROPERTY.ARRAY element within a containing <A href="#SecINSTANCE" >INSTANCE</A> element MUST NOT
be taken to imply that the Property type is or is not a fixed-size array (i.e.
the <A href="#SecCLASS" >CLASS</A>
definition is always authoritative in this respect).</P>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H4><A name=SecPROPERTYREFERENCE>3.2.5.6. PROPERTY.REFERENCE</A></H4>
<P>The PROPERTY.REFERENCE element models a single CIM
Property with reference semantics. In future the features of XML Linking [<A href="#RefXLL" >4</A>] may be
used to identify linking elements within the XML Document; as XML Linking
is currently only at Working Draft status no explicit dependencies have been
made at this point.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT
PROPERTY.REFERENCE (<A href="#SecQUALIFIER" >QUALIFIER</A><FONT face="Courier New" size=2
>*,<A href="#SecVALUEREFERENCE" >VALUE.REFERENCE</A></FONT>?)><BR
><!ATTLIST PROPERTY.REFERENCE<BR
> <A href="#SecCIMName" >%CIMName;</A><BR
> <A href="#SecReferenceClass" >%ReferenceClass;<BR
></A> <A href="#SecClassOrigin" >%ClassOrigin;</A><BR
> <A href="#SecPropagated" >%Propagated;</A>></FONT></TD></TR></TBODY></TABLE></P>
<P>The <FONT face="Courier New">NAME
</FONT>attribute defines the name of the Property. </P>
<P>The <FONT face="Courier New">REFERENCECLASS</FONT> attribute, if present, defines
the strong type of the reference. If not present it indicates that this
reference is not strongly typed.</P>
<P>The ClassOrigin and Propagated entities are used in the
same manner as for other CIM Properties.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecMETHOD>3.2.5.7.
METHOD</A></H4>
<P>The METHOD element defines a single CIM Method. It may
have Qualifiers, and zero or more parameters. </P>
<P>The order of the <A href="#SecPARAMETER" >PARAMETER</A>, <A href="#SecPARAMETERREFERENCE" >PARAMETER.REFERENCE</A>, <A href="#SecPARAMETERARRAY" >PARAMETER.ARRAY</A> and <A href="#SecPARAMETERREFARRAY" >PARAMETER.REFARRAY</A> subelements is
significant as it MUST conform to the parameter order in the formal signature of
the method. </P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT METHOD (<A href="#SecQUALIFIER" >QUALIFIER</A>*,(<A href="#SecPARAMETER" >PARAMETER</A>|<A href="#SecPARAMETERREFERENCE" >PARAMETER.REFERENCE</A>|<A href="#SecPARAMETERARRAY" >PARAMETER.ARRAY</A>|<A href="#SecPARAMETERREFARRAY" >PARAMETER.REFARRAY</A>)*)><BR
><!ATTLIST METHOD <BR
> <A href="#SecCIMName" >%CIMName;</A><BR
> <A href="#SecCIMType" >%CIMType;</A>
#IMPLIED <BR
> <A href="#SecClassOrigin" >%ClassOrigin;</A><BR
> <A href="#SecPropagated" >%Propagated;</A>></FONT></TD></TR></TBODY></TABLE>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the Method. </P>
<P>The <FONT face="Courier New">TYPE
</FONT>attribute defines the method return type, if the method returns a
value. If this attribute is absent then the method MUST return no
value (i.e. it has the special return type <FONT face="Courier New">void</FONT>).</P>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H4><A name=SecPARAMETER>3.2.5.8.
PARAMETER</A></H4>
<P>The PARAMETER element defines a single (non-array,
non-reference) Parameter to a CIM Method. The parameter MAY
have zero or more Qualifiers.</P>
<TABLE border=1 cellPadding=5 cellSpacing=1 id=TABLE5 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT PARAMETER (<A href="#SecQUALIFIER" >QUALIFIER</A>*)><BR
><!ATTLIST PARAMETER <BR
> <A href="#SecCIMName" >%CIMName;</A> <BR
> <A href="#SecCIMType" >%CIMType;</A>
#REQUIRED></FONT></TD></TR></TBODY></TABLE>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the Parameter.
The <FONT face="Courier New">TYPE</FONT> attribute defines
the CIM type of the parameter.</P>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H4><A name=SecPARAMETERREFERENCE>3.2.5.9. PARAMETER.REFERENCE</A></H4>
<P>The PARAMETER.REFERENCE element defines a single
reference Parameter to a CIM Method. The parameter MAY have zero or
more Qualifiers.</P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT
PARAMETER.REFERENCE (<A href="#SecQUALIFIER" >QUALIFIER</A>*)><BR
><!ATTLIST PARAMETER.REFERENCE<BR
> <A href="#SecCIMName" >%CIMName;</A><BR
> <A href="#SecReferenceClass" >%ReferenceClass;</A>></FONT></TD></TR></TBODY></TABLE></FONT>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the Parameter.
</P>
<P>The <FONT face="Courier New">REFERENCECLASS</FONT> attribute, if present, defines the
strong type of the reference. If absent the parameter is assumed to a
reference that is not strongly typed.</P>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H4><A name=SecPARAMETERARRAY>3.2.5.10. PARAMETER.ARRAY</A></H4>
<P>The PARAMETER.ARRAY element defines a single Parameter
to a CIM Method that has an array type. The parameter MAY have zero or
more Qualifiers.</P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT
PARAMETER.ARRAY (<A href="#SecQUALIFIER" >QUALIFIER</A>*)><BR
><!ATTLIST PARAMETER.ARRAY<BR
> <A href="#SecCIMName" >%CIMName;</A><BR
> <A href="#SecCIMType" >%CIMType;</A>
#REQUIRED<BR
> <A href="#SecArraySize" >%ArraySize;</A>></FONT></TD></TR></TBODY></TABLE></FONT>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the Parameter.
The <FONT face="Courier New">TYPE</FONT> attribute defines
the CIM type of the parameter.</P>
<P>The <FONT face="Courier New">ARRAYSIZE </FONT>attribute is present if and only if the
array is constrained to a fixed number of elements. If it has empty content this
indicates that the array is of variable size.</P>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H4><A name=SecPARAMETERREFARRAY>3.2.5.11. PARAMETER.REFARRAY</A></H4>
<P>The PARAMETER.REFARRAY element defines a single
Parameter to a CIM Method that has an array of references type. The
parameter MAY have zero or more Qualifiers.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT
PARAMETER.REFARRAY (<A href="#SecQUALIFIER" >QUALIFIER</A>*)><BR
><!ATTLIST PARAMETER.REFARRAY<BR
> <A href="#SecCIMName" >%CIMName;</A><BR
> <A href="#SecReferenceClass" >%ReferenceClass;</A><BR
> <A href="#SecArraySize" >%ArraySize;</A>></FONT></TD></TR></TBODY></TABLE></FONT></P>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the Parameter.
</P>
<P>The <FONT face="Courier New">REFERENCECLASS</FONT> attribute defines the strong
type of a reference. If absent, it is assumed that the parameter
is not a strongly typed reference.</P>
<P>The <FONT face="Courier New">ARRAYSIZE</FONT> attribute is present if and only if the
array is constrained to a fixed number of elements. If absent this
indicates that the array is of variable size.</P>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H3>3.2.6. <A name=SecMessageElements>Message Elements</A></H3>
<P>This section defines those elements of the Schema that
are concerned with expressing the definition of CIM Messages for the CIM
Mapping onto HTTP [9].</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecMESSAGE>3.2.6.1.
MESSAGE</A></H4>
<P>The MESSAGE element models a single CIM message.
This element is used as the basis for CIM Operations [9].</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT MESSAGE (<A href="#SecSIMPLEREQ" >SIMPLEREQ</A>|<A href="#SecMULTIREQ" >MULTIREQ</A>|<A href="#SecSIMPLERSP" >SIMPLERSP</A>|<A href="#SecMULTIRSP" >MULTIRSP</A>)><BR
><!ATTLIST MESSAGE<BR
> ID
CDATA #REQUIRED<BR
>
PROTOCOLVERSION CDATA
#REQUIRED></FONT></TD></TR></TBODY></TABLE></P>
<P>The <FONT face="Courier New">ID</FONT> attribute defines an identifier for the
MESSAGE. The content of the value is not constrained by this
specification, but the intention is this be used as a correlation mechanism
between two CIM entities.</P>
<P>The PROTOCOLVERSION attribute defines the version of the
CIM Mapping to which this message conforms. </P>
<P>The HTTP mapping specification [9] provides more
details on the values that these attributes may take.</P>
<P><A href="#SecContents" >Back to contents</FONT></A> </P>
<H4><A name=SecMULTIREQ>3.2.6.2.
MULTIREQ</A></H4>
<P>The MULTIREQ element defines a Multiple CIM
Operation request. It contains two or more subelements defining the
<A href="#SecSIMPLEREQ" >SIMPLEREQ</A> elements that make up this multiple
request.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT MULTIREQ
(<A href="#SecSIMPLEREQ" >SIMPLEREQ</A>,<A href="#SecSIMPLEREQ" >SIMPLEREQ</A>+)></FONT></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecSIMPLEREQ>3.2.6.3.
SIMPLEREQ</A></H4>
<P>The SIMPLEREQ element defines a Simple CIM Operation
request. It contains either a <A href="#SecMETHODCALL" >METHODCALL</A> (extrinsic
method) element or an <A href="#SecIMETHODCALL" >IMETHODCALL</A> (intrinsic method) element.</P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT SIMPLEREQ
(<A href="#SecMETHODCALL" >METHODCALL</A>|<A href="#SecIMETHODCALL" >IMETHODCALL</A>)></FONT></TD></TR></TBODY></TABLE>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecMETHODCALL>3.2.6.4.
METHODCALL</A></H4>
<P>The METHODCALL element defines a single method
invocation on a Class or Instance. It specifies the local path of the
target Class or Instance, followed by zero or more <A href="#SecPARAMVALUE" >PARAMVALUE</A> subelements as the parameter
values to be passed to the method.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT METHODCALL
((<A href="#SecLOCALCLASSPATH" >LOCALCLASSPATH</A>|<A href="#SecLOCALINSTANCEPATH" >LOCALINSTANCEPATH</A>),<A href="#SecPARAMVALUE" >PARAMVALUE</A>*)><BR
><!ATTLIST METHODCALL<BR
> <A href="#SecCIMName" >%CIMName;</A>></FONT></TD></TR></TBODY></TABLE></P>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the method to be
invoked.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecPARAMVALUE>3.2.6.5.
PARAMVALUE</A></H4>
<P>The PARAMVALUE element defines a single extrinsic method
named parameter value. If no subelement is present this indicates that
no value has been supplied for this parameter.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2
><!ELEMENT PARAMVALUE (<A href="#SecVALUE" >VALUE</A>|<A href="#SecVALUEREFERENCE" >VALUE.REFERENCE</A>|<A href="#SecVALUEARRAY" >VALUE.ARRAY</A>|<A href="#SecVALUEREFARRAY" >VALUE.REFARRAY</A>)?><BR
><!ATTLIST PARAMVALUE<BR
> <A href="#SecCIMName" >%CIMName;</A>></FONT></TD></TR></TBODY></TABLE></P>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the
parameter.</P>
<P><A href="#SecContents" >Back to contents</A></FONT></P>
<H4><A name=SecINTRINSICCALL>3.2.6.6.
</A><A name=SecIMETHODCALL>IMETHODCALL</A></H4>
<P>The IMETHODCALL element defines a single intrinsic
method invocation. It specifies the target local namespace, followed by
zero or more <A href="#SecIPARAMVALUE" >IPARAMVALUE</A> subelements as the
parameter values to be passed to the method.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT IMETHODCALL
(<A href="#SecLOCALNAMESPACEPATH" >LOCALNAMESPACEPATH</A>,<A href="#SecIPARAMVALUE" >IPARAMVALUE</A>*)><BR
><!ATTLIST IMETHODCALL<BR
> <A href="#SecCIMName" >%CIMName;</A>></FONT></TD></TR></TBODY></TABLE></P>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the method to be
invoked.</P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecIPARAMVALUE>3.2.6.7.
IPARAMVALUE</A></H4>
<P>The IPARAMVALUE element defines a single intrinsic
method named parameter value. If no subelement is present this
indicates that no value has been supplied for this parameter.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2
><!ELEMENT IPARAMVALUE (<A href="#SecVALUE" >VALUE</A>|<A href="#SecVALUEARRAY" >VALUE.ARRAY</A>|<A href="#SecVALUEREFERENCE" >VALUE.REFERENCE</A>|<A href="#SecCLASSNAME2" >CLASSNAME</A>|<A href="#SecINSTANCENAME" >INSTANCENAME</A>|<A href="#SecQUALIFIERDECLARATION" >QUALIFIER.DECLARATION</A>|<BR
>
<A href="#SecCLASS" >CLASS</A>|<A href="#SecINSTANCE" >INSTAN</A><CODE
><FONT size=2><A href="#SecINSTANCE" >CE</A>|<A href="#SecVALUENAMEDINSTANCE" >VALUE.NAMEDINSTANCE</A></FONT></CODE>)?><BR
><!ATTLIST IPARAMVALUE<BR
> <A href="#SecCIMName" >%CIMName;</A>></FONT></TD></TR></TBODY></TABLE></P>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the
parameter.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecMULTIRSP>3.2.6.8.
MULTIRSP</A></H4>
<P>The MULTIRSP element defines a Multiple CIM
Operation response. It contains two or more subelements defining the
<A href="#SecSIMPLERSP" >SIMPLERSP</A> elements that make up this multiple
response.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT MULTIRSP
(<A href="#SecSIMPLERSP" >SIMPLERSP</A>,<A href="#SecSIMPLERSP" >SIMPLERSP</A>+)></FONT></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecSIMPLERSP>3.2.6.9.
SIMPLERSP</A> </H4>
<P>The SIMPLERSP element defines a Simple CIM Operation
response. It contains either a <A href="#SecMETHODRESPONSE" >METHODRESPONSE</A> (for
extrinsic methods) or <A href="#SecIMETHODRESPONSE" >IMETHODRESPONSE</A> (for intrinsic methods)
subelement.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2><!ELEMENT SIMPLERSP
(<A href="#SecMETHODRESPONSE" >METHODRESPONSE</A>|<A href="#SecIMETHODRESPONSE" >IMETHODRESPONSE</A>)></FONT></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecMETHODRESPONSE>3.2.6.10. METHODRESPONSE</A></H4>
<P>The METHODRESPONSE defines the response to a single CIM
extrinsic method invocation. It contains either an <A href="#SecERROR" >ERROR</A> subelement (to report a
fundamental error which prevented the method from executing), or a combination
of an optional return value and zero or more out parameter values.<CODE></P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT METHODRESPONSE (<A href="#SecERROR" >ERROR</A>|(<A href="#SecRETURNVALUE" >RETURNVALUE</A>?,<A href="#SecPARAMVALUE" >PARAMVALUE</A>*))><BR
><!ATTLIST METHODRESPONSE<BR
> <A href="#SecCIMName" >%CIMName;</A>></CODE></TD></TR></TBODY></TABLE></CODE>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the
method that was invoked.</P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecINTRINSICRESPONSE>3.2.6.11. </A><A name=SecIMETHODRESPONSE>IMETHODRESPONSE</A><A name=SecINTRINSICRESPONSE></A></H4>
<P>The IMETHODRESPONSE defines the response to a single
intrinsic CIM method invocation. It contains either an <A href="#SecERROR" >ERROR</A> subelement (to report a
fundamental error which prevented the method from executing), or an
optional return value.<CODE></P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT IMETHODRESPONSE (<A href="#SecERROR" >ERROR</A>|<A href="#SecIRETURNVALUE" >IRETURNVALUE</A>?)><BR
><!ATTLIST IMETHODRESPONSE<BR
> <A href="#SecCIMName" >%CIMName;</A>></CODE></TD></TR></TBODY></TABLE></CODE></P>
<P>The <FONT face="Courier New">NAME</FONT> attribute defines the name of the
method that was invoked.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecERROR>3.2.6.12.
ERROR</A></H4>
<P>The ERROR element is used to define a fundamental
error which prevented a method from executing normally. </P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><CODE
><!ELEMENT ERROR EMPTY><BR
><!ATTLIST ERROR<BR
> CODE CDATA #REQUIRED<BR
>
DESCRIPTION CDATA #IMPLIED></CODE></TD></TR></TBODY></TABLE></P>
<P>The <FONT face="Courier New">CODE</FONT> attribute contains a numerical status code
indicating the nature of the error. The valid status codes are defined in
[9]. The <FONT face="Courier New">DESCRIPTION</FONT>
attribute, if present, provides a human-readable description of the error.</P>
<P><A href="#SecContents" >Back to contents</A></P>
<H4><A name=SecRETVAL>3.2.6.13. </A><A
name=SecRETURNVALUE>RETURNVALUE</A></H4>
<P>The RETURNVALUE element specifies the value returned
from an extrinsic method call.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2
><!ELEMENT RETURNVALUE (<A href="#SecVALUE" >VALUE</A>|<A href="#SecVALUEARRAY" >VALUE.ARRAY</A>|<A href="#SecVALUEREFERENCE" >VALUE.REFERENCE</A>|<A href="#SecVALUEREFARRAY" >VALUE.REFARRAY</A>)></FONT></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</FONT></A></P>
<H4><A name=SecINTRINSICRETVAL>3.2.6.14. </A><A name=SecIRETURNVALUE>IRETURNVALUE</A></H4>
<P>The IRETURNVALUE element specifies the value returned
from an intrinsic method call.</P>
<P>
<TABLE border=1 cellPadding=5 cellSpacing=1 width="100%">
<TBODY>
<TR>
<TD bgColor=#00ffff vAlign=center><FONT
face="Courier New" size=2
><!ELEMENT IRETURNVALUE (<A href="#SecCLASSNAME2" >CLASSNAME</A>*|<A href="#SecINSTANCENAME" >INSTANCENAME</A>*|<A href="#SecVALUE" >VALUE</A>*|<A href="#SecVALUEOBJECTWITHPATH" >VALUE.OBJECTWITHPATH</A>*|<A
href="#SecVALUEOBJECTWITHLOCALPATH">VALUE.OBJECTWITHLOCALPATH</A>*<BR
>
<A href="#SecVALUEOBJECT" >VALUE.OBJECT</A>*|<A href="#SecOBJECTPATH" >OBJECTPATH</A>*|<A href="#SecQUALIFIERDECLARATION" >QUALIFIER.DECLARATION</A>*|<A href="#SecVALUEARRAY" >VALUE.ARRAY</A>?|<A href="#SecVALUEREFERENCE" >VALUE.REFERENCE</A>?|<BR
>
<A href="#SecCLASS" >CLASS</A>*|<A href="#SecINSTANCE" >INSTAN</A><CODE
><FONT size=2><A href="#SecINSTANCE" >CE</A>*|<A href="#SecVALUENAMEDINSTANCE" >VALUE.NAMEDINSTANCE</A></FONT></CODE>*)></FONT></TD></TR></TBODY></TABLE></P>
<P><A href="#SecContents" >Back to contents</A></P>
<H1><A name=SecReferences>4.
References</A></H1>
<OL>
<LI><A name=RefCIM></A>"Common
Information Model (CIM) Specification", Version 2.0, DMTF, 3<SUP
>rd</SUP> March 1998 (<A
href="http://dmtf.org/spec/cim_spec_v20"
>http://dmtf.org/spec/cim_spec_v20</A>)
<LI>"Extensible Markup Language (XML)", Version 1.0, W3C
Recommendation (<A href="http://www.w3.org/TR/REC-xml"
>http://www.w3.org/TR/REC-xml</A>)
<LI><A name=NamespaceRef
></A>"Namespaces in XML", 14<SUP
>th</SUP> January 1999, W3C Recommendation (<A
href="http://www.w3.org/TR/REC-xml-names"
>http://www.w3.org/TR/REC-xml-names</A>)
<LI><A name=RefXLL></A>"XML Linking
Language (XLink)", 3<SUP>rd</SUP> March 1998, W3C Working
Draft (<A href="http://www.w3.org/TR/WD-xlink"
>http://www.w3.org/TR/WD-xlink</A>
<LI><A name=RefXMLWP></A>"XML as a
Representation for Management Information - A White Paper", Version 1.0,
DMTF, September 15<SUP>th</SUP> 1998 (<A
href="http://www.dmtf.org/spec/xmlw.html"
>http://www.dmtf.org/spec/xmlw.html</A>)
<LI><A name=RefCSS1></A>"Cascading
Style Sheets, Level 1", W3C Recommendation 17<SUP
>th</SUP> December 1996 (<A
href="http://www.w3.org/TR/REC-CSS1"
>http://www.w3.org/TR/REC-CSS1</A>)
<LI><A name=RefCSS2></A>"Cascading
Style Sheets, Level 2", W3C Recommendation, 12<SUP
>th</SUP> May 1998 (<A
href="http://www.w3.org/TR/REC-CSS2"
>http://www.w3.org/TR/REC-CSS2</A>)
<LI><A name=RefXSL></A>"XSL
Transformations (XSLT)", Version 1.0, W3C Working Draft, 21<SUP
>st</SUP> April 1999 (<A
href="http://www.w3.org/TR/WD-xsltl"
>http://www.w3.org/TR/WD-xslt</A>)
<LI>"Specification for CIM Operations over HTTP", Version
1.0, DMTF, 20<SUP>th</SUP> July 1999 (<A
href="http://www.dmtf.org/spec/CIM_HTTP_Mapping10.htm"
>http://www.dmtf.org/spec/CIM_HTTP_Mapping10.htm</A>)
<LI>"Key words for use in RFCs to Indicate Requirement
Levels", IETF RFC 2119, March 1997 (<A
href="http://www.ietf.org/rfc/rfc2119.txt"
>http://www.ietf.org/rfc/rfc2119.txt</A>)
<LI>"CIM XML DTD", Version 2.0, DMTF, 20<SUP
>th</SUP> July 1999 (<A
href="http://www.dmtf.org/download/spec/xmls/CIM_DTD_V20.txt"
>http://www.dmtf.org/download/spec/xmls/CIM_DTD_V20.txt</A>)</LI></OL>
<P><A href="#SecContents" >Back to contents</A></P>
<DL></DL></BODY></HTML>
| No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |