Re: [Minutes] 20 Oct 2003 TAG teleconf (abstractComponentRefs-37, URI Syntax, RFC 3023)

I am traveling this week and do not have the network access, the time, or 
quite possibly the expertise to follow all the subtleties and implications 
of this thread.  I do notice the proposal to supercede RFC 3023, which as 
I think you're aware is referenced by SOAP Part 2 and the associated 
application/soap+xml media type.  Perhaps one of you might send a note to 
distApp giving the protocols WG a heads up regarding what's being 
considered and why?  I could try this evening, but I'm unlikely to give a 
good explanation.  Many thanks.

Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142

MURATA Makoto <>
Sent by:
10/24/2003 06:48 AM

        To:     Chris Lilley <>
        cc:, (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        Re: [Minutes] 20 Oct 2003 TAG teleconf (abstractComponentRefs-37, URI 
Syntax, RFC 3023)

> As a first cut though it would do what you said above:
> - deprecate text/xml.
> - the optianal charset parameter of application/xml
>   (and non-text/*+xml) is recommended if and
>   only if the value is correct.

Then, everybody will be happy. I would propose to publish an 
RFC that *obsoletes* RFC 3023.  Such an RFC is better than an update RFC, 
since other things have to be changed (e.g., we have to mention XML 1.1).
I volunteer to write such an RFC together with somebody from W3C.


MURATA Makoto <>

Received on Monday, 27 October 2003 00:26:49 UTC