### Example SQL Script for Database Setup

Source: https://xmpp.org/extensions/xep-0043.html

This SQL script is used to set up an example database named 'testdb' with two tables, 'tbl_one' and 'tbl_two', for use with the protocol.

```sql
create table tbl_one
        (
          a_int int,
          a_float float,
          a_char  char(10)
        )
        create table tbl_two
        (
          a_date datetime,
      a_numeric numeric(9,3)
        )
```

--------------------------------

### Start Database Readout Failure Example

Source: https://xmpp.org/extensions/xep-0326.html

This example shows an IQ set request to start a database readout and the subsequent IQ error response indicating insufficient privileges.

```xml
<iq type='set'
    from='client@example.org/client'
    to='concentrator@example.org'
    id='67'>
  <startDatabaseReadout xmlns='urn:xmpp:iot:concentrators' xml:lang='en' databaseId='LocalDB' seqnr='2' userToken='12392748927492834'> 
    <node sourceId='MeteringTopology' nodeId='Node1'/>
    <node sourceId='MeteringTopology' nodeId='Node2'/>
    <node sourceId='MeteringTopology' nodeId='Node3'/>
    <x type='submit' xmlns='jabber:x:data'>
      ...
    </x>
  </startDatabaseReadout>
</iq>

<iq type='error'
    from='concentrator@example.org'
    to='client@example.org/client'
    id='67'>
  <startDatabaseReadoutResponse xmlns='urn:xmpp:iot:concentrators' result='InsufficientPrivileges'/>
</iq>
```

--------------------------------

### Stream Setup before TLS

Source: https://xmpp.org/extensions/xep-0288.html

This example shows the stream setup process before TLS negotiation, including the bidirectional stream feature and Server Dialback result exchange. It precedes the TLS handshake and subsequent authentication.

```xml
<!-- Client -->
<bidi xmlns='urn:xmpp:bidi'/>
<db:result from='capulet.lit' to='montague.lit'>
  e3f5cf21f12749ef2cf59269bc0118f35bc46b26</db:result>
<!-- Server -->
<db:result from='montague.lit' to='capulet.lit' type='valid'/>
<!-- At this point S may send from montague.lit to capulet.lit.-->
<!-- Client -->
<iq from='juliet@capulet.lit/balcony' to='montague.lit' type='get'
  id='8dfc70af'><query xmlns='urn:xmpp:ping'/></iq>
```

--------------------------------

### httpx URL Examples

Source: https://xmpp.org/extensions/xep-0332.html

Illustrative examples of the 'httpx' URI scheme, demonstrating its structure with different paths and queries.

```text
httpx://httpServer@example.org/index.html
httpx://httpServer@example.org/images/image1.png
httpx://httpServer@example.org/api?p1=a&p2=b

```

--------------------------------

### Examples of httpx URLs

Source: https://xmpp.org/extensions/xep-0332.html

Illustrates various examples of valid URLs using the 'httpx' scheme.

```text
httpx://httpServer@example.org/index.html
httpx://httpServer@example.org/images/image1.png
httpx://httpServer@example.org/api?p1=a&p2=b
```

--------------------------------

### EXI Option Document for Shortcut Setup (Client to Server)

Source: https://xmpp.org/extensions/xep-0322.html

This XML document specifies EXI options for shortcut setup, including the schema ID. It allows clients to initiate a stream using previously negotiated configurations.

```xml
<?xml version="1.0"?>
<header xmlns="http://www.w3.org/2009/exi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <common>
  <schemaId>c:761aabc0-a255-4b9b-89a1-4cb859559691</schemaId>
 </common>
</header>
```

--------------------------------

### Jingle Fingerprint Element Example

Source: https://xmpp.org/extensions/xep-0320.html

An example of the Jingle fingerprint element, demonstrating the use of 'sha-256' for the hash and 'actpass' for the setup role.

```xml
<fingerprint xmlns='urn:xmpp:jingle:apps:dtls:0' hash='sha-256' setup='actpass'>
  02:1A:CC:54:27:AB:EB:9C:53:3F:3E:4B:65:2E:7D:46:3F:54:42:CD:54:F1:7A:03:A2:7D:F9:B0:7F:46:19:B2
</fingerprint>
```

--------------------------------

### Client initiates quick configuration

Source: https://xmpp.org/extensions/xep-0322.html

Use this XML stanza to request a quick configuration setup using a previously established configuration ID. Ensure the configurationId is valid.

```xml
<setup xmlns='http://jabber.org/protocol/compress/exi' configurationId='c76ab4ec-4993-4285-8c7a-098060581bb8'/>
```

--------------------------------

