RE: [BXXPwg] application/beep+xml

Marshall, my only question is whether some of the Security Considerations of
<http://www.imc.org/draft-murata-xml> additionally apply.  Since you are
prohibiting the use of external entities, you avoid most of the risks,
however there is still the possibility of someone parsing the data with a
standard XML processor.  Also, you might explicitly want to mention whether
this type follows RFC 2376bis's advice on use of the BOM (section 4),
XPointer syntax (section 5), and Base URI (section 6).  Or, you could just
leave these things undefined. 

Thanks.

                - dan
--
Dan Kohn <mailto:dan@xxxxxxxxxxx>
<http://www.dankohn.com>  <tel:+1-650-327-2600>

-----Original Message-----
From: Marshall Rose [mailto:mrose@xxxxxxxxxxxxxxxx]
Sent: Tuesday, 2000-10-24 08:21
To: bxxpwg@xxxxxxxxxxxxxxxxxxx
Cc: mrose@xxxxxxxxxxxxxxxx
Subject: [BXXPwg] application/beep+xml


hi. after review, it looks like application/beep+xml is probably the
better choice. unless folks believe otherwise, here is what i propose to
add to the draft. please comment.
    
thanks,
    
/mtr

ps: naturally, the examples will all change to use this media type
instead of text/xml
    
                                  #######
    
6.4 Registration: application/beep+xml

   MIME media type name: application

   MIME subtype name: beep+xml

   Required parameters: none

   Optional parameters: charset (defaults to "UTF-8"[RFC 2279])

   Encoding considerations: always use binary

   Security considerations: none, per se; however, any BEEP profile
      which uses this media type must describe its relevant security
      considerations

   Interoperability considerations: n/a

   Published specification: This media type is a proper subset of the
      the XML 1.0 specification[2]. Two restrictions are made. 

      First, no entity references other than the five predefined
      general entities references ("&amp;", "&lt;", "&gt;", "&apos;",
      and "&quot;") and numeric entity references may be present. 

      Second, neither the "XML" declaration (e.g., <?xml version="1.0"
      ?>) nor the "DOCTYPE" declaration (e.g., <!DOCTYPE ...>) may be
      present. (Accordingly, if another character set other than UTF-8
      is desired, then the "charset" parameter must be present.) 

      All other XML 1.0 instructions (e.g., CDATA blocks, processing
      instructions, and so on) are allowed.

   Applications which use this media type: any BEEP profile wishing to
      make use of this XML 1.0 subset

   Additional Information: none

   Contact for further information: c.f., the "Author's Address"
      section of this memo

   Intended usage: limited use

   Author/Change controller: the IESG


_______________________________________________
BXXPwg mailing list
BXXPwg@xxxxxxxxxxxxxxxxxxx
http://lists.invisible.net/mailman/listinfo/bxxpwg