File:  beep01extracts.txt
From:  http://www.ietf.org/internet-drafts/draft-ietf-beep-framework-01.txt
Date:  2000-09-14

--------------------------------------------------
2.2.2.2 XML-based Profiles

   If a profile uses XML to structure its messages, then only XML's
   baseline facilities (as described in the XML 1.0 specification[3])
   are allowed. Additional XML features (e.g., namespaces) are made
   available only by being explicitly discussed in a given profile's
   specification.

   In particular this limitation allows use of only the five predefined
   general entities references ("&", "<", ">", "'", and
   """) and numeric entity references in the messages exchanged.

   Further, because the profile registration template defines the
   messages exchanged over a channel, the XML documents exchanged in
   each message needn't have either a "XML" declaration (e.g., <?xml
   version="1.0" ?>) or a "DOCTYPE" declaration (e.g., <!DOCTYPE ...>).
   All other XML 1.0 instructions (e.g., CDATA blocks, processing
   instructions, and so on) are allowed.

   Finally, because the "XML" declaration isn't present, the default
   character set for XML-based profiles is UTF-8. If another character
   set is desired, a "Content-Type" entity-header should be used to
   specify the character set in question.


-----------------------------------------------------------------------------
6.2 BXXP Channel Management DTD

   <!--
     DTD for BXXP Channel Management, as of 2000-09-04


     Refer to this DTD as:

       <!ENTITY % BXXP PUBLIC "-//Blocks//DTD BXXP//EN"
                  "http://xml.resource.org/profiles/BXXP/bxxp.dtd">
       %BXXP;
     -->


   <!--
     DTD data types:

           entity        syntax/reference     example
           ======        ================     =======
       a channel number
           CHAN          1..2147483647        1

       authoritative profile identification
           URI          c.f., [RFC-2396]      http://invisible.net/

       one or more feature tokens, seperated by space
           FTRS         NMTOKENS              "magic"

       zero or more language tags
           LOCS         NMTOKENS              "en-US"

       a language tag
           LANG         c.f., [RFC-1766]      "en", "en-US", etc.

       a 3-digit reply code
           XYZ           [1-5][1-9][1-9]      500
   -->


   <!ENTITY % CHAN       "CDATA">
   <!ENTITY % URI        "CDATA">
   <!ENTITY % FTRS       "NMTOKENS">
   <!ENTITY % LOCS       "NMTOKEN">
   <!ENTITY % LANG       "NMTOKEN">
   <!ENTITY % XYZ        "CDATA">

   <!--
     BXXP messages

        role       MSG         RSP         ERR
       =======     ===         ===         ===
       I and L                 greeting    error

       I or L      start       profile     error

       I or L      close       ok          error
     -->


   <!ELEMENT greeting    (profile)*>
   <!ATTLIST greeting
             features    %FTRS;            #IMPLIED
             localize    %LOCS;            "i-default">

   <!ELEMENT start       (profile)+>
   <!ATTLIST start
             number      %CHAN;             #REQUIRED
             serverName  CDATA              #IMPLIED>

   <!-- profile element is empty if contained in a greeting -->
   <!ELEMENT profile     ANY>
   <!ATTLIST profile
             uri         %URI;              #REQUIRED>

   <!ELEMENT close       (#PCDATA)*>
   <!ATTLIST close
             number      %CHAN;             "0"
             code        %XYZ;              #REQUIRED
             xml:lang    %LANG;             #IMPLIED>

   <!ELEMENT ok          EMPTY>

   <!ELEMENT error       (#PCDATA)*>
   <!ATTLIST error
             code        %XYZ;              #REQUIRED
             xml:lang    %LANG;             #IMPLIED>


-------------------------
6.4 TLS Transport Security Profile DTD

   <!--
     DTD for the TLS Transport Security Profile, as of 2000-09-04


     Refer to this DTD as:

       <!ENTITY % TLS PUBLIC "-//Blocks//DTD TLS//EN"
                  "http://xml.resource.org/profiles/TLS/tls.dtd">
       %TLS;
     -->


   <!--
     TLS messages

        role       MSG         RSP         ERR
       ======      ===         ===         ===
       I or L      ready       proceed     error
     -->


   <!ELEMENT ready       EMPTY>
   <!ATTLIST ready
             version     CDATA              "1">

   <!ELEMENT proceed     EMPTY>



-----------------------------------
6.6 SASL Family of Profiles DTD

   <!--
     DTD for the SASL Family of Profiles, as of 2000-09-04


     Refer to this DTD as:

       <!ENTITY % SASL PUBLIC "-//Blocks//DTD SASL//EN"
                  "http://xml.resource.org/profiles/sasl/sasl.dtd">
       %SASL;
     -->


   <!--
     SASL messages

        role       MSG         RSP         ERR
       ======      ===         ===         ===
       I or L      blob        blob        error
     -->


   <!ELEMENT blob        (#PCDATA)*>
   <!ATTLIST blob
             xml:space   (default|preserve)
                                           "preserve"
             status      (abort|complete|continue)
                                            "continue">