• To: Rick Jelliffe <ricko@a...>
• Subject: Re: Revised Internet-Draft: Media Feature - xmlns
• From: "Simon St.Laurent" <simonstl@s...>
• Date: 24 Jan 2002 23:56:53 -0500
• Cc: xml-dev@l...
• In-reply-to: <013201c1a550$3b4a0d00$4bc8a8c0@A...>
• References: <200201250244.VAA27345@m...> <013201c1a550$3b4a0d00$4bc8a8c0@A...>

On Thu, 2002-01-24 at 22:27, Rick Jelliffe wrote:
> But since such a streaming XML process would be simularly impeded
> from generating the correct MIME information talked about by Simon's
> draft, I don't see how this applies. But careful wording should be able
> to cover that case.

It's entirely possible that such processes would be completely incapable
of providing any MIME description (Media Type or Media Feature) beyond
the Media Type application/xml before they commenced sending the XML
information.

I'm not particularly fond of the raw application/xml in cases where more
information is available, but it certainly provides a baseline in this
case.

Now to find the "careful wording" to cover that case properly...

xmlns="*" for xmlns="[who knows?]" ???
 
-- 
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com

• References:
  • Re: Revised Internet-Draft: Media Feature - xmlns
    • From: Mark Baker <distobj@a...>
  • Re: Revised Internet-Draft: Media Feature - xmlns
    • From: "Rick Jelliffe" <ricko@a...>

• Prev by Date: Re: Revised Internet-Draft: Media Feature - xmlns
• Next by Date: Re: Revised Internet-Draft: Media Feature - xmlns
• Previous by thread: Re: Revised Internet-Draft: Media Feature - xmlns
• Next by thread: Re: Revised Internet-Draft: Media Feature - xmlns
• Index(es):
  • Date
  • Thread