SGML: MIME in SGML
SGML: MIME in SGML
From firstname.lastname@example.org Fri Jun 2 13:22:14 1995
Received: from ebt-inc.ebt.com by utafll.uta.edu (4.1/25-eef)
id AA02883; Fri, 2 Jun 95 13:22:01 CDT
Received: from Princeton.EDU (root@Princeton.EDU [184.108.40.206]) by ebt-inc.ebt.com (8.6.9/8.6.9) with SMTP id KAA07483 for <email@example.com>; Fri, 2 Jun 1995 10:58:45 -0400
Received: from acupain.UUCP by Princeton.EDU (5.65b/2.118/princeton)
id AA21495; Fri, 2 Jun 95 10:50:46 -0400
Received: by Accurate.COM (4.1/SMI-4.0)
id AA09887; Fri, 2 Jun 95 10:46:36 EDT
Subject: WG Last Call: SGML Encap. et al.
Organization: Accurate Information Systems, Inc.
X-Org-Addr: 2 Industrial Way
X-Org-Addr: Eatontown, NJ 08840
X-Org-Misc: 1.908.389.5550 (phone) 1.908.389.5556 (fax)
X-Mailer: MH 6.8
Content-Type: Multipart/Mixed; boundary=tiger-lily
Date: Fri, 02 Jun 1995 10:46:32 -0400
From: Ed Levinson <elevinso@Accurate.COM>
Content-Description: Cover Letter
The new draft for SGML in MIME has been completed. Actually
draft-ietf-mimesgml-encap-00.txt (20 pages)
draft-ietf-mimesgml-access-cid-00.txt ( 4 pages)
draft-ietf-mimesgml-multipart-rel-01.txt ( 7 pages)
This announcement is for a last call within the MIMESGML working
group. After two weeks (June 19), if a rough consensus exists I
will forward the drafts to the area directors for Proposed
These drafts represent the specification from which implementors will
work. You can get copies from your favorite archive, see the attached
abstracts and instructions (I copied them from the announcements sent
to the list). The last attachment will retrieve the three documents
via email (if your mail reader is MIME-capable).
Here's how the drafts fit together:
encap is the main document and has all the details
about handling SGML. It incorporates many of
the suggestions people have made over the
course of the discussions.
multipart-rel describes the Multipart/Related proposal, the
MIME entity that encloses an SGML document. It
contains nothing about SGML itself but defines
the behaviour for this media type.
access-cid provides the a cross-referece mechanism that
permits an SGML entity appear more than once
without replicating the data.
So read, respond, and provide your comments.
This draft describes the encapsulation of a Standard Generalized Markup
Language (SGML) document withing a MIME message. It proposes new content
sub-types of Text/SGML, Application/SGML, and Application/SGML-notation,
and a new header, Content-SGML-Entity.
This specification uses the proposed Multipart/Related Content-Type
[RFC-REL] and access-type=content-id [RFC-ACTI] specifications.
Multipart/Related provides the mechanism for treating the entire document
as a single object and access-type=content-type allows a single MIME entity
to appear several times without replicating the body of that MIME entity.
When using MIME [MIME] to encapsulate a structured object that consist of
many elements, for example an SGML [SGML] document, a single element may
occur several times. An encapsulation normally maps each of the structured
objects elements to a MIME entity. It is useful to include elements that
occur multiple time exactly once. To accomplish that and to preserve the
object structure it is desirable to unambiguously refer to another body
part of the same message.
The Multipart/Related content-type provides a common mechanism for
representing objects that are aggregates of related MIME body parts. This
document defines the Multipart/Related content-type and provides examples
of its use.
The exsisting MIME Content-Type Message/External-Body access-types allow
a MIME entity (body-part) to refer to an object that is not in the message
by specifying how to access that object. The Content-ID access method
described in this document provides the capability to refer to an object
within the message.
Content-Description: Instructions for getting the drafts
Internet-Drafts are available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
The URL for the Internet-Drafts are:
Internet-Drafts directories are located at:
Address: ftp.is.co.za (220.127.116.11)
Address: nic.nordu.net (18.104.22.168)
Address: ftp.nis.garr.it (22.214.171.124)
o Pacific Rim
Address: munnari.oz.au (126.96.36.199)
o US East Coast
Address: ds.internic.net (188.8.131.52)
o US West Coast
Address: ftp.isi.edu (184.108.40.206)
Internet-Drafts are also available by mail.
Send a message to: firstname.lastname@example.org. In the body type:
NOTE: The mail server at ds.internic.net can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e., documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
For questions, please mail to Internet-Drafts@cnri.reston.va.us.
Content-Description: mail-server request