%ents; ]>
Software Information This document specifies an extended data format whereby XMPP service discovery responses can include detailed information about the software application that powers a given XMPP entity for including detailed data about the in service discovery responses. &LEGALNOTICE; 0232 Proposed Standards Track Standards Council XMPP Core XEP-0004 XEP-0030 NOT_YET_ASSIGNED &stpeter; 0.3 2009-02-26 psa

Per Last Call feedback, removed icons for presence states; redefined the icon field to use media element per XEP-0221.

0.2 2008-03-14 psa

Added icon fields.

0.1 2008-01-30 psa

Initial published version.

0.0.3 2008-01-23 psa

Added software field; generalized to be software information, not client information.

0.0.2 2008-01-22 psa

Clarified relationship to Software Version (XEP-0092).

0.0.1 2008-01-21 psa

First draft.

&xep0128; defines a way for an XMPP entity to include extended information in its responses to &xep0030; information requests. This document specifies a usage of XEP-0128 whereby an XMPP entity can provide detailed data about itself in such responses. This protocol is intended to replace &xep0092; for software information discovery (thus reducing or eliminating the need for distinct software version requests) and also provides a format that can be encapsulated into &xep0115; notifications.

To illustrate this usage, consider the following example of a disco#info request-response interaction that includes detailed client information:

]]>

Upon receiving the disco#info request, the software replies and includes extended information in a data form (&xep0004;), where the icon is communicated using the format defined in &xep0221;.

urn:xmpp:dataforms:softwareinfo http://www.shakespeare.lit/clients/exodus.jpg cid:sha1+f24030b8d91d233bac14777be5ab531ca3b9f102@bob.xmpp.org Windows XP Exodus 0.9.1 ]]>

The fields have the following meaning:

Service discovery information is typically world-readable. Therefore, care should be taken in exposing information that may make it easier for a potential attacker to target the publishing entity's system (e.g., the operating system on which the software is running).

This document requires no interaction with &IANA;.

The ®ISTRAR; shall include the following information in its registries.

&xep0068; defines a process for standardizing the fields used within Data Forms qualified by a particular namespace, and XEP-0128 describes how to use field standardization in the context of service discovery. This section registers fields for software information scoped by the "urn:xmpp:dataforms:softwareinfo" FORM_TYPE.

urn:xmpp:dataforms:softwareinfo XEP-0232 Forms enabling the communication of detailed information about an XMPP client. ]]>

Thanks to Dave Cridland, Olivier Goffart, Joe Hildebrand, Etan Reisner, Remko Tronçon, and Jiří Zárevúcký for their comments.