### Get Capabilities (No Batch Commands)

Source: https://xmpp.org/extensions/xep-0326.html

Request capabilities from a smaller gateway that may not support batch operations. This example shows the initial 'get' IQ.

```xml
<iq type='get'
  from='client@example.org/client'
  to='gateway@example.org'
  id='2'>
```

--------------------------------

### GET Method Call

Source: https://xmpp.org/extensions/xep-0332.html

Shows an example of a GET method call over XMPP, including the response with data. Note that the 'Connection: Close' header has no meaning in this context.

```xml
<iq type='set'
    from='httpclient@example.org/browser'
    to='httpserver@example.org'
    id='2'>
   <req xmlns='urn:xmpp:http' method='GET' resource='/rdf/xep' version='1.1'>
       <headers xmlns='http://jabber.org/protocol/shim'>
           <header name='Host'>example.org</header>
       </headers>
   </req>
</iq>

<iq type='result'
    from='httpserver@example.org'
    to='httpclient@example.org/browser'
    id='2'>
   <resp xmlns='urn:xmpp:http' version='1.1' statusCode='200' statusMessage='OK'>
       <headers xmlns='http://jabber.org/protocol/shim'>
           <header name='Date'>Fri, 03 May 2013 16:39:54GMT-4</header>
           <header name='Server'>Clayster</header>
           <header name='Content-Type'>text/turtle</header>
           <header name='Content-Length'>...</header>
           <header name='Connection'>Close</header>
       </headers>
       <data>
           <text>@prefix dc: &lt;http://purl.org/dc/elements/1.1/&gt;.
@base &lt;http://example.org/&gt;.

&lt;xep&gt; dc:title "HTTP over XMPP";
      dc:creator &lt;PeterWaher&gt;;
      dc:publisher &lt;XSF&gt;.</text>
       </data>
   </resp>
</iq>
```

--------------------------------

### JOBS OOB 'init' Command-line Example

Source: https://xmpp.org/extensions/xep-0042.html

Example of the command-line for the 'init' method in the JOBS OOB protocol. This is used to initiate a new session.

```text
jobs/0.4 init
```

--------------------------------

### Example Client and DSPS JIDs for Connection

Source: https://xmpp.org/extensions/xep-0037.html

An example of the string format for initiating a DSPS connection, showing a client JID and a DSPS JID.

```text
rob@nauseum.org/dspsclient dsps.jabber.org/0beec7b5ea3f0fdbc95d0dd47f3c5bc275da8a33
```

--------------------------------

### Get Common Commands for Nodes Example

Source: https://xmpp.org/extensions/xep-0326.html

Illustrates an IQ get stanza to retrieve common commands for a list of specified nodes and the IQ result stanza containing the available commands.

```xml
<iq type='get'
  from='client@example.org/client'
  to='concentrator@example.org'
  id='48'>
  <getCommonNodeCommands xmlns='urn:xmpp:iot:concentrators' xml:lang='en'>
    <node sourceId='MeteringGroups' nodeId='Apartment 1-1'/>
    <node sourceId='MeteringGroups' nodeId='Apartment 1-2'/>
    <node sourceId='MeteringGroups' nodeId='Apartment 1-3'/>
    <node sourceId='MeteringGroups' nodeId='Apartment 1-4'/>
    <node sourceId='MeteringGroups' nodeId='Apartment 1-5'/>
    <node sourceId='MeteringGroups' nodeId='Apartment 1-6'/>
  </getCommonNodeCommands>
</iq>

<iq type='result'
  from='concentrator@example.org'
  to='client@example.org/client'
  id='48'>
  <getCommonNodeCommandsResponse xmlns='urn:xmpp:iot:concentrators' result='OK'>
    <command command='knockDoor' name='Knock on door' type='Simple'
      confirmationString='Are you sure you want to knock on the door?'
      failureString='Unable to knock on the door.'
      successString='Door knocked.'/>
    <command command='scheduleWakeupCall' name='Schedule wakeup call' type='Parameterized'
      failureString='Unable to schedule the wakeup call.'
      successString='Wakeup call scheduled.'/>
  </getCommonNodeCommandsResponse>
</iq>
```

--------------------------------

### Embed JSON in a Custom Protocol IQ Get

Source: https://xmpp.org/extensions/xep-0335.html

This example shows how to embed JSON within an IQ 'get' request for a custom protocol. The <json> element should be nested within a protocol-specific element.

```xml
<iq to="recipient.example.com" type="get" id="q1">
      <query xmlns="http://example.com/user-queries">
        <json xmlns="urn:xmpp:json:0">
          { "name": "romeo" }
        </json>
      </query>
    </iq>
```

