Namespace: |
|
Content: |
complex, 2 elements |
Defined: |
globally in hsdl.xsd; see XML source |
Includes: |
definitions of 2 elements |
Used: |
at 1 location |
XML Representation Summary |
|||||
<...> |
|||||
|
|||||
</...> |
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="xpQueryResponse">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains the node set selected by the matching
</xsd:documentation>
<b>xpQuery</b>
. If the selected
node set matches zero nodes, and <b>minOccurs</b>
is zero, this element is still present
but contains empty content indicating that there were no matching nodes. <xsd:complexType>
<xsd:sequence>
</xsd:complexType>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip">
</xsd:sequence>
<xsd:annotation>
</xsd:any>
<xsd:documentation>
</xsd:annotation>
This element is a placeholder that indicates where the
</xsd:documentation>
content of the item being queried is returned.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains the response to the associated
</xsd:documentation>
<b>changeQuery</b>
. The content of this element
is a single, optional <b>changeSummary</b>
element in the form of an
<b>updateRequest</b>
that describes the changes for
the selected node set, relative to the synchronization base specified by the <b>changeNumber</b>
attribute. The client software maintaining a cache of .NET My Services data should process this
<b>updateRequest</b>
into its own cache, bringing that cache up to date.
<xsd:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
This element contains the base change number for this
</xsd:documentation>
<b>changeQuery</b>
. On request,
the <b>baseChangeNumber</b>
is supplied and is associated with a subtree in the document.
This attribute returns the new value for the change number in that subtree. It is assumed that the client software will easily know where to place this. </xsd:complexType>
|
Type: |
anonymous complexType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This element contains the response to the associated
</xsd:documentation>
<b>changeQuery</b>
. The content of this element
is a single, optional <b>changeSummary</b>
element in the form of an
<b>updateRequest</b>
that describes the changes for
the selected node set, relative to the synchronization base specified by the <b>changeNumber</b>
attribute. The client software maintaining a cache of .NET My Services data should process this
<b>updateRequest</b>
into its own cache, bringing that cache up to date.
<xsd:complexType>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
This element contains the base change number for this
</xsd:documentation>
<b>changeQuery</b>
. On request,
the <b>baseChangeNumber</b>
is supplied and is associated with a subtree in the document.
This attribute returns the new value for the change number in that subtree. It is assumed that the client software will easily know where to place this. </xsd:element>
|
Type: |
anonymous complexType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This element contains the node set selected by the matching
</xsd:documentation>
<b>xpQuery</b>
. If the selected
node set matches zero nodes, and <b>minOccurs</b>
is zero, this element is still present
but contains empty content indicating that there were no matching nodes. <xsd:complexType>
<xsd:sequence>
</xsd:complexType>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip">
</xsd:sequence>
<xsd:annotation>
</xsd:any>
<xsd:documentation>
</xsd:annotation>
This element is a placeholder that indicates where the
</xsd:documentation>
content of the item being queried is returned. </xsd:element>
|