element <notification> (unified local)
Namespace:
http://schemas.microsoft.com/hs/2001/10/myAlerts
Type:
notificationType
Content:
complex, 1 attribute, 4 elements
Defined:
locally at 3 locations in myAlerts.xsd
XML Representation Summary
<notification
   
 = 
xsd:string
   
>
   
Content: 
</notification>
Content model elements (4):
contents (in notification), from (in notification), routing (in notification), to (in notification)
Included in content model of elements (3):
bufferStreamParameters, notifyRequest, pollResponse
Definition Locations
Annotations (3) (by all definition locations)
Location:
within pollResponse element [def]
Annotation:
A new alert contained in the buffer stream.
Location:
within notifyRequest element [def]
Annotation:
An alert to be delivered.
Location:
within bufferStreamParameters element [def]
Annotation:
Zero or more alerts in the buffer of the streamBuffer stream.
Attribute Detail (all declarations; 1/1)
id
Type:
xsd:string, predefined
Use:
optional
Defined:
locally within notificationType complexType
XML Source (see within schema source)
<xsd:attribute name="id" type="xsd:string"/>
Content Element Detail (all declarations; 4/4)
contents
Type:
anonymous complexType, complex content
Defined:
locally within notificationType complexType
This element contains the problem domain-specific data to be conveyed to the receiver. Each child element of the <b>contents</b> element is an argot, a problem domain-specific strongly typed XML blob. Streams and connections query against the element names of these blobs when selecting alerts they will process.
XML Source (see within schema source)
<xsd:element maxOccurs="1" minOccurs="1" name="contents">
<xsd:annotation>
<xsd:documentation>
This element contains the problem domain-specific data to be conveyed to the receiver.
Each child element of the
<b>contents</b>
element is an argot, a problem domain-specific
strongly typed XML blob. Streams and connections query against the element names of
these blobs when selecting alerts they will process.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
from
Type:
fromType, complex content
Defined:
locally within notificationType complexType
This tag contains all data from the sender, including sender authentication as well as preferences and requests from the sender.
XML Source (see within schema source)
<xsd:element minOccurs="1" name="from" type="fromType">
<xsd:annotation>
<xsd:documentation>
This tag contains all data from the sender, including sender authentication as well
as preferences and requests from the sender.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
routing
Type:
routingType, complex content
Defined:
locally within notificationType complexType
This tag contains any routing data inserted by the .NET Alerts routing process.
XML Source (see within schema source)
<xsd:element minOccurs="1" name="routing" type="routingType">
<xsd:annotation>
<xsd:documentation>
This tag contains any routing data inserted by the .NET Alerts
routing process.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
to
Type:
toType, complex content
Defined:
locally within notificationType complexType
This tag contains all data pertaining to the receiver. This data can be set by the sender or by any processing/routing agent between the sender and the receiver.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="to" type="toType">
<xsd:annotation>
<xsd:documentation>
This tag contains all data pertaining to the receiver. This data can be set
by the sender or by any processing/routing agent between the sender and the receiver.
</xsd:documentation>
</xsd:annotation>
</xsd:element>