--------------------------------

### Client Initiation with Pipelining

Source: https://xmpp.org/extensions/xep-0305.html

Client sends initial stream header, STARTTLS command, and TLS ClientHello. Assumes server supports XMPP STARTTLS.

```xml
<stream:stream
  from='juliet@im.example.com'
  to='im.example.com'
  version='1.0'
  xml:lang='en'
  xmlns='jabber:client'
  xmlns:stream='http://etherx.jabber.org/streams'>
<starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
TLS ClientHello
```

--------------------------------

### Actual EXI Stream for Setup Response

Source: https://xmpp.org/extensions/xep-0322.html

This is the raw EXI byte stream representing the server's setup response, including schema information.

```exi
0000000 7c 08 c9 8d cd 8c 58 58 58 98 cc 0b 58 4c 8d 4d
0000020 4b 4d 18 8e 58 8b 4e 0e 58 4c 4b 4d 18 d8 8e 0d
0000040 4e 4d 4d 4e 4d 8e 4c 72 a8 28 89 05 1a 9a 52 95
0000060 e1 00 96 b1 2c e1 6a 92 a1 3c 47 41 de 47 a4 81
0000100 a1 d1 d1 c0 e8 bc bd a9 85 89 89 95 c8 b9 bd c9
0000120 9c bd c1 c9 bd d1 bd 8d bd b0 bd b5 d5 8c 84 0a
0000140 22 33 88 e1 08 a7 60 54 45 a9 23 3b d6 d7 9c 26
0000160 31 14 77 1d 23 26 68 74 74 70 3a 2f 2f 6a 61 62
0000200 62 65 72 2e 6f 72 67 2f 70 72 6f 74 6f 63 6f 6c
0000220 2f 6d 75 63 23 6f 77 6e 65 72 c0
0000233
```

--------------------------------

### Start Database Readout Invalid Input Failure Example

Source: https://xmpp.org/extensions/xep-0326.html

This example demonstrates an IQ set request for a database readout that results in an IQ error response due to invalid input parameters, specifically a 'FormError' with a detailed error message.

```xml
<iq type='set'
    from='client@example.org/client'
    to='concentrator@example.org'
    id='68'>
  <startDatabaseReadout xmlns='urn:xmpp:iot:concentrators' xml:lang='en' databaseId='LocalDB' seqnr='3' userToken='12392748927492834'>
    <node sourceId='MeteringTopology' nodeId='Node1'/>
    <node sourceId='MeteringTopology' nodeId='Node2'/>
    <node sourceId='MeteringTopology' nodeId='Node3'/>
    <x type='submit' xmlns='jabber:x:data'>
      ...
      <field var='from' type='text-single'>
        <value>2013-03-23T00:00:00</value>
      </field>
      <field var='to' type='text-single'>
        <value>2013-03-22T00:00:00</value>
      </field>
      ...
    </x>
  </startDatabaseReadout>
</iq>

<iq type='error'
    from='concentrator@example.org'
    to='client@example.org/client'
    id='68'>
  <startDatabaseReadoutResponse xmlns='urn:xmpp:iot:concentrators' result='FormError'>
    <error var='to'>The To timestamp cannot be older than the From timestamp.</error>
  </startDatabaseReadoutResponse>
</iq>
```

--------------------------------

### XMPP IQ Get for Ping

Source: https://xmpp.org/extensions/xep-0238.html

An example of an IQ stanza used to request a ping, demonstrating the structure for sending queries between XMPP entities.

```xml
<iq from='citizen@type1.lit/foo'
    id='t1_t3'
    to='romeo@type3.lit'
    type='get'>
  <ping xmlns='urn:xmpp:ping'/>
</iq>
```

--------------------------------

### Example External Service Registrations

Source: https://xmpp.org/extensions/xep-0215.html

These examples demonstrate how to register STUN and TURN services. Multiple service types can be registered within separate <service/> elements.

```xml
<service>
  <name>stun</name>
  <desc>a server that provides Session Traversal Utilities for NAT (STUN)</desc>
  <doc>RFC 5389</doc>
</service>

<service>
  <name>turn</name>
  <desc>a server that provides Traversal Using Relays around NAT (TURN)</desc>
  <doc>RFC 5766</doc>
</service>
```

--------------------------------

### XML Equivalent of EXI Setup Response

Source: https://xmpp.org/extensions/xep-0322.html

This XML snippet shows the server's response to a client's EXI setup request, indicating agreement and providing schema information.

