SGML: MIMESGML Drafts
SGML: MIMESGML Drafts
Mirrored (September 26, 1995) from http://www.ietf.cnri.reston.va.us/ids.by.wg/mimesgml.html.
"The MIME Multipart/Related Content-type", E. Levinson, 07/07/1995. (19674 bytes)
- 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.
"Message/External-Body Content-ID Access Type", E. Levinson, J. Clark, 05/31/1995. (6903 bytes)
- 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 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.
"Encapsulating SGML Documents Using the Multipart/Related Content-Type", E. Levinson, 07/25/1995. (52653 bytes)
- This document describes the encapsulation of a Standard Generalized
Markup Language (SGML) document within a MIME message. The document
may be represented in the message by some or all of its components.
The MIME message may also include auxiliary information to be used by
the recipient in processing the encapsulated SGML. The document
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 set of SGML
components as a single object and access-type=content-type allows a
several MIME entities to contain identical bodies without replicating
the body in each MIME entity.
"Using Catalogs and MIME to Exchange SGML Documents", D. Stinchfield, 09/19/1995. (51391 bytes)
- This draft proposes a standard for exchanging SGML documents over the
World Wide Web using catalogs and MIME. This draft extends SGML Open
definition of catalogs  by adding to it new keywords and storage
object identifier (SOI) types. The new keywords identify SGML document
objects (such as document type declarations and document entities) and
non-SGML document objects (such as stylesheets). The new SOI types
include URIs and MIME Content-IDs. This document also defines two new
MIME content types called Application/SGML-Catalog and
Application/SGML. Application/SGML-Catalog identifies a MIME body part
as a catalog, while Application/SGML identifies a MIME body part as an
SGML object. (This Internet-Draft is also available in
PostScript format [139848 bytes].)
IETF Secretariat - Corporation for National Research Initiatives
Please send questions, comments, and/or suggestions to
Return to IETF home page.