element <inlineAttachment> (local)
Namespace:
Type:
Content:
complex, 3 elements
Defined:
locally within htmlBodyType complexType in myInbox.xsd; see XML source
XML Representation Summary
<inlineAttachment>
   
Content: 
</inlineAttachment>
Content model elements (3):
content (type xsd:base64Binary), contentType (type xsd:string), uri (in inlineAttachment)
Included in content model of elements (1):
htmlBody (type htmlBodyType)
Annotation
This element represents an inline attachment
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="inlineAttachment" type="inlineAttachmentType">
<xsd:annotation>
<xsd:documentation>
This element represents an inline attachment
</xsd:documentation>
</xsd:annotation>
</xsd:element>
Content Element Detail (all declarations; 3/3)
content
Type:
xsd:base64Binary, predefined, simple content
Defined:
locally within inlineAttachmentType complexType
The base64 encoded attachment content
XML Source (see within schema source)
<xsd:element name="content" type="xsd:base64Binary">
<xsd:annotation>
<xsd:documentation>
The base64 encoded attachment content
</xsd:documentation>
</xsd:annotation>
</xsd:element>

contentType
Type:
xsd:string, predefined, simple content
Defined:
locally within inlineAttachmentType complexType
The Content-Type of the attachment
XML Source (see within schema source)
<xsd:element name="contentType" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The Content-Type of the attachment
</xsd:documentation>
</xsd:annotation>
</xsd:element>

uri
Type:
xsd:string, predefined, simple content
Defined:
locally within inlineAttachmentType complexType
The client defined unique identifier for the inline attachment. This element is used to identify this attachment location within the html body of a message
XML Source (see within schema source)
<xsd:element name="uri" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The client defined unique identifier for the inline attachment. This element is used to identify
this attachment location within the html body of a message
</xsd:documentation>
</xsd:annotation>
</xsd:element>