1.1 Glossary

This document uses the following terms:

Multipurpose Internet Mail Extensions (MIME): A set of extensions that redefines and expands support for various types of content in email messages, as described in [RFC2045], [RFC2046], and [RFC2047].

SOAP message: An XML document consisting of a mandatory SOAP envelope, an optional SOAP header, and a mandatory SOAP body. See [SOAP1.2-1/2007] section 5 for more information.

streaming: The act of processing a part of an XML Infoset without requiring that the entire XML Infoset be available.

XML Information Set (Infoset): An abstract data set that provides a consistent set of definitions for use in specifications that refer to the information in a well-formed XML document, as described in [XMLINFOSET].

XML-binary Optimized Packaging (XOP): The packaging convention that efficiently serializes XML Infosets that contain certain types of content, as described in [XML-XOP].

XOP Information Set (XOP Infoset): An XML Infoset in which optimized content has been removed and replaced by <xop:Include> SOAP element information items, as described in [XML-XOP].

XOP package: A package that offers an alternate serialization of an XML Infoset and that contains the XOP document and any optimized content from the original XML Infoset, as described in [XML-XOP].

MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.