W3C home > Mailing lists > Public > xml-dist-app@w3.org > September 2000

RE: Removal (Time for XMail?)

From: S. Mike Dierken <mike@knownow.com>
Date: Fri, 29 Sep 2000 10:28:52 -0700
To: "Simon St.Laurent" <simonstl@simonstl.com>, <xml-dist-app@w3.org>
Message-ID: <ENEILMMLEJBPJPFHPJGGEEIGCEAA.mike@knownow.com>
Did you take a look at the MIME multipart/related specification?

A single low-level stream can have multiple message bodies. A single body
can reference other related bodies through a URL syntax:
mid:other-message-id and cid:other-content-id. Each message body can have
its own set of headers for content-type, etc.

You could send a 'hub' document with data and references to the other parts
of the message - or other parts on the Web if you want as well.


Mike

> -----Original Message-----
> From: xml-dist-app-request@w3.org [mailto:xml-dist-app-request@w3.org]On
> Behalf Of Simon St.Laurent
> Sent: Friday, September 29, 2000 10:00 AM
> To: xml-dist-app@w3.org
> Subject: RE: Removal (Time for XMail?)
>
>
> At 08:50 AM 9/29/00 -0700, David Orchard wrote:
> >The problem of using 1 syntax to contain instances of that same syntax is
> >occurring in a few places XML.  The issues surround the data
> model for the
> >"xmlns" quasi-attribute are one example.  When is it an
> attribute and when
> >not?  The same occurs for special elements, say an <xml:include
> /> element.
> >I'm reminded of Godel and issues around circular reference.
>
> I have to admit that I've been wondering lately if the SMTP approach, with
> each message as a sequential stream of information, still makes sense.
> Maybe sending a couple of streams - an initial (likely XML) description of
> what's coming, followed by retrievals to get that information by the
> recipient using keys provided in the description.
>
> Effectively, it'd be headers first, then content as a separate message or
> set of messages.  The recipient would have a lot more control over what
> they got, we wouldn't be trying to stuff everything into an XML document,
> and maybe we could finally get past some of SMTP's legacy headaches.
>
> (Yes, I'm aware that this would create many new headaches.
> Still, it seems
> worth putting out for consideration.)
>
> Simon St.Laurent
> XML Elements of Style / XML: A Primer, 2nd Ed.
> XHTML: Migrating Toward XML
> http://www.simonstl.com - XML essays and books
Received on Friday, 29 September 2000 13:28:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:57 GMT