```xml
<?xml version="1.0"?>
<exi:setupResponse xmlns:exi='http://jabber.org/protocol/compress/exi' agreement="true" configurationId="a83b19b31e016409d3001331d9f084fc">
  <exi:schema ns="http://jabber.org/protocol/muc" bytes="1322" md5Hash="853ad555f102bb2b71da9a2f2787f4f9" />
  <exi:schema ns="http://jabber.org/protocol/muc#owner" bytes="1284" md5Hash="6e4e2257c1a4ba937fbdf71664a7e793" />
</exi:setupResponse>
```

--------------------------------

### Get All Databases (XMPP IQ)

Source: https://xmpp.org/extensions/xep-0326.html

Use the getDatabases command to retrieve a list of available databases on the concentrator. This example shows both the request and the expected result.

```xml
<iq type='get'
                    from='client@example.org/client'
                    to='concentrator@example.org'
                    id='64'>
                    <getDatabases xmlns='urn:xmpp:iot:concentrators' xml:lang='en'/>
                  </iq>
```

```xml
<iq type='result'
                    from='concentrator@example.org'
                    to='client@example.org/client'
                    id='64'>
                    <getDatabasesResponse xmlns='urn:xmpp:iot:concentrators' result='OK'>
                      <database databaseId='LocalDB' name='Local Database'/>
                      <database databaseId='LocalDBTest' name='Local Test Database'/>
                      <database databaseId='LocalDBProduction' name='Local Production Database'/>
                      <database databaseId='RemoteDB' name='Remote Database'/>
                    </getDatabasesResponse>
                  </iq>
```

--------------------------------

### Client requests to start EXI compression

Source: https://xmpp.org/extensions/xep-0322.html

Send this stanza to signal readiness to begin EXI compression after successful option negotiation. The method must be set to 'exi'.

```xml
<compress xmlns='http://jabber.org/protocol/compress'>
    <method>exi</method>
</compress>
```

--------------------------------

### HTTP Client Makes Request (No Credentials)

Source: https://xmpp.org/extensions/xep-0070.html

An example of an HTTP GET request made by a client to retrieve a resource. This is the initial request before any authentication is attempted.

```http
GET https://files.shakespeare.lit:9345/missive.html HTTP/1.1
```

--------------------------------

### Strong Emphasis Span Example

Source: https://xmpp.org/extensions/xep-0393.html

Shows text enclosed in asterisks, intended for bold display. The opening delimiter must be at the start of the block or after whitespace.

```html
<body>
  The full title is "Twelfth Night, or What You Will" but
  *most* people shorten it.
</body>
```

--------------------------------

### Service Discovery Info Request (XMPP)

Source: https://xmpp.org/extensions/xep-0481.html

An example of an XMPP IQ get request to query for service discovery information, used to determine if a feature is supported.

```xml
<iq type='get'
        from='example.org'
        to='device@example.org'
        id='disco1'>
      <query xmlns='http://jabber.org/protocol/disco#info'/>
    </iq>
```

--------------------------------

### Server Information with Software Version

Source: https://xmpp.org/extensions/xep-0485.html

This XML example extends the server information to include software version details using the 'query' element from XEP-0092.

```xml
<serverinfo xmlns="urn:xmpp:serverinfo:0">
  <domain name="shakespeare.lit">
    <federation>
      <remote-domain name='montague.net'>
        <connection type="bidi"/>
      </remote-domain>
    </federation>
  </domain>
  <query xmlns='jabber:iq:version'>
    <name>Openfire</name>
    <version>4.8.0</version>
    <os>Windows 11</os>
  </query>
</serverinfo>
```

--------------------------------

### Terminate Session (Application Setup Failed)

Source: https://xmpp.org/extensions/xep-0166.html

Use this when the application setup fails. The terminating party sends a session-terminate IQ with a <failed-application/> reason.

```xml
<iq from='juliet@capulet.lit/balcony'
id='kd82vs71'
to='romeo@montague.lit/orchard'
type='set'>
  <jingle xmlns='urn:xmpp:jingle:1'
          action='session-terminate'
          sid='a73sjjvkla37jfea'>
    <reason>
      <failed-application/>
    </reason>
  </jingle>
</iq>
```

--------------------------------

### Jingle Session-Accept with DTLS Fingerprint

Source: https://xmpp.org/extensions/xep-0320.html

Example of an IQ stanza for a Jingle session-accept where the responder includes the DTLS fingerprint information. Note the 'setup' attribute is 'active' in this case.

