- From: Mark Nottingham <mnot@mnot.net>
- Date: Tue, 19 Feb 2002 17:29:56 -0800
- To: "Simon St.Laurent" <simonstl@simonstl.com>
- Cc: www-tag@w3.org, ietf-xml-mime@imc.org
Is it possible to negotiate a content feature with current HTTP implementations? AFAIK it isn't, but it would be possible to do so on a media type attribute, using server-driven negotiation. If I'm missing something, a reference would be very much appreciated. Cheers, On Tue, Feb 19, 2002 at 09:28:05PM -0500, Simon St.Laurent wrote: > On Tue, 2002-02-19 at 19:20, Mark Nottingham wrote: > > Might I suggest that any revision of RFC3023 include a new parameter > > for application/xml and text/xml (say, 'rootNS') that contains the > > root element's namespace URI, to allow HTTP content negotiation with > > current implementations? Yes, this won't address cases where there is > > a need to negotiate on more than one namespace in the document, but > > it will certainly help with the simple cases, where dispatch is based > > upon the root element's namespace (which seems to be the direction > > things are going in). > > You're welcome to register a rootNS content feature. > > I have to admit that I don't understand or sympathize with the > fascination with root element namespaces, and don't believe that RFC > 3023 needs to add any XML-specific parameters, but a content feature > should take care of what you're looking for. > > -- > Simon St.Laurent > Ring around the content, a pocket full of brackets > Errors, errors, all fall down! > http://simonstl.com > -- Mark Nottingham http://www.mnot.net/
Received on Tuesday, 19 February 2002 20:29:57 UTC