Lists Home |
Date Index |
- From: Clark Evans <firstname.lastname@example.org>
- To: XML Dev <email@example.com>
- Date: Tue, 23 Feb 1999 19:16:24 +0000
Sorry to revive a dead thread, but I'm making progress
on the subject, so I'd like your feedback.
A while back I wrote:
> The rewrite program would:
> 2) Leave valid XML/HTML alone if possible.
To which David Megginson wrote:
> Wrong -- or, to put it differently, it should leave content with
> text/html and text/xml alone, but it should not try to recognise
> markup in text/plain.
Then, Parand Tony Darugar <firstname.lastname@example.org> and
Jonathan Borden <email@example.com> posted their
current implementations of such a monster.
The debate then swung as to how to treat the "body"
of the e-mail. Most people agreed that it was some
sort of CDATA thing, where "]]>" in the text body
would become "]]>"
Isn't there a way to do smart stuff like #2 ?
For example, look at Didier's post below.
It'd be slick to have the XMLMail program
recognize his markup.
For my example, I'd like to "embeed" bookkeeping
information in my e-mail. If the e-mail leaves
the 'organization', the bookkeeping is stripped.
A wizened browser using style sheets may put
the bookkeeping info off to the side, where
an old e-mailer may show it in-line.
This way I can do stuff like:
<bookkeeping date="23feb1999" contract="research-xml" hours=".25"
work="Wrote e-mail to xml-list about extracting tagged bookkeeping
information from an otherwise text-only message"
Then I can run all of my e-mail through my
journal, which then hits my ledger, and accounts
for my time appropriately. I'm actually very
serious about this...
XML, it's not just for computers anymore.
-------- Original Message --------
Subject: RE: Streaming XSL
Date: Tue, 23 Feb 1999 12:08:08 -0500
From: "Didier PH Martin" <firstname.lastname@example.org>
The use of a "stream" media to specify this seems like a kludge (though I
appreciate how you came to use it in the current framework). It really
should be in the <xsl:stylesheet> element.
I agree 100%. Actually, if we look closely to XSL specs or to any other xml
processing stuff. We have no common way to associate an interpreter to a XML
document. A XML document without an associated interpreter is nothing more
than just sleeping data in a serialized format. What we should have:
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/ and on CD-ROM/ISBN 981-02-3594-1
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)