```xml
<iq from='juliet@capulet.lit/balcony'
    id='pn2va48j'
    to='romeo@montague.lit/orchard'
    type='set'>
  <jingle xmlns='urn:xmpp:jingle:1'
          action='session-accept'
          initiator='romeo@montague.lit/orchard'
          responder='juliet@capulet.lit/balcony'
          sid='a73sjjvkla37jfea'>
    <content creator='initiator' name='voice'>
      <description xmlns='urn:xmpp:jingle:apps:rtp:1' media='audio'>
        <payload-type id='97' name='speex' clockrate='8000'/>
        <payload-type id='18' name='G729'/>
      </description>
      <transport xmlns='urn:xmpp:jingle:transports:ice-udp:1'
                 pwd='YH75Fviy6338Vbrhrlp8Yh'
                 ufrag='9uB6'>
        <fingerprint xmlns='urn:xmpp:jingle:apps:dtls:0' hash='sha-256' setup='active'>

```

--------------------------------

### Send DNS Query using IQ Get

Source: https://xmpp.org/extensions/xep-0418.html

An example of an IQ-get stanza used to send a DNS query. The <dns/> element contains the base64-encoded DNS query.

```xml
<iq from='romeo@montague.lit/home' to='juliet@capulet.lit/chamber'
 id='s2c1' type='get'>
  <dns xmlns='urn:xmpp:dox:0'>vOIBIAABAAAAAAABB2V4YW1wbGUDb3JnAAABAAEAACkQAAAAAAAADAAKAAj5HO5JuEe+mA</dns>
</iq>
```

--------------------------------

### Server Agreement on EXI Setup

Source: https://xmpp.org/extensions/xep-0322.html

The server's response to a setup test, indicating agreement and providing a configuration ID. It mirrors the schema information sent by the client.

```xml
<setupResponse xmlns='http://jabber.org/protocol/compress/exi' version='1' strict='true'
               blockSize='1024' valueMaxLength='32' valuePartitionCapacity='100' agreement='true'
               configurationId='c76ab4ec-4993-4285-8c7a-098060581bb8'>
    <schema ns='http://www.w3.org/XML/1998/namespace' bytes='4726' md5Hash='2e2cf9072dc058dcda41b7ee77a5cb54'/>
    <schema ns='http://etherx.jabber.org/streams' bytes='3450' md5Hash='68719b98725477c46a70958d1ea7c781'/>
    <schema ns='jabber:client' bytes='6968' md5Hash='5e2d5cbf0506e3f16336d295093d66c4'/>
    <schema ns='jabber:server' bytes='6948' md5Hash='dd95bd3055dfdd69984ed427cd6356e0'/>
    <schema ns='jabber:x:roster' bytes='1077' md5Hash='00cb233dee83919067559c5dcee04f3d'/>
    <schema ns='urn:ietf:params:xml:ns:xmpp-sasl' bytes='2769' md5Hash='fd9a83f5c75628486ce18c0eb3a35995'/>
    <schema ns='urn:ietf:params:xml:ns:xmpp-streams' bytes='3315' md5Hash='75cd95aecb9f1fd66110c3ddcf00c9b8'/>
    <schema ns='urn:ietf:params:xml:ns:xmpp-tls' bytes='688' md5Hash='dc18bc4da35bc1be7a6c52aa43330825'/>
    <schema ns='urn:ietf:params:xml:ns:xmpp-stanzas' bytes='3133' md5Hash='1a8d21588424f9134dc497de64b10c3f'/>
    <schema ns='http://jabber.org/protocol/compress/exi' bytes='15094' md5Hash='8b8f91b95d9101f0781e0ba9b4e106be'/>
    <schema ns='urn:xmpp:iot:control' bytes='6293' md5Hash='74dcea52300e8c8df8c4de2c9e90495b'/>
</setupResponse>
```

--------------------------------

### VPI Delegation Example

Source: https://xmpp.org/extensions/xep-0151.html

This VPI configuration demonstrates delegation, directing the client to another VPI file.

```xml
<location>
  <delegate>http://www.shakespeare.com/_vpi.xml</delegate>
</location>
```

--------------------------------

### Server returns error to blocked entity for IQ get

Source: https://xmpp.org/extensions/xep-0016.html

Example of a server responding with a <service-unavailable/> error to a blocked entity's IQ stanza, as per XEP-0016.

```xml
<iq type='error'
  from='romeo@example.net'
  to='tybalt@example.com/pda'
  id='probing1'>
<query xmlns='jabber:iq:version'/>
<error type='cancel'>
  <service-unavailable
      xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
</error>
</iq>
```

--------------------------------

### Initiate Version Negotiation (Client)

Source: https://xmpp.org/extensions/xep-0043.html

The client sends an IQ stanza with the desired database version to initiate the session. This is the first step in establishing a compatible connection.

```xml
<iq id="000" type="get" to="db.host">
  <database
      xmlns="http://openaether.org/projects/jabber_database.html">
      <version>0.1</version>
    </database>
</iq>
```

