tag

can someone explain me, why developers give us a separate
<response 
id="xxx" /> tag?
it is break a relation between response and it's id.

why not include response ID as attribute to every high-level
tag:
C: <rosterList id="A7" />
S: <rosterItem id="A7"
ask="subscribe" peer="user1host" 
subscription="none" />
S: <rosterItem id="A7"
ask="subscribe" peer="user1host" 
subscription="none" />

or at least make frame-tag:
C: <rosterList id="A7" />
S: <response id="A7">
S:   <rosterItem id="A7"
ask="subscribe" peer="user1host" 
subscription="none" />
S:   <rosterItem id="A7"
ask="subscribe" peer="user1host" 
subscription="none" />
S: </response>

p.s. please make a bit more sessions examples in XIMSS
manual. There are 
no examples in "Instant Messaging" and
"Roster and Presence" sections.
commented example of common session [connection, roaster
retrieving, 
change of status, sending and receiving messages] , would be
great too.

best regards

############################################################
#
This message is sent to you because you are subscribed to
  the mailing list <CGatePromail.stalker.com>.
To unsubscribe, E-mail to: <CGatePro-offmail.stalker.com>
To switch to the DIGEST mode, E-mail to
<CGatePro-digestmail.stalker.com>
To switch to the INDEX mode, E-mail to
<CGatePro-indexmail.stalker.com>
Send administrative queries to  <CGatePro-requestmail.stalker.com>