diff --git a/xep-0156.xml b/xep-0156.xml index 21febf7e..593c8a6d 100644 --- a/xep-0156.xml +++ b/xep-0156.xml @@ -200,6 +200,7 @@ _xmppconnect IN TXT "_xmpp-client-websocket=wss://web.example.com:443/ws"

The following business rules apply:

    +
  1. Services implementing this XEP MUST offer the information in the Extensible Resource Descriptor (XRD) format and SHOULD additionally provide the JRD format (both formats are specified in &rfc6415;).
  2. HTTP queries for host-meta information MUST be used only as a fallback after the methods specified in RFC 6120 have been exhausted.
  3. A domain SHOULD NOT present information in host-meta link records that is available via the DNS SRV records defined in RFC 6120.
  4. The order of XMPP related link entries in the host-meta file SHOULD NOT be interpreted as significant by the presenting domain or the receiving entity.
  5. @@ -208,7 +209,6 @@ _xmppconnect IN TXT "_xmpp-client-websocket=wss://web.example.com:443/ws"

    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.

    ... @@ -219,7 +219,7 @@ _xmppconnect IN TXT "_xmpp-client-websocket=wss://web.example.com:443/ws" ... ]]> -

    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 an alternative JSON 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: