Fix reference to RFC 6415 and organize requirements more clearly. This raises the JSON requirement from MAY (OPTIONAL) to SHOULD (effectively), to accustom web-based software.
The following business rules apply:
The following examples show two host-meta link records: the first indicates support for the XMPP Over BOSH connection method defined in XEP-0124 and XEP-0206 and the second indicates support for the XMPP Over WebSocket connection method defined in &rfc7395;.
-As specified in RFC 6120 §3, support for the XML encoding of the host-meta resource is REQUIRED while alternative representations such as JSON are OPTIONAL.
It is possible to use an alternative JSON format for host-meta information, in which case the above example would be presented as:
+It is possible to use additionally a JSON-based format for host-meta information. The JSON representation of the host metadata is named JRD and specified in Appendix A of &rfc6415;. The above XRD example would be presented in JRD as:
Add 'status-addresses' value in registrar, with example.
The administrators of an XMPP service may desire to advertise contact information related to that service.
Values of 'status-addresses' form field MUST be valid URIs, i.e. comply with the + 'xs:anyURI' datatype of &w3xmlschema2;. Values of the 'abuse-addresses', + 'admin-addresses', 'feedback-addresses', 'sales-addresses', + 'security-addresses' and 'support-addresses' SHOULD be valid URIs.
+To illustrate this usage, consider the following example of a disco#info request sent to the mythical shakespeare.lit XMPP server: