complexType "notificationType"
Namespace:
http://schemas.microsoft.com/hs/2001/10/myAlerts
Content:
complex, 1 attribute, 4 elements
Defined:
globally in myalerts.xsd; see XML source
Includes:
definitions of 1 attribute, 4 elements
Used:
at 2 locations
XML Representation Summary
<...
   
 = 
xsd:string
   
>
   
Content: 
</...>
Content Model Elements (4):
contents (defined in notificationType complexType), from (type fromType), routing (type routingType), to (type toType)
All Direct / Indirect Based Elements (2):
notification (in notifyEndpointRequest), notification (type notificationType)
Known Usage Locations
Annotation
An alert has contents: "from" (sender) data, optional "to" (receiver) data, and optional "routing" data. The contents are a set of argots (domain-specific blobs). The sender and receiver must understand and agree on the argots that are transmitted in the alert. In the .NET Alerts service, both streams and connections usually choose which alerts they process based on the argots contained within the alerts.
XML Source (see within schema source)
<xsd:complexType name="notificationType">
<xsd:annotation>
<xsd:documentation>
An alert has contents: "from" (sender) data,
optional "to" (receiver) data, and optional "routing" data.
The contents are a set of argots (domain-specific blobs).
The sender and receiver must understand and agree on the argots that are
transmitted in the alert.
In the .NET Alerts service, both streams and connections usually choose which alerts
they process based on the argots contained within the alerts.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<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>
<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>
<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>
<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>
</xsd:sequence>
<!--
<xsd:attribute name="uuid" type="hs:uuidType"/>
-->
<xsd:attribute name="id" type="xsd:string"/>
</xsd:complexType>
Attribute Detail (all declarations; 1/1)
id
Type:
xsd:string, predefined
Use:
optional
Defined:
locally within (this) 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 (this) 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 (this) 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 (this) 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 (this) 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>