Namespace: |
|
Type: |
|
Content: |
|
Defined: |
XML Representation Summary |
||||||
<messageStatus |
||||||
|
||||||
> |
||||||
|
||||||
</messageStatus> |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This element defines the status of the email and frequently changes. Caching clients should take
</xsd:documentation>
advantage of this when deciding which part of the message to change </xsd:element>
|
Type: |
|
Use: |
required |
Defined: |
Type: |
flagType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This optional element defines the flag state of the message. It includes an {any} element
</xsd:documentation>
that can be used for extensible flags. </xsd:element>
|
Type: |
refType, empty content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This element defines the single folder that this message logically belongs to.
</xsd:documentation>
</xsd:element>
|
Type: |
xsd:boolean, predefined, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This element defines the read/unread state of the message and can be modified.
</xsd:documentation>
</xsd:element>
|
Type: |
messageStateEnum, simple content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This element defines the sent/received state of the message. This element is read only, which
</xsd:documentation>
means that it can be queried for, but not updated </xsd:element>
|
Defined: |
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
|