--------------------------------

### Mixer Indicates Speaking Status

Source: https://xmpp.org/extensions/xep-0327.html

This example demonstrates how a mixer indicates when calls joined to it start or stop speaking. This is useful for features like active speaker detection.

```xml
<presence from='myMixer@mixer.shakespeare.lit'
          to='juliet@capulet.lit/balcony'>
  <started-speaking xmlns='urn:xmpp:rayo:1' call-uri='xmpp:callA@call.shakespeare.lit'/>
</presence>

<presence from='myMixer@mixer.shakespeare.lit'
          to='juliet@capulet.lit/balcony'>
  <started-speaking xmlns='urn:xmpp:rayo:1' call-uri='xmpp:callB@call.shakespeare.lit'/>
</presence>

<presence from='myMixer@mixer.shakespeare.lit'
          to='juliet@capulet.lit/balcony'>
  <stopped-speaking xmlns='urn:xmpp:rayo:1' call-uri='xmpp:callB@call.shakespeare.lit'/>
</presence>

<presence from='myMixer@mixer.shakespeare.lit'
          to='juliet@capulet.lit/balcony'>
  <stopped-speaking xmlns='urn:xmpp:rayo:1' call-uri='xmpp:callA@call.shakespeare.lit'/>
</presence>
```

--------------------------------

### Propose EXI Compression Parameters

Source: https://xmpp.org/extensions/xep-0322.html

Client sends a setup stanza with proposed EXI compression parameters, including schema details like namespace, byte size, and MD5 hash. This is used to initiate EXI compression negotiation.

```xml
<setup xmlns='http://jabber.org/protocol/compress/exi' version='1' strict='true' blockSize='1024' valueMaxLength='32' valuePartitionCapacity='100'>
    <schema ns='http://www.w3.org/XML/1998/namespace' bytes='4726' md5Hash='2e2cf9072dc058dcda41b7ee77a5cb54'/>
    <schema ns='http://etherx.jabber.org/streams' bytes='3450' md5Hash='68719b98725477c46a70958d1ea7c781'/>
    <schema ns='jabber:client' bytes='6968' md5Hash='5e2d5cbf0506e3f16336d295093d66c4'/>
    <schema ns='jabber:server' bytes='6948' md5Hash='dd95bd3055dfdd69984ed427cd6356e0'/>
    <schema ns='jabber:x:roster' bytes='1077' md5Hash='00cb233dee83919067559c5dcee04f3d'/>
    <schema ns='urn:ietf:params:xml:ns:xmpp-sasl' bytes='2769' md5Hash='fd9a83f5c75628486ce18c0eb3a35995'/>
    <schema ns='urn:ietf:params:xml:ns:xmpp-streams' bytes='3315' md5Hash='75cd95aecb9f1fd66110c3ddcf00c9b8'/>
    <schema ns='urn:ietf:params:xml:ns:xmpp-tls' bytes='688' md5Hash='dc18bc4da35bc1be7a6c52aa43330825'/>
    <schema ns='urn:ietf:params:xml:ns:xmpp-stanzas' bytes='3133' md5Hash='1a8d21588424f9134dc497de64b10c3f'/>
    <schema ns='http://jabber.org/protocol/compress/exi' bytes='15094' md5Hash='8b8f91b95d9101f0781e0ba9b4e106be'/>
    <schema ns='urn:xmpp:iot:control' bytes='6293' md5Hash='74dcea52300e8c8df8c4de2c9e90495b'/>
    <schema ns='urn:xmpp:iot:sensordata' bytes='8092' md5Hash='49b101e7deea39ccc31340a3c7871c43'/>
    <schema ns='urn:xmpp:iot:interoperability' bytes='1275' md5Hash='5d39845a0082715ff8807691698353bb'/>
    <schema ns='urn:xmpp:iot:provisioning' bytes='6303' md5Hash='3ed5360bc17eadb2a8949498c9af3f0c'/>
</setup>
```

--------------------------------

### REST Method Call Example

Source: https://xmpp.org/extensions/xep-0332.html

Illustrates making a RESTful GET request and receiving a response via XMPP IQ stanzas. This is suitable for interacting with REST APIs through XMPP.

