MIME namespace...

[Chris Maden]

[Gabe Beged-Dov]
> <PICTURE
>         xmlns:mime="http://www.ietf.org/rfc2045"
>         mime:content-type="image/jpeg"
>         href="ftp://ftp.pictures.com/pretty.jpg">
> Its a pretty picture
> </PICTURE>

It's a good proposal for embedding MIME information in documents.  But
one of the great values of MIME is its use with unknown quantities and
content negotiation; depending on user settings and user agent
capabilities, the pretty picture might be a PNG, a JPEG, a GIF, a BMP,
or EPS.

So if your resources are guaranteed to be in a single format, this is
a good idea.  But I'd rather leave content typing where it belongs,
with the resource itself, not with the reference thereto.

-Chris
-- 
<!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
"<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.617.499.7487
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)