Lists Home |
Date Index |
- From: David Megginson <email@example.com>
- To: "'xml-dev Mailing List'" <firstname.lastname@example.org>
- Date: Thu, 5 Feb 1998 09:09:21 -0500
Gavin McKenzie writes:
> David Megginson wrote:
> > [snip]
> > XML documents may (and perhaps, usually will) contain non-XML objects
> > such as wordprocessor documents, spreadsheets, MPEG clips, Java
> > applets, audio sequences, and many others -- to date, thankfully, no
> > one has proposed uuencoding any these and dumping them inline between
> > a start and and tag.
> > [snip]
> Am I to understand from this paragraph that there would be
> something wrong with uuencoded or base64'd resources, like audio
> clips or even a Java class, between a start and end tag?
You are quite right that this is legal XML or SGML -- that's one valid
use of NOTATION attributes. Here's this paragraph UUENCODED:
begin 644 para
It reflects well on XML that this is possible.
> I thought this would be a given. Sure using XLL or simple url
> hrefs are great, but many times the requirement is for a single
> file with all resources literally included.
I don't see that there is any long-term advantage to that -- in the
short-term, it will work around some temporary short-comings in specs
and implementations, but it's the equivalent of writing an entire C
program in a single file to save time on linking (or even all in
main(), to avoid the overhead of subroutines). Modularity and
encapsulation have already proven their worth in the programming
world, and they will prove their worth in XML as well.
In other words, inlining uuencoded objects is a kludge: by all means,
do it in your implementations if you plan to ship soon and need to
work with the current generation of software and Internet protocols,
but recognise that you are creating maintenance headaches for yourself
later on (as I have for myself by forcing AElfred into a single Java
class file), and **PLEASE** do not codify kludges in standards.
All the best,
David Megginson email@example.com
Microstar Software Ltd. firstname.lastname@example.org
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)