This is a schema to encapsulate email document files. An email instance represents an Internet-like mail message as recorded by a receiving email system. The specification consists of a description of the XML schema and an example of an instance of the schema.
http://preservation.naa.gov.au/email/1.0
Prefix Namespace
xsd
http://www.w3.org/2001/XMLSchema
email
http://preservation.naa.gov.au/email/1.0
The following sections describe the email XML schema.
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:email="http://preservation.naa.gov.au/email/1.0"
targetNamespace="http://preservation.naa.gov.au/email/1.0"
version="1.0">
<xsd:annotation>
<xsd:documentation xml:lang="en">
email. A schema to represent networked messages
that conform to the principles of Internet email as
codified by RFC 2822 and related Internet Engineering Task
Force (IETF) Request For Comments documents.
Developed by the National Archives of Australia.
Copyright 2010 Commonwealth of Australia.
</xsd:documentation>
</xsd:annotation>
<xsd:element name="email">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="headers">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="header" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:attribute name="name" type="xsd:string" use="optional" />
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="parts">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="part" minOccurs="1" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
<xsd:attribute name="id" type="xsd:ID" use="optional" />
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
The following is an instance of the email schema.
<email:email xmlns:email="http://preservation.naa.gov.au/email/1.0">
<email:headers>
<email:header email:name="From">jack.rizzo@example.gov.au</email:header>
<email:header email:name="Subject">RE: Xena</email:header>
<email:header email:name="To">frank.tors@example.gov.au</email:header>
<email:header email:name="CC">rosine.nikos@example.gov.au</email:header>
<email:header email:name="Date">Thu, 06 Nov 2003 07:19:16 </email:header>
<email:header email:name="MIME-Version">1.0</email:header>
<email:header email:name="Content-type">multipart/mixed; boundary="--boundary-LibPST-iamunique-0_-_-"</email:header>
</email:headers>
<email:parts>
<email:part>
<xena>
<meta_data>
<meta_data_wrapper_name>Default Package Wrapper</meta_data_wrapper_name>
<normaliser_name>au.gov.naa.digipres.xena.plugin.plaintext.PlainTextToXenaPlainTextNormaliser</normaliser_name>
<input_source_uri>file:/D02_11753.MBX/D02_11753.MBX</input_source_uri>
</meta_data><content>
<plaintext:plaintext xmlns:plaintext="http://preservation.naa.gov.au/plaintext/1.0">
<plaintext:line xml:space="preserve"/>
<plaintext:line xml:space="preserve">Xena standards for Xml Electronic </plaintext:line>
<plaintext:line xml:space="preserve">Normalising of Archives. Xena transforms</plaintext:line>
<plaintext:line xml:space="preserve">digital records into open, fully documented</plaintext:line>
<plaintext:line xml:space="preserve">formats for long-term digital preservation.</plaintext:line>
<plaintext:line xml:space="preserve">This is useful for many situations, but especially</plaintext:line>
<plaintext:line xml:space="preserve">for government archival institutions.</plaintext:line>
</plainext:plaintext>
</content>
</xena>
</email:part>
</email:parts>
</email:email>