```xml
<iq type='set'
    from='httpclient@example.org/browser'
    to='httpserver@example.org'
    id='16'>
   <req xmlns='urn:xmpp:http' method='GET' resource='/api/multiplicationtable?m=5' version='1.1'>
       <headers xmlns='http://jabber.org/protocol/shim'>
           <header name='Host'>example.org</header>
       </headers>
   </req>
</iq>

<iq type='result'
    from='httpserver@example.org'
    to='httpclient@example.org/browser'
    id='16'>
   <resp xmlns='urn:xmpp:http' version='1.1' statusCode='200' statusMessage='OK'>
       <headers xmlns='http://jabber.org/protocol/shim'>
           <header name='Date'>Fri, 05 May 2013 15:01:53GMT-4</header>
           <header name='Server'>Clayster</header>
           <header name='Content-Type'>text/xml</header>
           <header name='Content-Length'>...</header>
       </headers>
       <data>
           <xml>
               <table>
                   <value n='1' nTimesM='5'/>
                   <value n='2' nTimesM='10'/>
                   <value n='3' nTimesM='15'/>
                   <value n='4' nTimesM='20'/>
                   <value n='5' nTimesM='25'/>
                   <value n='6' nTimesM='30'/>
                   <value n='7' nTimesM='35'/>
                   <value n='8' nTimesM='40'/>
                   <value n='9' nTimesM='45'/>
                   <value n='10' nTimesM='50'/>
               </table>
           </xml>
       </data>
   </resp>
</iq>
```

--------------------------------

### Discover Available Form Templates

Source: https://xmpp.org/extensions/xep-0346.html

Perform a disco#items query on a PubSub service to find nodes starting with 'fdp/template/'. This example shows how to discover available form templates.

```xml
<iq id="34385937-3740-411d-a360-374e9ba73202" to="pubsub.stan.isode.net" type="get">
  <query xmlns="http://jabber.org/protocol/disco#items"/>
</iq>

<iq from='pubsub.stan.isode.net' to='sysop@stan.isode.net/4d67a58b4d16cc1d' type='result' id='34385937-3740-411d-a360-374e9ba73202'>
  <query xmlns='http://jabber.protocol/disco#items'>
    <item jid='pubsub.stan.isode.net' node='fdp/submitted/stan.isode.net/accidentreport' name='AccidentReport'/>
    <item jid='pubsub.stan.isode.net' node='fdp/template/stan.isode.net/accidentreport' name='AccidentReport'/>
  </query>
</iq>
```

--------------------------------

### Provide HTTP Basic Auth Parameters

Source: https://xmpp.org/extensions/xep-0104.html

This example shows how to provide additional parameters for basic HTTP authentication, including realm, username, and password.

```xml
<message to='client@domain.com'>
  <url-data xmlns='http://jabber.org/protocol/url-data'
      xmlns:http='http://jabber.org/protocol/url-data/scheme/http'
      target='http://www.jabber.org/members/index.php'>
    <http:auth scheme='basic'>
      <http:auth-param name='realm' value='www.jabber.org'/>
      <http:auth-param name='username' value='defaultuser'/>
      <http:auth-param name='password' value='defaultpwd'/>
    </http:auth>
  </url-data>
</message>
```

--------------------------------

### Example VPI Configuration

Source: https://xmpp.org/extensions/xep-0151.html

This XML configuration defines rules for mapping URLs to virtual presence services. It includes handling specific domains like .com and .de, and a general rule for other domains.

```xml
<?xml version='1.0' ?>
<vpi xmlns='http://schema.bluehands.de/virtual-presence-info'>

  <!-- handle .com(s) by another file -->
  <location match='^http://.*\.com/.*'>
    <delegate>http://vpi.vp.bluehands.de/lluna-2.5.2/dotcom-vpi.xml</delegate>
  </location>

  <!-- handle .de(s) by another file -->
  <location match='^http://.*\.de/.*'>
    <delegate>http://vpi.vp.bluehands.de/lluna-2.5.2/dotde-vpi.xml</delegate>
  </location>

  <!-- all others go here -->
  <location match='^http://([^/]+)($|/.*$)'>
    <service>xmpp:location.virtual-presence.org</service>
      <!-- one location per website  -->
      <name>\1</name>
      <digest/>
  </location>
</vpi>
```

--------------------------------

### User Activity With Time Period

Source: https://xmpp.org/extensions/xep-0149.html

Publish user activity with 'Start' and 'Stop' SHIM headers to define the duration of the activity. This example shows publishing a 'relaxing' and 'partying' activity.

```xml
<iq type='set'
    from='juliet@capulet.com/balcony'
    to='pubsub.shakespeare.lit'
    id='activity1'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
    <publish node='generic/juliet-activity'>
      <item id='current'>
        <activity xmlns='http://jabber.org/protocol/activity'>
          <relaxing>
            <partying/>
          </relaxing>
          <text xml:lang='en'>My best friend&apos;s birthday!</text>
        </activity>
        <headers xmlns='http://jabber.org/protocol/shim'>
          <header name='Start'>2005-03-17T19:00:00Z</header>
          <header name='Stop'>2005-03-17T23:00:00Z</header>
        </headers>
      </item>
    </publish>
  </pubsub>
</iq>
```

