[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Revised Internet-Draft: Media Feature - xmlns

• To: "Rick Jelliffe" <ricko@a...>, <xml-dev@l...>
• Subject: Re: Revised Internet-Draft: Media Feature - xmlns
• From: Tim Bray <tbray@t...>
• Date: Fri, 25 Jan 2002 10:00:47 -0800
• In-reply-to: <00c801c1a547$23b4ff50$4bc8a8c0@A...>
• References: <1011891343.5317.339.camel@l...>

At 01:22 PM 25/01/02 +1100, Rick Jelliffe wrote:
>Is there value in constructing pipes when there are no
>feasible connectors?   At the moment, the WWW basically
>runs on 
>  file extension -> MIME type -> type handler
>We know that a document is xslt not because of its top-level
>element but because it is .xsl or .xslt.

I'm not sure I agree.  An increasingly high proportion
of stuff being pumped around the web (and I suspect an
even higher proportion of XML) is generated dynamically
by code that knows what's going to be in it and could
straightforwardly emit helpful MIME headers.

Having said that, I'm still not convinced that a 
laundry list of namespaces that occur somewhere in
this doc is all that helpful in many applications, but
the RFC seems a harmless, lightweight, and standards-
compliant way to enable the possibility. -Tim

• References:
  • Revised Internet-Draft: Media Feature - xmlns
    • From: "Simon St.Laurent" <simonstl@s...>
  • Re: Revised Internet-Draft: Media Feature - xmlns
    • From: "Rick Jelliffe" <ricko@a...>

• Prev by Date: Re: Entity resolution vs. URI resolution
• Next by Date: Re: Entity resolution vs. URI resolution
• Previous by thread: Re: Revised Internet-Draft: Media Feature - xmlns
• Next by thread: Instance-centric Semantics (WAS RE: Being "precise" vs being "human")
• Index(es):
  • Date
  • Thread