Re: application/beep+xml

hi. i think you raise three issues:

1. text/xml isn't the right tag to use for xml-based profiles

2. rfc1982 on sequence number arithmetic should be referenced, e.g.,

   Consult Sections 2 through 5 of [8] for a discussion of the arithmetic
   properties of sequence numbers.

3. the "URL:" in things like "<URL:http://iana.org/>" should be removed


2 & 3 are editorial, and probably not all that controversial. if anyone
objects to making these changes, speak up.


the first issue requires more discussion.

i'll agree that text/xml isn't optimal for the reasons you suggest (e.g.,
not intended for display to humans).

so, if text/xml is out, what should we use instead?

the things being moved around in the xml-based profiles described in beep
are protocol exchanges, not documents. when a channel is started, a
negotiation process is used to determine which profile is bound to the
channel. the registration for this profile defines what the exchanges look
like.

so, having each profile register its own mime type is at best redundant.
worse, since the whole point of using URIs to identify profiles was to get
away from a centralized registry, a mime type per profile negates this
property.

this leaves application/xml, which is as good a choice as any, i guess...

/mtr