--------------------------------

### Bidirectional Streams with Server Dialback

Source: https://xmpp.org/extensions/xep-0288.html

This example illustrates the stream negotiation for bidirectional streams utilizing Server Dialback. It shows the initial stream setup and feature negotiation before proceeding to dialback.

```xml
<!-- Client -->
<stream:stream xmlns:stream='http://etherx.jabber.org/streams'
               xmlns='jabber:server' xmlns:db='jabber:server:dialback'
               to='montague.lit' from='capulet.lit'
               xml:lang='en' version='1.0'>
<!-- Server -->
<stream:stream xmlns='jabber:server' xmlns:db='jabber:server:dialback'
               xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en'
               id='65b30434afd7646699d077f7affcb2c120c48e18'
               from='montague.lit' to='capulet.lit' version='1.0'>
<stream:features>
  <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
  <bidi xmlns='urn:xmpp:features:bidi'/>
</stream:features>
<!-- Client -->
<starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
<!-- Server -->
<proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
<!-- Client -->
<stream:stream xmlns:stream='http://etherx.jabber.org/streams'
               xmlns='jabber:server' xmlns:db='jabber:server:dialback'
               to='montague.lit' from='capulet.lit'
               xml:lang='en' version='1.0'>
<!-- Server -->
<stream:stream xmlns='jabber:server' xmlns:db='jabber:server:dialback'
               xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en'
               id='b5cd769b1dc292c6f6557fe76cabc4d112333f9a'
               from='montague.lit' to='capulet.lit' version='1.0'>
<stream:features>
  <mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'/>
  <bidi xmlns='urn:xmpp:features:bidi'/>
</stream:features>
```

--------------------------------

### Example PubSub Items with CAP-Vs

Source: https://xmpp.org/extensions/xep-0395.html

This example demonstrates how a PubSub service returns items along with their associated Compare-And-Publish Values (CAP-Vs). The CAP-Vs are provided in a `<cap-v-map/>` element, mapping item IDs to their respective CAP-V hashes.

```xml
<iq type='result'
    from='pubsub.shakespeare.lit'
    to='francisco@denmark.lit/barracks'
    id='items1'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
    <items node='princely_musings'>
      <item id='368866411b877c30064a5f62b917cffe'>
        <entry xmlns='http://www.w3.org/2005/Atom'>
          <title>The Uses of This World</title>
          <summary>
O, that this too too solid flesh would melt
Thaw and resolve itself into a dew!
          </summary>
        </entry>
      </item>
      <item id='3300659945416e274474e469a1f0154c'>
        <entry xmlns='http://www.w3.org/2005/Atom'>
          <title>Ghostly Encounters</title>
          <summary>
O all you host of heaven! O earth! what else?
And shall I couple hell? O, fie! Hold, hold, my heart;
And you, my sinews, grow not instant old,
But bear me stiffly up. Remember thee!
          </summary>
        </entry>
      </item>
      <item id='4e30f35051b7b8b42abe083742187228'>
        <entry xmlns='http://www.w3.org/2005/Atom'>
          <title>Alone</title>
          <summary>
Now I am alone.
O, what a rogue and peasant slave am I!
          </summary>
        </entry>
      </item>
      <cap-v-map xmlns='urn:xmpp:pubsub:cap:0'>
        <cap-value-map-entry
          item-id='368866411b877c30064a5f62b917cffe'
          cap-value='35a204c2-5d6c-43a2-8e0d-a235a627b04a'/>
        <cap-value-map-entry
          item-id='3300659945416e274474e469a1f0154c'
          cap-value='166b7c04-ed4d-4872-aa56-a58268da84e2'/>
        <cap-value-map-entry
          item-id='4e30f35051b7b8b42abe083742187228'
          cap-value='67f7f792-f2ee-4918-8894-36a3c4a6dd5f'/>
      </cap-v-map>
    </items>
  </pubsub>
</iq>
```

--------------------------------

### Directory Requests vCard Data from Server (XMPP IQ)

Source: https://xmpp.org/extensions/xep-0309.html

A directory sends an IQ 'get' request to a server to retrieve its vCard information. This example uses the vCard 4.0 namespace.

```xml
<iq from='xmpp.net'
    id='lw71bs73'
    to='jabber.org'
    type='get'>
  <vcard xmlns='urn:ietf:params:xml:ns:vcard-4.0'/>
</iq>
```