Pretty Diff - The difference tool

Accessibility note. <span> tags in the output represent character differences per lines compared.

version 1.0 finalversion 1.b
1Expires October 11, 20091Demo
22
33
4Network Working Group A. Cheney4Demo A. Cheney
5Internet Draft Sabre Inc.5Demo Sabre Inc.
6Category: Standards Draft April 20096Demo February 2009
7Obsoletes: 1939, 3501, 53227Obsoletes: 1939, 3501, 5322
88
9 Mail Markup Language - Version 1.09 Mail Markup Language - Version 1.0
1010
11Status of this Memo11Status of this Memo
1212
13 This document specifies an Internet standards track protocol for the13 This document specifies an Internet standards track protocol for the
14 Internet community, and requests discussion and suggestions for14 Internet community, and requests discussion and suggestions for
15 improvements. Please refer to the current edition of the "Internet15 improvements. Please refer to the current edition of the "Internet
16 Official Protocol Standards" (STD 1) for the standardization state16 Official Protocol Standards" (STD 1) for the standardization state
17 and status of this protocol.17 and status of this protocol.
1818
19 Mail Markup Language (MML) is the intellectual property (IP) of Sabre19 Mail Markup Language (MML) is the intellectual property (IP) of Sabre
20 Inc. Concepts introduced by this technology and specified20 Inc. Concepts introduced by this technology and specified
21 constraints as a standard are protected by provisional patent with21 constraints as a standard are protected by provisional patent with
22 intent to achieve full patent protection. Removal or omission of22 intent to achieve full patent protection. Removal or omission of
23 entire features of specifically the language or its containing23 entire features of specifically the language or its containing
24 standard may represent a conflict of IP unless approval for such24 standard may represent a conflict of IP unless approval for such
25 removal is granted from an authorized agent of Sabre Inc. Changes25 removal is granted from an authorized agent of Sabre Inc. Changes
26 and additions to the standard requirements, language, or concepts26 and additions to the standard requirements, language, or concepts
27 proposed by this document are allowed without permission. Derivative27 proposed by this document are allowed without permission. Derivative
28 works and distribution are authorized unlimited without permission.28 works and distribution are authorized unlimited without permission.
2929
30 "By submitting this Internet-Draft, each author represents that any30 "By submitting this Internet-Draft, each author represents that any
31 applicable patent or other IPR claims of which he or she is aware31 applicable patent or other IPR claims of which he or she is aware
32 have been or will be disclosed, and any of which he or she becomes32 have been or will be disclosed, and any of which he or she becomes
33 aware will be disclosed, in accordance with Section 6 of BCP 79.33 aware will be disclosed, in accordance with Section 6 of BCP 79.
3434
35 "Internet-Drafts are working documents of the Internet Engineering35 "Internet-Drafts are working documents of the Internet Engineering
36 Task Force (IETF), its areas, and its working groups. Note that36 Task Force (IETF), its areas, and its working groups. Note that
37 other groups may also distribute working documents as Internet-37 other groups may also distribute working documents as Internet-
38 Drafts.38 Drafts.
3939
40 Internet-Drafts are draft documents valid for a maximum of six months40 Internet-Drafts are draft documents valid for a maximum of six months
41 and may be updated, replaced, or obsoleted by other documents at any41 and may be updated, replaced, or obsoleted by other documents at any
42 time. It is inappropriate to use Internet-Drafts as reference42 time. It is inappropriate to use Internet-Drafts as reference
43 material or to cite them other than as "work in progress."43 material or to cite them other than as "work in progress."
4444
45 The list of current Internet-Drafts can be accessed at45 The list of current Internet-Drafts can be accessed at
46 http://www.ietf.org/1id-abstracts.html46 http://www.ietf.org/1id-abstracts.html
4747
48 The list of Internet-Draft Shadow Directories can be accessed at48 The list of Internet-Draft Shadow Directories can be accessed at
49 http://www.ietf.org/shadow.html"49 http://www.ietf.org/shadow.html"
5050
5151
5252
5353
5454
5555
56Cheney Standards Track [Page 1]56Cheney Standards Track [Page 1]
5757
58Internet-Draft Mail Markup Language - Version 1.0 April 200958Internet-Draft Mail Markup Language - Version 1.0 February 2009
5959
60Abstract60Abstract
61 Mail Markup Language (MML) is a simple tag based markup language used61 Mail Markup Language (MML) is a simple tag based markup language used
62 to describe and structure data in a document intended to represent62 to describe and structure data in a document intended to represent
63 communication across the medium of email. MML is written in W3C XML63 communication across the medium of email. MML is written in W3C XML
64 Schema language. All MML documents are XML documents that conform to64 Schema language. All MML documents are XML documents that conform to
65 the MML schema. This specification intends to replace RFC 5322.65 the MML schema. This specification intends to replace RFC 5322.
6666
67IANA Considerations67IANA Considerations
68 This specification requests the registration of a namespace and two68 This specification requests the registration of a namespace and two
69 MIME types. The namespace name requested is MML. A static URI69 MIME types. The namespace name requested is MML. A static URI
70 pointed to the location of the mail.xsd as hosted by a standards body70 pointed to the location of the mail.xsd as hosted by a standards body
71 is also requested for mapping to the requested namespace name. That71 is also requested for mapping to the requested namespace name. That
72 URI would become the value of the MML:schemaLocation attribute. The72 URI would become the value of the MML:schemaLocation attribute. The
73 MIME types application/mail and text/xsl are also requested. The73 MIME types application/mail and text/xsl are also requested. The
74 application/mail MIME type will be used to identify a MML document74 application/mail MIME type will be used to identify a MML document
75 for processing as mail over any standard mail protocol. The text/xsl75 for processing as mail over any standard mail protocol. The text/xsl
76 MIME type is requested to identify documents written in the76 MIME type is requested to identify documents written in the
77 Extensible Markup Language (XSL) for stylesheet processing.77 Extensible Markup Language (XSL) for stylesheet processing.
7878
7979
8080
8181
8282
8383
8484
8585
8686
8787
8888
8989
9090
9191
9292
9393
9494
9595
9696
9797
9898
9999
100100
101101
102102
103103
104104
105105
106106
107107
108108
109109
110110
111111
112Cheney Standards Track [Page 2]112Cheney Standards Track [Page 2]
113113
114Internet-Draft Mail Markup Language - Version 1.0 April 2009114Internet-Draft Mail Markup Language - Version 1.0 February 2009
115115
116Table of Contents116Table of Contents
117117
1181. Introduction .................................................... 51181. Introduction .................................................... 5
119 1.1. Scope ...................................................... 5119 1.1. Scope ...................................................... 5
120 1.2. Requirements ............................................... 6120 1.2. Requirements ............................................... 5
121 1.3. Terminology ................................................ 6121 1.3. Terminology ................................................ 6
1222. Philosophy of Design ............................................ 71222. Philosophy of Design ............................................ 7
123 2.1. Structure .................................................. 7123 2.1. Structure .................................................. 7
124 2.2. Syntax Simplicity and Understandability .................... 8124 2.2. Syntax Simplicity and Understandability .................... 7
125 2.3. Semantics .................................................. 8125 2.3. Semantics .................................................. 8
126 2.4. Accessibility .............................................. 9126 2.4. Accessibility .............................................. 8
127 2.5. Presentation ............................................... 9127 2.5. Presentation ............................................... 9
128 2.6. Security ................................................... 9128 2.6. Security ................................................... 9
1293. External Technologies ........................................... 101293. External Technologies ........................................... 9
130 3.1. Extensible Markup Language (XML) and W3C XML Schema ........ 10130 3.1. Extensible Markup Language (XML) and W3C XML Schema ........ 10
131 3.2. XForms ..................................................... 10131 3.2. XForms ..................................................... 10
132 3.3. Accessible Rich Internet Applications (ARIA) ............... 10132 3.3. Accessible Rich Internet Applications (ARIA) ............... 10
133 3.4. Resource Document Framework (RDF) .......................... 10133 3.4. Resource Document Framework (RDF) .......................... 10
134 3.5. Stylesheet Technologies .................................... 11134 3.5. Stylesheet Technologies .................................... 10
135 3.6. Behaviors and Scripting .................................... 11135 3.6. Behaviors and Scripting .................................... 11
136 3.7. Public Key Infrastructure (PKI) ............................ 11136 3.7. Public Key Infrastructure (PKI) ............................ 11
137 3.8. Uniform Resource Identifier (URI) .......................... 11137 3.8. Uniform Resource Identifier (URI) .......................... 11
138 3.9. Multipurpose Internet Mail Extensions (MIME) ............... 11138 3.9. Multipurpose Internet Mail Extensions (MIME) ............... 11
1394. Processor Roles ................................................. 111394. Processor Roles ................................................. 11
140 4.1. Processor Requirements and Constraints ..................... 12140 4.1. Processor Requirements and Constraints ..................... 11
141 4.1.1. Validation ............................................ 12141 4.1.1. Validation ............................................ 12
142 4.1.2. RFC 2822/5322 Conformance ............................. 12142 4.1.2. RFC 2822/5322 Conformance ............................. 12
143 4.1.3. Session Separation and Presentation ................... 12143 4.1.3. Session Separation and Presentation ................... 12
144 4.1.4. Session Preservation .................................. 13144 4.1.4. Session Preservation .................................. 12
145 4.1.5. Character Set ......................................... 13145 4.1.5. Character Set ......................................... 12
146 4.1.6. Session Timestamp ..................................... 13146 4.1.6. Session Timestamp ..................................... 13
147 4.1.7. URI Resolution ........................................ 13147 4.1.7. URI Resolution ........................................ 13
148 4.1.8. MIME Execution Restriction ............................ 13148 4.1.8. MIME Execution Restriction ............................ 13
149 4.1.9. Caching ............................................... 13149 4.1.9. Caching ............................................... 13
150 4.1.10. Local Processing ..................................... 13150 4.1.10. Local Processing ..................................... 13
151 4.1.11. MIME Catalogue ....................................... 14151 4.1.11. MIME Catalogue ....................................... 13
152 4.1.12. From and Reply-to Tags ............................... 14152 4.1.12. From and Reply-to Tags ............................... 14
153 4.1.13. Attachments .......................................... 14153 4.1.13. Attachments .......................................... 14
154 4.1.14. Processing of <plain-text> ........................... 15154 4.1.14. Processing of <plain-text> ........................... 14
155 4.1.15. Processing of style Attribute ........................ 15155 4.1.15. Processing of style Attribute ........................ 14
156 4.1.16. Internationalization Attribute Processing ............ 15156 4.1.16. Internationalization Attribute Processing ............ 15
157 4.1.17. xmlns Attribute ...................................... 15157 4.1.17. refer Attribute Processing ........................... 15
158 4.1.18. refer Attribute Processing ........................... 16158 4.2. Processor Allowances ....................................... 15
159 4.2. Processor Allowances ....................................... 16159 4.2.1. Processor Default Presentation ........................ 15
160 4.2.1. Processor Default Presentation ........................ 16160 4.2.2. Processor Default Behaviors ........................... 15
161 4.2.2. Processor Default Behaviors ........................... 161615. Default mime.xsd ................................................ 16
162 4.2.3. Processing Elaborations Over Native MML Definitions ... 171626. MML Schema ...................................................... 36
1635. MML Schema Header Documentation ................................. 171637. MML Schema Header Documentation ................................. 49
164 5.1. MIME Type Usage and mime.xsd ............................... 17164 7.1. MIME Type Usage and mime.xsd ............................... 50
165 5.2. MML Header Documentation ................................... 18165 7.2. MML Header Documentation ................................... 50
166 5.2.1. Root Element .......................................... 18166 7.2.1. Root Element .......................................... 50
167167
168Cheney Standards Track [Page 3]168Cheney Standards Track [Page 3]
169169
170Internet-Draft Mail Markup Language - Version 1.0 April 2009170Internet-Draft Mail Markup Language - Version 1.0 February 2009
171171
172 5.2.2. <session> Tag ......................................... 18172 7.2.2. <session> Tag ......................................... 50
173 5.2.3. <address> Tag ......................................... 19173 7.2.3. <address> Tag ......................................... 51
174 5.2.4. <to>, <copy>, <blind-copy>, and <from> Tags ........... 19174 7.2.4. <to>, <copy>, <blind-copy>, and <from> Tags ........... 51
175 5.2.5. <reply-to> Tag ........................................ 19175 7.2.5. <reply-to> Tag ........................................ 51
176 5.2.6. <attachments> Tag ..................................... 19176 7.2.6. <attachments> Tag ..................................... 51
177 5.2.7. <collection> Tag ...................................... 19177 7.2.7. <collection> Tag ...................................... 52
178 5.2.8. <collection-name> Tag ................................. 19178 7.2.8. <collection-name> Tag ................................. 52
179 5.2.9. <collection-file> Tag ................................. 20179 7.2.9. <collection-file> Tag ................................. 52
180 5.2.10. <collection-type> Tag ................................ 20180 7.2.10. <collection-type> Tag ................................ 52
181 5.2.11. <collection-description> Tag ......................... 20181 7.2.11. <collection-description> Tag ......................... 52
182 5.2.12. <file> Tag ........................................... 20182 7.2.12. <file> Tag ........................................... 52
183 5.2.13. <file-name> Tag ...................................... 20183 7.2.13. <file-name> Tag ...................................... 52
184 5.2.14. <file-type> Tag ...................................... 20184 7.2.14. <file-type> Tag ...................................... 53
185 5.2.15. <file-description> Tag ............................... 20185 7.2.15. <file-description> Tag ............................... 53
186 5.2.16. <subject> Tag ........................................ 20186 7.2.16. <subject> Tag ........................................ 53
187 5.2.17. <presentation> Tag ................................... 21187 7.2.17. <presentation> Tag ................................... 53
188 5.2.18. <stylesheet> Tag ..................................... 21188 7.2.18. <stylesheet> Tag ..................................... 53
189 5.2.19. <source> Tag ......................................... 21189 7.2.19. <source> Tag ......................................... 53
190 5.2.20. <source-uri> Tag ..................................... 21190 7.2.20. <source-uri> Tag ..................................... 53
191 5.2.21. <source-type> Tag .................................... 21191 7.2.21. <source-type> Tag .................................... 54
192 5.2.22. <plain-text> Tag ..................................... 21192 7.2.22. <plain-text> Tag ..................................... 54
193 5.2.23. <markup> Tag ......................................... 22193 7.2.23. <markup> Tag ......................................... 54
194 5.3. <markup> Organization of Types and Groups .................. 22194 7.3. <markup> Organization of Types and Groups .................. 54
195 5.3.1. <markup> Element Organization ......................... 22195 7.3.1. <markup> Element Organization ......................... 54
196 5.3.2. <markup> Attribute Organization ....................... 23196 7.3.2. <markup> Attribute Organization ....................... 55
197 5.4. <markup> Attributes ........................................ 23197 7.4. <markup> Attributes ........................................ 56
198 5.4.1. id Attribute .......................................... 23198 7.4.1. id Attribute .......................................... 56
199 5.4.2. title Attribute ....................................... 24199 7.4.2. title Attribute ....................................... 56
200 5.4.3. class Attribute ....................................... 24200 7.4.3. class Attribute ....................................... 56
201 5.4.4. role Attribute ........................................ 24201 7.4.4. role Attribute ........................................ 56
202 5.4.5. uri Attribute ......................................... 24202 7.4.5. uri Attribute ......................................... 56
203 5.4.6. direction Attribute ................................... 24203 7.4.6. direction Attribute ................................... 57
204 5.4.7. orientation Attribute ................................. 25204 7.4.7. orientation Attribute ................................. 57
205 5.4.8. wrap Attribute ........................................ 25205 7.4.8. wrap Attribute ........................................ 57
206 5.4.9. section-language Attribute ............................ 25206 7.4.9. section-language Attribute ............................ 57
207 5.4.10. span-column Attribute ................................ 25207 7.4.10. span-column Attribute ................................ 57
208 5.4.11. span-row Attribute ................................... 25208 7.4.11. span-row Attribute ................................... 57
209 5.4.12. refer Attribute ...................................... 25209 7.4.12. refer Attribute ...................................... 58
210 5.4.13. scope Attribute ...................................... 25210 7.4.13. scope Attribute ...................................... 58
211 5.4.14. long-form Attribute .................................. 26211 7.4.14. long-form Attribute .................................. 58
212 5.5. <markup> Elements .......................................... 26212 7.5. <markup> Elements .......................................... 58
213 5.5.1. <define-list> Tag ..................................... 26213 7.5.1. <define-list> Tag ..................................... 58
214 5.5.2. <define-item> Tag ..................................... 26214 7.5.2. <define-item> Tag ..................................... 58
215 5.5.3. <define-term> Tag ..................................... 27215 7.5.3. <define-term> Tag ..................................... 59
216 5.5.4. <definition> Tag ...................................... 27216 7.5.4. <definition> Tag ...................................... 59
217 5.5.5. <navigation-list> Tag ................................. 27217 7.5.5. <navigation-list> Tag ................................. 59
218 5.5.6. <navigation-item> Tag ................................. 27218 7.5.6. <navigation-item> Tag ................................. 59
219 5.5.7. <navigation-object> Tag ............................... 27219 7.5.7. <navigation-object> Tag ............................... 59
220 5.5.8. <navigation-text> Tag ................................. 28220 7.5.8. <navigation-text> Tag ................................. 60
221 5.5.9. <order-list> Tag ...................................... 28221 7.5.9. <order-list> Tag ...................................... 60
222 5.5.10. <unorder-list> Tag ................................... 28222 7.5.10. <unorder-list> Tag ................................... 60
223223
224Cheney Standards Track [Page 4]224Cheney Standards Track [Page 4]
225225
226Internet-Draft Mail Markup Language - Version 1.0 April 2009226Internet-Draft Mail Markup Language - Version 1.0 February 2009
227227
228 5.5.11. <list-item> Tag ...................................... 29228 7.5.11. <list-item> Tag ...................................... 61
229 5.5.12. <form> Tag ........................................... 29229 7.5.12. <form> Tag ........................................... 61
230 5.5.13. <form-body> Tag ...................................... 29230 7.5.13. <form-body> Tag ...................................... 61
231 5.5.14. <table> Tag .......................................... 29231 7.5.14. <table> Tag .......................................... 61
232 5.5.15. <head-row> Tag ....................................... 29232 7.5.15. <head-row> Tag ....................................... 61
233 5.5.16. <table-row> Tag ...................................... 30233 7.5.16. <table-row> Tag ...................................... 62
234 5.5.17. <head-cell> Tag ...................................... 30234 7.5.17. <head-cell> Tag ...................................... 62
235 5.5.18. <table-cell> Tag ..................................... 30235 7.5.18. <table-cell> Tag ..................................... 62
236 5.5.19. <section> Tag ........................................ 30236 7.5.19. <section> Tag ........................................ 62
237 5.5.20. <block-code> Tag ..................................... 31237 7.5.20. <block-code> Tag ..................................... 63
238 5.5.21. <block-quote> Tag .................................... 31238 7.5.21. <block-quote> Tag .................................... 63
239 5.5.22. <citation> Tag ....................................... 31239 7.5.22. <citation> Tag ....................................... 63
240 5.5.23. <heading> Tag ........................................ 32240 7.5.23. <heading> Tag ........................................ 64
241 5.5.24. <object> Tag ......................................... 32241 7.5.24. <object> Tag ......................................... 64
242 5.5.25. <object-text> Tag .................................... 32242 7.5.25. <object-text> Tag .................................... 64
243 5.5.26. <object-uri> Tag ..................................... 32243 7.5.26. <object-uri> Tag ..................................... 64
244 5.5.27. <object-type> Tag .................................... 32244 7.5.27. <object-type> Tag .................................... 64
245 5.5.28. <paragraph> Tag ...................................... 32245 7.5.28. <paragraph> Tag ...................................... 64
246 5.5.29. <separator> Tag ...................................... 33246 7.5.29. <separator> Tag ...................................... 65
247 5.5.30. <short> Tag .......................................... 33247 7.5.30. <short> Tag .......................................... 65
248 5.5.31. <button> Tag ......................................... 33248 7.5.31. <button> Tag ......................................... 65
249 5.5.32. <cite> Tag ........................................... 33249 7.5.32. <cite> Tag ........................................... 65
250 5.5.33. <emphasis> Tag ....................................... 33250 7.5.33. <emphasis> Tag ....................................... 65
251 5.5.34. <identifier> Tag ..................................... 34251 7.5.34. <identifier> Tag ..................................... 65
252 5.5.35. <quote> Tag .......................................... 34252 7.5.35. <quote> Tag .......................................... 66
253 5.5.36. <format> Tag ......................................... 34253 7.5.36. <format> Tag ......................................... 66
254 5.5.37. <strong> Tag ......................................... 34254 7.5.37. <strong> Tag ......................................... 66
255 5.5.38. <title> Tag .......................................... 34255 7.5.38. <title> Tag .......................................... 66
2566. Protocol Compatibility .......................................... 342568. Protocol Compatibility .......................................... 66
257 6.1. Simple Mail Transfer Protocol (SMTP) ....................... 35257 8.1. Simple Mail Transfer Protocol (SMTP) ....................... 67
258 6.2. Post Office Protocol - Version 3 (POP3) .................... 35258 8.2. Post Office Protocol - Version 3 (POP3) .................... 67
259 6.3. Internet Message Access Protocol - Version 4rev1 (IMAP) .... 35259 8.3. Internet Message Access Protocol - Version 4rev1 (IMAP) .... 67
260 6.4. Requirements for Web Mail .................................. 36260 8.4. Requirements for Web Mail .................................. 67
2617. Default mime.xsd ................................................ 362619. References ...................................................... 68
2628. MML Schema ...................................................... 5626210. Acknowledgements ............................................... 71
2639. References ...................................................... 7126311. Author's Address ............................................... 72
26410. Acknowledgements ............................................... 75
26511. Author's Address ............................................... 75
266264
2671. Introduction2651. Introduction
268 MML as a standard is both a language and a standard list of266 MML as a standard is both a language and a standard list of
269 processing constraints upon that language.267 processing constraints upon that language.
270268
2711.1. Scope2691.1. Scope
272 This document seeks to fully describe the specification and syntax270 This document seeks to fully describe the specification and syntax
273 rules of the actual language, the constraints upon processing that271 rules of the actual language, the constraints upon processing that
274 language, and the inclusion of other standards or technologies.272 language, and the inclusion of other standards or technologies.
275273
276
277
278
279
280Cheney Standards Track [Page 5]
281
282Internet-Draft Mail Markup Language - Version 1.0 April 2009
283
2841.2. Requirements2741.2. Requirements
285 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",275 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
286 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this276 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
287 document are to be interpreted as described in RFC 2119 [34].277 document are to be interpreted as described in RFC 2119 [34].
288278
279Cheney Standards Track [Page 5]
280
281Internet-Draft Mail Markup Language - Version 1.0 February 2009
282
289 If an implementation, feature, or constraint does not satisfy a283 If an implementation, feature, or constraint does not satisfy a
290 requirement level of MUST, MUST NOT, or REQUIRED for its respective284 requirement level of MUST or REQUIRED for its respective statement,
291 statement, clause, phrase, or section that implementation, feature,285 clause, phrase, or section that implementation, feature, or
292 or constraint MUST be considered failed. Under such a circumstance,286 constraint MUST be considered failed. Under such a circumstance,
293 known as conditional compliance, a MML document MUST NOT be287 known as conditional compliance, a MML document must not be
294 transmitted. The ideal MML document will satisfy conditional 288 transmitted. The ideal MML document will satisfy all MUST, REQUIRED,
295 compliance, SHOULD and SHOULD NOT conditions, known as unconditional289 and SHOULD conditions, known as unconditional compliance.
296 compliance.
297290
2981.3. Terminology2911.3. Terminology
299 This document will use several terms to describe various features or292 This document will use several terms to describe various features or
300 components.293 components.
301294
302 tag295 tag
303 A tag is a code command enclosed in angle brackets such as,296 A tag is a code command enclosed in angle brackets such as,
304 "<strong>". Every tag exists as pairs of an opening tag and a297 "<strong>". Every tag exists as pairs of an opening tag and a
305 closing tag. All closing tags are identical to their opening298 closing tag. All closing tags are identical to their opening
306 counter-part except that are preceded by a forward slash299 counter-part except that are preceded by a forward slash
307 character, such as "</strong>".300 character, such as "</strong>".
308301
309 element302 element
310 The word "element" is synonymous and used interchangeably with the303 The word "element" is synonymous and used interchangeably with the
311 term "tag".304 term "tag".
312305
313 simple block306 simple block
314 A simple block is a tag that is capable of containing text and/or307 A simple block is a tag that is capable of containing text and/or
315 line-level tags.308 line-level tags.
316309
317 complex block310 complex block
318 A complex block is a tag that is capable of containing simple311 A complex block is a tag that is capable of containing simple
319 blocks or complex blocks.312 blocks or complex blocks.
320313
321 line-level tag314 line-level tag
322 Line-level tags are only capable of existing in simple blocks.315 Line-level tags are only capable of existing in simple blocks.
323 Line-level tags cannot contain other tags.316 Line-level tags cannot contain other tags.
324317
325 processor318 processor
326 The term processor is to refer to any application that processes,319 The term processor is to refer to any application that processes,
327 interprets, or seeks to process a MML document. The term320 interprets, or seeks to process a MML document. The term
328 processor may typically refer to email client applications, but is321 processor may typically refer to email client applications, but is
329 not limited to such. The term "MML processor" is directly322 not limited to such. The term "MML processor" is directly
330 synonymous to the term "mail client" used by other related323 synonymous to the term "mail client" used by other related
331 specifications.324 specifications.
332325
333
334
335
336Cheney Standards Track [Page 6]
337
338Internet-Draft Mail Markup Language - Version 1.0 April 2009
339
340 accessibility326 accessibility
341 Accessibility is the degree of ease from which any human is327 Accessibility is the degree of ease from which any human is
342 equally capable of receiving data intended for human consumption328 equally capable of receiving data intended for human consumption
343 from the desired document or request. Accessibility may refer to329 from the desired document or request. Accessibility may refer to
344 persons with a sensory disability, a motor disability, or software330 persons with a sensory disability, a motor disability, or software
345 impairment.331 impairment.
332
333
334
335
336Cheney Standards Track [Page 6]
337
338Internet-Draft Mail Markup Language - Version 1.0 February 2009
346339
347 understandability340 understandability
348 Understandability is the degree of ability by which a technology341 Understandability is the degree of ability by which a technology
349 can be learned and used by a person who has never seen or used the342 can be learned and used by a person who has never seen or used the
350 technology previously. Understandability also refers to the343 technology previously. Understandability also refers to the
351 lack of effort necessary for an experienced user to consume and344 lack of effort necessary for an experienced user to consume and
352 process the technology.345 process the technology.
353346
354 semantics347 semantics
355 Semantics refers to the degree of description provided by meta-348 Semantics refers to the degree of description provided by meta-
356 data and syntax rules either statically or through nesting and349 data and syntax rules either statically or through nesting and
357 hierarchal implementation thereof. The objective of semantics is350 hierarchal implementation thereof. The objective of semantics is
358 to provide the most expansive description of data intended for351 to provide the most expansive description of data intended for
359 human consumption without that description interfering with352 human consumption without that description interfering with
360 understandability during reading or writing.353 understandability during reading or writing.
361354
362 structure355 structure
363 Structure refers to the effectual organization of data only as a356 Structure refers to the effectual organization of data only as a
364 result of well organized meta-data containers into a rigid357 result of well organized meta-data containers into a rigid
365 hierarchy.358 hierarchy.
366359
367 session360 session
368 In the context of MML the term session only refers to an instance361 In the context of MML the term session only refers to an instance
369 of communication, which is defined by the <session></session>362 of communication, which is defined by the <session></session>
370 tags.363 tags.
371364
372 URI
373 The abbreviation of URI is short for Uniform Resource Identifier.
374 A URI is the address of a resource on a network or networks as
375 defined by RFC 3986, addressed by RFC 3305, and supplemented by
376 RFC 2368.
377
3782. Philosophy of Design3652. Philosophy of Design
379 The philosophy of design represents a shell container of decisions366 The philosophy of design represents a shell container of decisions
380 whose intent is certain beneficial objectives and to identify367 whose intent is certain beneficial objectives and to identify
381 negative consequences. The design philosophies for MML creation are368 negative consequences. The design philosophies for MML creation are
382 listed in order of most significant to less relevant.369 listed in order of most significant to less relevant.
383370
3842.1. Structure3712.1. Structure
385 Structure is the primary design consideration influencing MML. It is372 Structure is the primary design consideration influencing MML. It is
386 important that structure be the most important factor in the design373 important that structure be the most important factor in the design
387 of the language as all other design considerations are merely a374 of the language as all other design considerations are merely a
388 result of the logic and conventions imposed by a well structured375 result of the logic and conventions imposed by a well structured
389 form.376 form.
390
391
392Cheney Standards Track [Page 7]
393
394Internet-Draft Mail Markup Language - Version 1.0 April 2009
395377
396 The primary difference between MML and other markup languages is that378 The primary difference between MML and other markup languages is that
397 proper structure is mandatorily imposed upon a document author. This379 proper structure is mandatorily imposed upon a document author. This
398 rigid inflexibility produces several profoundly significant benefits380 rigid inflexibility produces several profoundly significant benefits
399 that exist inherently, which would otherwise merely be referred as381 that exist inherently, which would otherwise merely be referred as
400 best use. The cost that comes from such rigidness is an inability382 best use. The cost that comes from such rigidness is an inability
401 put content absolutely anywhere in a document in hopes to circumvent383 put content absolutely anywhere in a document in hopes to circumvent
402 a processor's short-comings.384 a processor's short-comings.
403385
4042.2. Syntax Simplicity and Understandability3862.2. Syntax Simplicity and Understandability
405 Syntax in MML is rather simple. It MUST be well-formed XML that387 Syntax in MML is rather simple. It MUST be well-formed XML that
406 conforms to the MML schema. Every tag in MML MUST exist as a pair of388 conforms to the MML schema. Every tag in MML must exist as a pair of
407 opening and closing tags. Syntax in MML is simple and always389 opening and closing tags. Syntax in MML is simple and always
408 uniform.390 uniform.
391
392Cheney Standards Track [Page 7]
393
394Internet-Draft Mail Markup Language - Version 1.0 February 2009
409395
410 Tag names are English words and not abbreviations or shortcuts. This396 Tag names are English words and not abbreviations or shortcuts. This
411 is critical to understandability. An abbreviation is a symbolic397 is critical to understandability. An abbreviation is a symbolic
412 representation of its expanded value. Although it may be faster to398 representation of its expanded value. Although it may be faster to
413 write <p> instead of <paragraph> we are saving time and physical399 write <p> instead of <paragraph> we are saving time and physical
414 effort only at the expense of increase mental effort. If we know a400 effort only at the expense of increase mental effort. If we know a
415 <p> tag represents a paragraph then it becomes of a symbol of the401 <p> tag represents a paragraph then it becomes of a symbol of the
416 word paragraph, which is a step of mental deduction.402 word paragraph, which is a step of mental deduction.
417403
418 As humans we are rather so consumed by symbolic use that it seems a404 As humans we are rather so consumed by symbolic use that it seems a
419 trivial effort to back out single step of symbolic deduction. The405 trivial effort to back out single step of symbolic deduction. The
420 savings become significantly more noticeable given the quantity of406 savings become significantly more noticeable given the quantity of
421 which meta-data often occurs in large mark up documents. The end407 which meta-data often occurs in large mark up documents. The end
422 result is that it is lesser mentally exhausting to read a document408 result is that it is lesser mentally exhausting to read a document
423 with descriptive and simple meta-data using complete words.409 with descriptive and simple meta-data using complete words.
424410
4252.3. Semantics4112.3. Semantics
426 Semantics are necessary for binding data, which is useful only to412 Semantics are necessary for binding data, which is useful only to
427 humans, and processing syntax, which is only useful to language413 humans, and processing syntax, which is only useful to language
428 processors. The objectives of semantic processing is for semantic414 processors. The objectives of semantic processing is for semantic
429 processors to parse human supplied data and make decisions upon data415 processors to parse human supplied data and make decisions upon data
430 that result in output relative to human decisions.416 that result in output relative to human decisions.
431 417
432 MML was designed with consideration for applying semantics in the418 MML was designed with consideration for applying semantics in the
433 least specific manner. Tag names were created for understandability419 least specific manner. Tag names were created for understandability
434 and not semantics. Any benefit received to semantics is purely420 and not semantics. Any benefit received to semantics is purely
435 consequential. There are two remedies to this intended lack of421 consequential. There are two remedies to this intended lack of
436 elaboration. Every tag in the <markup> section of MML is granted use422 elaboration. Every tag in the <markup> section of MML is granted use
437 of the role attribute. For the role attribute please see section423 of the role attribute. For the role attribute please see section
438 5.4.4. role Attribute. Hierarchal semantics are the primary424 7.4.4. role Attribute. Hierarchal semantics are the primary
439 unintended beneficiary of a rigid structure imposed upon the data.425 unintended beneficiary of a rigid structure imposed upon the data.
440 A combined use of the role attribute or the tag names and the426 A combined use of the role attribute or the tag names and the
441 hierarchal structure in which they exist is the second remedy for the427 hierarchal structure in which they exist is the second remedy for the
442 lack of semantic elaboration.428 lack of semantic elaboration.
443
444
445
446
447
448Cheney Standards Track [Page 8]
449
450Internet-Draft Mail Markup Language - Version 1.0 April 2009
451429
452 Even though conventions in MML were not created to directly benefit430 Even though conventions in MML were not created to directly benefit
453 semantics the conventions of semantic languages, such as Resource431 semantics the conventions of semantic languages, such as Resource
454 Document Framework, were the primary influencing factor in creating432 Document Framework, were the primary influencing factor in creating
455 the concepts and rules for imposing structure and tag hierarchy.433 the concepts and rules for imposing structure and tag hierarchy.
456434
4572.4. Accessibility4352.4. Accessibility
458 It is an important factor that all persons are equally capable of436 It is an important factor that all persons are equally capable of
459 accessing, using, and understanding documents defined as MML.437 accessing, using, and understanding documents defined as MML.
460 Accessibility is a lesser important design factor as many concerns of438 Accessibility is a lesser important design factor as many concerns of
461 accessibility are addressed by proper use of semantics and439 accessibility are addressed by proper use of semantics and
462 understandability. Usability is primarily a result of presentation440 understandability. Usability is primarily a result of presentation
463 of the data, which exceeds the scope of this document.441 of the data, which exceeds the scope of this document.
464442
465 There are constraints upon processing specified by this document that443 There are constraints upon processing specified by this document that
466 may serve to benefit accessibility. See section 4.1. Processor444 may serve to benefit accessibility. See section 4.1. Processor
467 Requirements and Constraints.445 Requirements and Constraints.
468446
447
448Cheney Standards Track [Page 8]
449
450Internet-Draft Mail Markup Language - Version 1.0 February 2009
451
4692.5. Presentation4522.5. Presentation
470 Presentation is perhaps the least concern of all design factors453 Presentation is perhaps the least concern of all design factors
471 influencing MML. All presentation will exist in either an external454 influencing MML. All presentation will exist in either an external
472 stylesheet(s) or the default presentational conventions supplied by455 stylesheet(s) or the default presentational conventions supplied by
473 the MML processor.456 the MML processor.
474457
475 This version of MML only recognizes Cascading Style Sheets and458 This version of MML only recognizes Cascading Style Sheets and
476 Extensible Stylesheet Language as presentation languages. The459 Extensible Stylesheet Language as presentation languages. The
477 degree of processing compliance afforded to those languages and460 degree of processing compliance afforded to those languages and
478 which versions are process-able are processor specific concerns,461 which versions are process-able are processor specific concerns,
479 which exceed the scope of this document. Please see section462 which exceed the scope of this document. Please see section
480 3.4. Stylesheet Technologies for more information.463 3.4. Stylesheet Technologies for more information.
481 464
482 MML processors SHOULD make no assumption that there is an implied465 MML processors should make no assumption that there is an implied
483 default presentation that any tag, element, or concept must adhere466 default presentation that any tag, element, or concept must adhere
484 to. Please see section 467 to. Please see section
485468
4862.6. Security4692.6. Security
487 While security is always important it is of trivial concern to the470 While security is always important it is of trivial concern to the
488 describing of data, which is why security is an consideration for the471 describing of data, which is why security is an consideration for the
489 design of MML, but is lowest priority. Much of the effort in472 design of MML, but is lowest priority. Much of the effort in
490 assuring MML data remains confidential and maintains integrity rests473 assuring MML data remains confidential and maintains integrity rests
491 on the processing of the MML processor, the security of the protocols474 on the processing of the MML processor, the security of the protocols
492 used to transport the data, and the general security practices of475 used to transport the data, and the general security practices of
493 document authors.476 document authors.
494477
495 Nonrepudiation is the most important security consideration, except478 Nonrepudiation is the most important security consideration, except
496 perhaps for encryption, concerning email. The job of nonrepudiation479 perhaps for encryption, concerning email. The job of nonrepudiation
497 rests most prominently with proper storage practices of documents by480 rests most prominently with proper storage practices of documents by
498 users and time/date stamps imposed by email processors on the arrival481 users and time/date stamps imposed by email processors on the arrival
499 of mail documents. MML does contribute to nonrepudiation by482 of mail documents. MML does contribute to nonrepudiation by
500 requiring a timestamp in a manner beyond user control. Please see483 requiring a timestamp in a manner beyond user control. Please see
501 section 4.1.4. Session Time-stamp and 5.2.2. <session> Tag.484 section 4.1.4. Session Time-stamp and 7.2.2. <session> Tag.
502
503
504Cheney Standards Track [Page 9]
505
506Internet-Draft Mail Markup Language - Version 1.0 April 2009
507485
508 MML does provide methods for specifying implementation of public key486 MML does provide methods for specifying implementation of public key
509 distribution to facilitate encryption. Please see section 3.6.487 distribution to facilitate encryption. Please see section 3.6.
510 Public Key Infrastructure.488 Public Key Infrastructure.
511489
512 MML also implements a description scheme for every attached asset490 MML also implements a description scheme for every attached asset
513 using MIME to identify various types of media. Media can only be491 using MIME to identify various types of media. Media can only be
514 executed according to the specified MIME type value. The intent is492 executed according to the specified MIME type value. The intent is
515 that a file that looks like a graphic a d has the file extension of a493 that a file that looks like a graphic a d has the file extension of a
516 a graphic may actually be a malicious executable program, but if it494 a graphic may actually be a malicious executable program, but if it
517 has a specified MIME type of a graphic format it can only open as a495 has a specified MIME type of a graphic format it can only open as a
518 graphic or it MUST fail to open. For more information please see496 graphic or it MUST fail to open. For more information please see
519 section 3.8. Multipurpose Internet Mail Extensions and section 4.1.3.497 section 3.8. Multipurpose Internet Mail Extensions and section 4.1.3.
520 MIME Execution Restriction.498 MIME Execution Restriction.
521499
5223. External Technologies5003. External Technologies
523 In order to advance the functionality of this technology it is501 In order to advance the functionality of this technology it is
524 necessary to incorporate use of prior existing standards.502 necessary to incorporate use of prior existing standards.
525503
504Cheney Standards Track [Page 9]
505
506Internet-Draft Mail Markup Language - Version 1.0 February 2009
507
5263.1. Extensible Markup Language (XML) and W3C XML Schema5083.1. Extensible Markup Language (XML) and W3C XML Schema
527 MML is written in W3C XML Schema, which is written XML. As a result509 MML is written in W3C XML Schema, which is written XML. As a result
528 MML code is case sensitive. This means all tag names MUST be lower510 MML code is case sensitive. This means all tag names MUST be lower
529 case. XML also requires that all attribute values MUST be quoted,511 case. XML also requires that all attribute values MUST be quoted,
530 tags MUST be properly nested, and every opening tag MUST have a512 tags MUST be properly nested, and every opening tag MUST have a
531 corresponding closing tag. Failure to adhere to these syntax rules513 corresponding closing tag. Failure to adhere to these syntax rules
532 will result in the document not validating, which will cause it to514 will result in the document not validating, which will cause it to
533 not send. Please see section 4.1.1. Validation for more information.515 not send. Please see section 4.1.1. Validation for more information.
534516
5353.2. XForms5173.2. XForms
536 XForms is the only form method specified in MML. Where XForms usage518 XForms is the only form method specified in MML. Where XForms usage
537 is allowed it MUST be used in accordance with the XForms schema:519 is allowed it must be used in accordance with the XForms schema:
538 http://www.w3.org/Markup/Forms/2002/XForms-Schema.xsd520 http://www.w3.org/Markup/Forms/2002/XForms-Schema.xsd
539 Processors MUST use XForms version 1.1 to be compliant with this521 Processors MUST use XForms version 1.1 to be compliant with this
540 version of MML.522 version of MML.
541523
5423.3. Accessible Rich Internet Applications5243.3. Accessible Rich Internet Applications
543 The standards specification Accessible Rich Internet Applications,525 The standards specification Accessible Rich Internet Applications,
544 WAI-ARIA, is not included into this version of MML due to the526 WAI-ARIA, is not included into this version of MML due to the
545 specification not being formalized at the time of this writing.527 specification not being formalized at the time of this writing.
546 WAI-ARIA is intended to be implemented in future versions of MML.528 WAI-ARIA is intended to be implemented in future versions of MML.
547 For more information please see http://www.w3c.org/WAI/529 For more information please see http://www.w3c.org/WAI/
548530
5493.4. Resource Document Framework
550 Resource Document Framework, RDF, is not an included technology of
551 this specification, however RDF did significantly influence design
552 patterns of MML. RDF implementation MAY occur as a server-side
553 feature, an optional client specific feature, or a MML processor
554 behavior feature. RDF implementation MUST NOT interfere with
555 conventions, syntax, data, or meta-data supplied in the document
556 directly. This is necessary so that a MML document maintains a5313.4. Resource Document Framework
557532 Resource Document Framework, RDF, is not an included technology of
558533 this specification, however RDF did significantly influence design
559534 patterns of MML. RDF implementation MAY occur as a server-side
560Cheney Standards Track [Page 10]535 feature, an optional client specific feature, or a MML processor
561536 behavior feature. RDF implementation MUST NOT interfere with
562Internet-Draft Mail Markup Language - Version 1.0 April 2009537 conventions, syntax, data, or meta-data supplied in the document
563538 directly. This is necessary so that a MML document maintains a
564 pre-RDF existence for distribution to other users that may not be539 pre-RDF existence for distribution to other users that may not be
565 capable of processing RDF. For more information please see540 capable of processing RDF. For more information please see
566 http://www.w3c.org/RDF/541 http://www.w3c.org/RDF/
567542
5683.5. Stylesheet Technologies5433.5. Stylesheet Technologies
569 This version of MML recognizes only Cascading Style Sheets (CSS) and544 This version of MML recognizes only Cascading Style Sheets (CSS) and
570 Extensible Stylesheets Language (XSL) as stylesheet languages. MML545 Extensible Stylesheets Language (XSL) as stylesheet languages. MML
571 imposes no requirement to support stylesheets. If a MML processor546 imposes no requirement to support stylesheets. If a MML processor
572 does attempt to support a particular stylesheet it SHOULD state what547 does attempt to support a particular stylesheet it SHOULD state what
573 version is supported and SHOULD fully support that version according548 version is supported and SHOULD fully support that version according
574 to its specification. For more information on CSS please see549 to its specification. For more information on CSS please see
575 http://www.w3.org/Style/CSS/ For more information on XSL please see550 http://www.w3.org/Style/CSS/ For more information on XSL please see
576 http://www.w3.org/Style/XSL/551 http://www.w3.org/Style/XSL/
577552
553
554
555
556
557
558
559
560Cheney Standards Track [Page 10]
561
562Internet-Draft Mail Markup Language - Version 1.0 February 2009
563
5783.6. Behaviors and Scripting5643.6. Behaviors and Scripting
579 MML does not support any scripting or behavior technologies. MML565 MML does not support any scripting or behavior technologies. MML
580 processors MUST NOT implement scripting in MML documents. This566 processors MUST NOT implement scripting in MML documents. This
581 version of MML does not provide a solution to likely cross-site567 version of MML does not provide a solution to likely cross-site
582 scripting vulnerabilities, breaches of non-repudiation, or568 scripting vulnerabilities, breaches of non-repudiation, or
583 interference to the integrity of the data that may result from the569 interference to the integrity of the data that may result from the
584 execution of scripting.570 execution of scripting.
585571
5863.7. Public Key Infrastructure5723.7. Public Key Infrastructure
587 MML supports the transfer of public keys by directly embedding the573 MML supports the transfer of public keys by directly embedding the
588 hash value of the public key into the document. MML provides no574 hash value of the public key into the document. MML provides no
589 support for specifications regarding encryption, data transport, or575 support for specifications regarding encryption, data transport, or
590 confidentiality. These are application specific and protocol576 confidentiality. These are application specific and protocol
591 features that exceed the scope of this document. Please see section577 features that exceed the scope of this document. Please see section
592 5.2.8. <public-key> Tag for more information on MML implementation.578 7.2.8. <public-key> Tag for more information on MML implementation.
593 For PKI specifications please see http://www.rsa.com/rsalabs/pkcs/579 For PKI specifications please see http://www.rsa.com/rsalabs/pkcs/
594580
5953.8 Uniform Resource Identifier5813.8 Uniform Resource Identifier
596 Uniform Resource Identifier (URI) is a representation of an address582 Uniform Resource Identifier (URI) is a representation of an address
597 to an external asset. MML requires the use of URIs to specify583 to an external asset. MML requires the use of URIs to specify
598 locations any object or stylesheet. Aside from text the only data584 locations any object or stylesheet. Aside from text the only data
599 that MAY be included directly into the document are public key585 that MAY be included directly into the document are public key
600 hashes. For additional information please refer to RFC 3305.586 hashes. For additional information please refer to RFC 3305.
601587
6023.9. Multipurpose Internet Mail Extensions5883.9. Multipurpose Internet Mail Extensions
603 Multipurpose Internet Mail Extensions (MIME) is specification589 Multipurpose Internet Mail Extensions (MIME) is specification
604 designed to support an expanded character set beyond the basic 7-bit590 designed to support an expanded character set beyond the basic 7-bit
605 ASCII natively supported by SMTP. For more information on the MIME591 ASCII natively supported by SMTP. For more information on the MIME
606 specification please refer to RFC 2045, RFC 2046, RFC 2047, RFC 4288,592 specification please refer to RFC 2045, RFC 2046, RFC 2047, RFC 4288,
607 RFC 4289, and RFC 2077.593 RFC 4289, and RFC 2077.
608594
6094. Processor Roles5954. Processor Roles
610 The role of a processor of MML is to conform to the following596 The role of a processor of MML is to conform to the following
611 specified requirements. Processors of MML are, however, allowed597 specified requirements. Processors of MML are, however, allowed
612 certain freedoms from presumption that are also specified.598 certain freedoms from presumption that are also specified.
613
614
615
616Cheney Standards Track [Page 11]
617
618Internet-Draft Mail Markup Language - Version 1.0 April 2009
619599
620 MML processors are encouraged to test the limits of innovation.600 MML processors are encouraged to test the limits of innovation.
621 Diversity, usability, and customization are necessary results of601 Diversity, usability, and customization are necessary results of
622 competition. The intent of section 4.1. Processor Requirements and602 competition. The intent of section 4.1. Processor Requirements and
623 Constraints is to impose requirements upon MML processors to ensure603 Constraints is to impose requirements upon MML processors to ensure
624 the integrity of the language. The intent of section 4.2. Processor604 the integrity of the language. The intent of section 4.2. Processor
625 Allowances is to illustrate some areas where MML processor vendors605 Allowances is to illustrate some areas where MML processor vendors
626 are free to explore without fear of violating this specification.606 are free to explore without fear of violating this specification.
627607
6284.1. Processor Requirements and Constraints6084.1. Processor Requirements and Constraints
629 The intent of imposing requirements and constraints unto the609 The intent of imposing requirements and constraints unto the
630 processor is to provide a uniform existence for data, meta-data, and610 processor is to provide a uniform existence for data, meta-data, and
631 syntax rules contained in a MML document not at the burden of a611 syntax rules contained in a MML document not at the burden of a
632 document author.612 document author.
633613
614
615
616Cheney Standards Track [Page 11]
617
618Internet-Draft Mail Markup Language - Version 1.0 February 2009
619
6344.1.1. Validation6204.1.1. Validation
635 It is absolutely essential that a MML document MUST validate against621 It is absolutely essential that a MML MUST validate against the MML
636 the MML schema prior to transmission. If a MML document does not 622 schema prior to transmission. If a MML document does not validate it
637 validate it MUST NOT be transmitted as email across any email 623 MUST NOT be transmitted as email across any email specific protocol
638 specific protocol or Hyper Text Transfer Protocol. A MML processor 624 or Hyper Text Transfer Protocol. A MML processor is not REQUIRED to
639 is not REQUIRED to process any malformed or invalid MML document.625 receive any malformed or invalid MML document.
640626
641 It is not invalid, according to some schema validators, for a session627 It is not invalid, according to the schema, for a session author to
642 author to include empty tags, also known as nil content, such as 628 include empty tags, such as <style></style>. Empty tags SHOULD be
643 <style></style>. It is, however, invalid to include nil content 629 removed by the MML processor during validation. Every tag SHOULD
644 elements, in accordance with the XML Schema standard, without
645 explicitly stating the XSI:nil="true" attribute. Empty tags MUST
646 be removed by the MML processor during validation. Every tag SHOULD
647 contain text, other tags, or both if so allowed.630 contain text, other tags, or both if so allowed.
648631
6494.1.2. RFC 2822/5322 Conformance6324.1.2. RFC 2822/5322 Conformance
650 A MML processor MUST create RFC 5322 conformant mail headers for633 A MML processor must create RFC 5322 conformant mail headers for
651 backwards compatibility. MML aware clients/servers MUST remove this634 backwards compatibility. MML aware clients/servers are required to
652 header data and instead rely only upon the header information635 ignore this header data and instead rely only upon the header
653 specified within the MML code. This is necessary to ensure seamless636 information specified within the document. This is necessary to
654 transactions across the SMTP protocol to clients not prepared to 637 ensure seamless transactions with the SMTP protocol. This header
655 receive MML. This header data MUST be created after document 638 data must be created after the user submits a document for transport
656 validation for transport and prior to the document being transported.639 and prior to the document being transported.
657640
6584.1.3. Session Separation and Presentation6414.1.3. Session Separation and Presentation
659 MML processors MUST process each session of a MML document642 MML processors MUST process each session of a MML document
660 separately. This means a stylesheet specified in one particular643 separately. This means a stylesheet specified in one particular
661 session MUST NOT be processed in another session on the same644 session MUST NOT be processed in another session on the same
662 document. For instance a background specified, via stylesheet, in645 document. For instance a background specified, via stylesheet, in
663 one session cannot exist as a background in any other session unless646 one session cannot exist as a background in any other session unless
664 so specified in each other session even if in the same document.647 so specified in each other session even if in the same document.
665648
666 A MML processor SHOULD allow session authors to alter the649 A MML processor SHOULD allow session authors to alter the
667 presentation of all elements and content in a session even if those650 presentation of all elements and content in a session even if those
668 elements or content exist outside the message body. This is not a651 elements or content exist outside the message body. This is not a
669 requirement because MML processors MAY choose to display the session652 requirement because MML processors MAY choose to display the session
670 header information only in their application shell opposed to text.653 header information only in their application shell.
671
672Cheney Standards Track [Page 12]
673
674Internet-Draft Mail Markup Language - Version 1.0 April 2009
675654
6764.1.4. Session Preservation6554.1.4. Session Preservation
677 All prior sessions received in a MML document MUST be preserved656 All prior sessions received in a MML document MUST be preserved
678 verbatim, including whitespace and presentation. Decisions upon 657 verbatim, including whitespace. The only decision that MAY be made
679 prior sessions MUST NOT be allowed except whether external assets MAY658 upon prior sessions is whether external assets can be processed. A
680 be processed. A MML processor SHOULD take steps to prevent prior 659 MML processor SHOULD take steps to prevent prior sessions from manual
681 sessions from manual alteration by a session author.660 alteration by a session author.
682661
6834.1.5. Character Set6624.1.5. Character Set
684 The character set for this version of MML MUST be UTF-16BE. 663 The official character set for this version of MML is UTF16.
685664
6864.1.6. Session Time-stamp6654.1.6. Session Time-stamp
687 The value of the time-stamp attribute MUST be written by the MML666 The value of the time-stamp attribute MUST be written by the MML
688 processor between the moment the session author submits the document667 processor between the moment the session author submits the document
689 for transmission and the validation by the MML processor. The MML668 for transmission and the validation by the MML processor. The MML
690 processor MUST write over any value supplied by the author with the669 processor MUST write over any value supplied by the author with the
691 correct value. The value MUST be based upon the local system clock.670 correct value. The value MUST be based upon the local system clock.
671
672Cheney Standards Track [Page 12]
673
674Internet-Draft Mail Markup Language - Version 1.0 February 2009
692675
6934.1.7. URI Resolution6764.1.7. URI Resolution
694 MML processors MUST set a standard timeout for any URI that is677 MML processors MUST set a standard timeout for any URI that is
695 referenced in a MML document. The length of that timeout MAY be678 referenced in a MML document. The length of that timeout MAY be
696 determined by the MML processor. A MML processor MAY or MAY not679 determined by the MML processor. A MML processor MAY or MAY not
697 allow its user to adjust the timeout length. If a MML processor680 allow its user to adjust the timeout length. If a MML processor
698 cannot resolve any resource at its specified URI timeout that681 cannot resolve any resource at its specified URI timeout that
699 resource MUST fail. If a URI is resolved but points to a location682 resource MUST fail. If a URI is resolved but points to a location
700 that is not the requested resource that resource MUST fail.683 that is not the requested resource that resource MUST fail.
701684
7024.1.8. MIME Execution Restriction6854.1.8. MIME Execution Restriction
703 Every object, stylesheet, or other external resource MUST be686 Every object, stylesheet, or other external resource MUST be
704 processed strictly according to its specified MIME type. If a687 processed strictly according to its specified MIME type. If a
705 resource does not match its associated MIME type it MUST NOT be688 resource does not match its associated MIME type it MUST NOT be
706 executed. A MML processor is not REQUIRED to process any external689 executed. A MML processor is not REQUIRED to process any external
707 resource.690 resource.
708691
7094.1.9. Caching6924.1.9. Caching
710 External assets, such as stylesheets or objects, MUST be cacheable by693 External assets, such as stylesheets or objects, MUST be cacheable by
711 the MML processor. Caching significantly improves performs by694 the MML processor. Caching significantly improves performs by
712 reducing the demand for bandwidth and allowing access to content even695 reducing the demand for bandwidth and allowing access to content even
713 when offline. Options, configuration, and implementation MUST exist696 when offline. Options, configuration, and implementation MUST exist
714 entirely at the discretion of the MML processor.697 entirely at the discretion of the MML processor.
715698
7164.1.10. Local Processing6994.1.10. Local Processing
717 MML processors MUST locally contain all required code components700 MML processors MUST locally contain all required code components
718 necessary to process and validate a MML document according to the701 necessary to process and validate a MML document according to the
719 MML schema. These components can be obtained from the following702 MML schema. These components can be obtained from the following
720 list:703 list:
721704
722 * mail.xsd705 * mml.xsd
723 * http://www.w3.org/MarkUp/Forms/2002/XForms-Schema.xsd706 * http://www.w3.org/MarkUp/Forms/2002/XForms-Schema.xsd
724 * http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-1.xsd707 * http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-1.xsd
725 * http://www.w3.org/2001/XMLSchema.xsd708 * http://www.w3.org/2001/XMLSchema.xsd
726 * http://www.w3.org/2001/03/xml.xsd709 * http://www.w3.org/2001/03/xml.xsd
727
728Cheney Standards Track [Page 13]
729
730Internet-Draft Mail Markup Language - Version 1.0 April 2009
731
732 * http://www.w3.org/2001/XMLSchema.dtd710 * http://www.w3.org/2001/XMLSchema.dtd
733 * http://www.w3.org/2001/datatypes.dtd711 * http://www.w3.org/2001/datatypes.dtd
734 * mime.xsd712 * mime.xsd
735713
736 MML processors MUST NOT require the use of a network or internet714 MML processors MUST NOT require the use of a network or internet
737 connection to process or validate a MML document.715 connection to process or validate a MML document.
738716
7394.1.11. MIME Catalogue7174.1.11. MIME Catalogue
740 A MML processor's list of MIME types for MUST exist as a local schema718 A MML processor's list of MIME types for MUST exist as a local schema
741 file. This file MUST be available for editing by either an719 file. This file MUST be available for editing by either an
742 administrator or common user. Adding new MIME types to the list will720 administrator or common user. Adding new MIME types to the list will
743 likely result in a failure to process outside an internal network.721 likely result in a failure to process outside an internal network.
744 Removing MIME types from the list MUST result in a failure to process722 Removing MIME types from the list MUST result in a failure to process
745 media of those types. By default the values in the MIME catalogue723 media of those types. By default the values in the MIME catalogue
746 file will be every IANA registered type.724 file will be every IANA registered type.
747725
726
727
728Cheney Standards Track [Page 13]
729
730Internet-Draft Mail Markup Language - Version 1.0 February 2009
731
7484.1.12. From and Reply-to Tags7324.1.12. From and Reply-to Tags
749 The <from> and <reply-to> tags are REQUIRED tags, so the tags will733 The <from> and <reply-to> tags are required tags, so the tags will
750 exist even if their content is null. If their content is null the734 exist even if their content is null. If their content is null the
751 MML processor MUST supply default values of the session author's735 MML processor MUST supply default values of the session author's
752 email address. This MML processor supplied default content MUST be736 email address. This MML processor supplied default content MUST be
753 supplied by the MML processor between the moment the session author737 supplied by the MML processor between the moment the session author
754 submits the document for transmission and the REQUIRED validation by738 submits the document for transmission and the required validation by
755 the MML processor. The default value for the <from> tag MUST be the739 the MML processor. The default value for the <from> tag MUST be the
756 address represented by the author. The default value for the740 address represented by the author. The default value for the
757 <reply-to> tag MUST match the default value of the <from> tag.741 <reply-to> tag MUST match the default value of the <from> tag.
758742
759 Session authors are allowed to specify content for these elements to743 Session authors are allowed to specify content for these elements to
760 hide their email address. The benefit is to customize how other744 hide their email address. The benefit is to customize how other
761 session authors can control direct traffic, such as reply and forward745 session authors can control direct traffic, such as reply and forward
762 traffic, back to their email address. It is important to understand746 traffic, back to their email address. It is important to understand
763 the actual traffic benefit of these fields as they offer absolutely747 the actual benefit of these fields as they offer absolutely no
764 no security advantage. MML processors MUST NOT use, process, or748 security advantage. MML processors MUST NOT use, process, or
765 regulate the <from> or <reply-to> tags for any intent related to749 regulate the <from> or <reply-to> tags for any intent related to
766 security. Email transmission protocols operate in unencrypted750 security. Email transmission protocols operate in unencrypted
767 plain-text by default, which is where any user can easily find any751 plain-text by default, which is where any user can easily find any
768 address or identity information.752 address or identity information.
769753
770 Please see section 5.2.4. <to>, <copy>, blind-Copy>, and <from> Tags754 Please see section 7.2.4. <to>, <copy>, blind-Copy>, and <from> Tags
771 and section 5.2.9. <reply-to>.755 and section 7.2.9. <reply-to>.
772756
7734.1.13. Attachments7574.1.13. Attachments
774 Attachments MUST be sent with the actual MML document. Attachment758 Attachments MUST be sent with the actual MML document. Attachment
775 persistence is OPTIONAL. Persistence is a design choice of MML759 persistence is OPTIONAL. Persistence is a design choice of MML
776 processor vendors. Attachment persistence refers to whether or not760 processor vendors. Attachment persistence refers to whether or not
777 attachments will continue to be sent with the MML document after the761 attachments will continue to be sent with the MML document after the
778 document session arrives at its originally intended destination(s).762 document session arrives at its originally intended destination(s).
779 A MML processor SHOULD allow users to choose to allow persistence.763 A MML processor SHOULD allow users to choose to allow persistence.
780764
781 Attachments MUST be processed only according to their specified type.765 Attachments MUST be processed only according to their specified type.
782 A MML processor is not REQUIRED to process any attachment. The type766 A MML processor is not REQUIRED to process any attachment. The type
783 767 specified for <collection-type> must represent every file in that
784Cheney Standards Track [Page 14]
785
786Internet-Draft Mail Markup Language - Version 1.0 April 2009
787
788 specified for <collection-type> MUST represent every file in that
789 respective <collection>. If the <collection-type> tag is not present768 respective <collection>. If the <collection-type> tag is not present
790 the files located in the collection MUST NOT be executable from the769 the files located in the collection MUST NOT be executable from the
791 MML processor, MML document, or any other mail service software.770 MML processor, MML document, or mail environment.
792771
7934.1.14. Processing of <plain-text>7724.1.14. Processing of <plain-text>
794 Content provided in <plain-text> MUST be processed as plain text773 Content provided in <plain-text> MUST be processed as plain text
795 characters and/or whitespace only. Code MUST NOT be processed, 774 characters and/or whitespace only. Code MUST NOT be processed in
796 rendered, or transformed in this tag.775 this tag.
797776
7984.1.15. Processing of style Attribute7774.1.15. Processing of style Attribute
799 The value supplied by the style attribute is defined in the MML778 The value supplied by the style attribute is defined in the MML
800 schema as lowercase alpha characters, uppercase alpha characters,779 schema as lowercase alpha characters, uppercase alpha characters,
801 and/or numbers plus a colon character (:) plus lowercase alpha780 and/or numbers plus a color character (:) plus lowercase alpha
802 characters, uppercase alpha characters, and/or numbers. The781 characters, uppercase alpha characters, and/or numbers. The
803 characters supplied prior to the colon MUST represent the value 782 characters supplied prior to the color MUST represent the value
783
784Cheney Standards Track [Page 14]
785
786Internet-Draft Mail Markup Language - Version 1.0 February 2009
787
804 supplied in a <stylesheet-namespace> element of the same session.788 supplied in a <stylesheet-namespace> element of the same session.
805 The value supplied after the colon SHOULD represent a reusable789 The value supplied after the color must represent a reusable
806 processing declaration defined inside the stylesheet, such as a CSS790 processing declaration defined inside the stylesheet, such as a CSS
807 class. An example of a supplied value: "namespaceName:CSSclass09".791 class. An example of a supplied value: "namespaceName:CSSclass09".
808792
809 MML processors are not REQUIRED to process stylesheets. If the noted793 MML processors are not REQUIRED to process stylesheets. If the noted
810 stylesheet cannot be resolved or if the value supplied by the style794 stylesheet cannot be resolved or if the value supplied by the style
811 attribute is either malformed or fails to match a stylesheet of the795 attribute is either malformed or fails to match a stylesheet of the
812 same session this attribute MUST NOT be processed.796 same session this attribute MUST NOT be processed.
813797
8144.1.16. Internationalization Attribute Processing7984.1.16. Internationalization Attribute Processing
815 Text MUST be processed in accordance with the defined values for the799 Text MUST be processed in accordance with the defined values for the
816 four internationalization attributes. For processing descriptions800 four internationalization attributes. For processing descriptions
817 please refer to these sections:801 please refer to these sections:
818 * section 5.4.6. direction Attribute802 * section 7.4.6. direction Attribute
819 * section 5.4.7. orientation Attribute803 * section 7.4.7. orientation Attribute
820 * section 5.4.8. wrap Attribute804 * section 7.4.8. wrap Attribute
821 * section 5.4.9. section-language Attribute805 * section 7.4.9. section-language Attribute
822806
823 Failure to process internationalization attributes according to 807 Failure to comply with internationalization MUST result in standards
824 their definition MUST result in conditional compliance failure.808 failure of this specification.
825809
8264.1.17. xmlns Attribute 8104.1.17. refer Attribute Processing
827 The xmlns attribute is not defined in this specification. It is
828 defined in the specification for Namespaces in XML 1.0. It is
829 considered an included technology by virtue of the xml.xsd schema
830 that is imported into the XMLSchema.xsd schema and XMLSchema.xsd is
831 imported into the mail.xsd that defines MML. Use of the xmlns
832 attribute MUST be allowed on the <session> element and any element
833 contained by the <session> element in accordance with XML processing
834 guidance defined by XML and Namespace standards.
835
836
837
838
839
840Cheney Standards Track [Page 15]
841
842Internet-Draft Mail Markup Language - Version 1.0 April 2009
843
8444.1.18. refer Attribute Processing
845 The refer attribute MUST NOT be allowed to reference id values811 The refer attribute MUST NOT be allowed to reference id values
846 outside the specific <markup> element containing the refer attribute.812 outside its <markup> container. For more information see 7.4.12
847 For more information see 5.4.12 refer Attribute.813 refer Attribute.
848814
8494.2. Processor Allowances8154.2. Processor Allowances
850 This document does not exist to define the role of MML processors for816 This document does not exist to define the role of MML processors for
851 features that exceed the scope of this document. This section only817 features that exceed the scope of this document. This section only
852 serves to dispel assumptions and specify certain freedoms allowed to818 serves to dispel assumptions and specify certain freedoms allowed to
853 MML processors that may not be allowed to processors of other markup819 MML processors that may not be allowed to processors of other markup
854 languages.820 languages.
855821
8564.2.1. Default Presentation8224.2.1. Default Presentation
857 This specification does not make any statements regarding823 This specification does not make any statements regarding
858 presentation of the language. This means a MML processor is free to824 presentation of the language. This means a MML processor is free to
859 determine the default presentation for tags and objects. This825 determine the default presentation for tags and objects. This
860 default presentation MAY apply to any or all parts of a MML document.826 default presentation MAY apply to any or all parts of a MML document.
861 This means that presentation provided from a MML processor fits a827 This means that presentation provided from a MML processor fits a
862 wider scope than presentation specified by a MML author since any MML828 wider scope than presentation specified by a MML author since any MML
863829
864 author can only specify presentation by use of an external stylesheet830 author can only specify presentation by use of an external stylesheet
865 and stylesheet processing is limited to its session of the document.831 and stylesheet processing is limited to its session of the document.
866832
867 MML processor default presentation MUST be lower priority than833 MML processor default presentation MUST be lower priority than
868 presentation defined in a stylesheet. If a conflict in presentation834 presentation defined in a stylesheet. If a conflict in presentation
869 arises between the default and a stylesheet the presentation835 arises between the default and a stylesheet the presentation
870 specified by the stylesheet MUST dominate even in regards to836 specified by the stylesheet MUST dominate even in regards to
871 cascading.837 cascading.
872838
839
840Cheney Standards Track [Page 15]
841
842Internet-Draft Mail Markup Language - Version 1.0 February 2009
843
873 This means a MML processor determines font size, color, font, and so844 This means a MML processor determines font size, color, font, and so
874 on until so specified by a stylesheet. A MML processor determines,845 on until so specified by a stylesheet. A MML processor determines,
875 by default, whether complex and simple blocks impose a line break,846 by default, whether complex and simple blocks impose a line break,
876 wrap, float, or so on.847 wrap, float, or so on.
877848
878 A MML processor MAY or MAY not allow a user to customize or alter its849 A MML processor MAY or MAY not allow a user to customize or alter its
879 default presentation. This specification will not mandate850 default presentation. This specification will not mandate
880 customization, however, accessibility concerns SHOULD be considered851 customization, however, accessibility concerns SHOULD be considered
881 for changing text size, turning off stylesheets, and replacing852 for changing text size, turning off stylesheets, and replacing
882 objects with their respective text content.853 objects with their respective text content.
883854
8844.2.2. Default Behaviors8554.2.2. Default Behaviors
885 This specification states not directive for behaviors or controls856 This specification states not directive for behaviors or controls
886 upon the data or the usability thereof. There is no convention for857 upon the data or the usability thereof. There is no convention for
887 allowing scripting in MML and any scripting that does exist MUST be858 allowing scripting in MML and any scripting that does exist MUST be
888 processed as plain text content. MML processors SHOULD allow859 processed as plain text content. MML processors SHOULD allow
889 behaviors that increase accessibility more importantly than860 behaviors that increase accessibility more importantly than
890 usability.861 usability.
891862
892 Section 3.3. Resource Document Framework states that RDF is not an863 Section 3.3. Resource Document Framework states that RDF is not an
893 included technology in this specification and MUST NOT interfere864 included technology in this specification and MUST NOT interfere
894 with conventions, syntax, data, or meta-data supplied in the document865 with conventions, syntax, data, or meta-data supplied in the document
895
896Cheney Standards Track [Page 16]
897
898Internet-Draft Mail Markup Language - Version 1.0 April 2009
899
900 directly. What it does not say is that semantic technologies MAY be866 directly. What it does not say is that semantic technologies MAY be
901 used to auto-fill many areas of MML based upon a user's data habits.867 used to auto-fill many areas of MML based upon a user's data habits.
902 Semantic technologies MAY also be used for searching, data sorting,868 Semantic technologies may also be used for searching, data sorting,
903 or other processing features to the data defined by the MML document.869 or other features.
904 Those semantic technologies MUST NOT, however, alter the contents of870
905 the MML document.8715. Default mime.xsd
906
9074.2.3. Processing Elaborations Over Native MML Definitions
908 MML processors MUST be capable of processing the full MML
909 specification. MML processors MAY allow processing of or definition
910 of elements or conventions not defined by this MML specification.
911 Such elaborations MUST NOT interfere, limit, constrain, remove, or
912 disable any aspect of the MML specification. Any elaboration,
913 element, or convention not defined by this MML specification is not
914 required of MML processors.
915
9165. MML Schema Documentation
917 This section is intended to provide a description of the language
918 along with justifications for certain conventions used. This section
919 is informational only. All processing declarations are stated in
920 section 4. Processor Roles and section 5. MML Schema.
921
922 If an element is followed by "0" it MAY occur 0 or 1 time. If an
923 element is followed by "+" it MUST occur once, but it MAY occur more
924 than once. If an item is followed by "0+" it MAY occur 0 or more
925 times. If an element does not have these descriptors it MUST occur
926 once and only once. Attributes MAY be followed by "0", which
927 indicates the attribute in concern is optional. Attributes MUST NOT
928 occur more than once in any element.
929
930 Those elements noted as (XForms) are defined by the XForms
931 specification and not this document. For more information see
932 section 3.2. XForms and 4.1.8. Local Processing. These elements MUST
933 be processed in strict accordance with the XForms schema.
934
9355.1. MIME Type Usage and mime.xsd
936 MIME types MUST be stored in the mime.xsd document, which is merely a
937 catalogue of all IANA registered MIME types at the time of this
938 writing. The information stored in mime.xsd is used in the MML
939 schema through the use of the "mime-type" schema complex type.
940
941 Elements based upon the "mime-type" element type are allowed only one
942 of nine possible child elements. These child elements each represent
943 a IANA registered content type. The values for those child elements
944 MUST be a MIME sub-type that exists in the local mime.xsd file. The
945 child elements are:
946 * <application> or <audio> or <example> or <image> or <message> or
947 <model> or <multipart> or <text> or <video>
948
949
950
951
952Cheney Standards Track [Page 17]
953
954Internet-Draft Mail Markup Language - Version 1.0 April 2009
955
9565.2. MML Header Documentation
957 The code described in this section exists in MML documents without
958 regard to how the message is formatted. For more information about
959 the message body see section 5.2.2. <session> Tag and section 5.3.
960 <markup> Element Documentation.
961
9625.2.1. Root Element
963 The root element of MML is the tag <mail>. The root tag is only
964 capable of containing <session> elements. This tag MUST contain the
965 following attributes:
966 xsi:noNamespaceSchemaLocation="http://mailmarkup.org/mail.xsd"
967 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
968 xmlns:xfm="http://www.w3.org/2002/xforms"
969 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
970 mail-type="application/mail"
971 version="1.0"
972
9735.2.2. <session> Tag
974 The session tag contains all information to represent an instance of
975 communication including markup and header information. A session
976 tag's child tags are as follows:
977 * <xsd:import> 0+
978     * <xsd:include> 0+
979 * <address>
980 * <attachments> 0
981 * <subject>
982 * <presentation> 0
983 * <source> or <markup> or <plain-text>
984
985 The <session> tag's attributes:
986 * time-stamp
987 * language (optional)
988
989 The session tag allows three methods of communicating the message
990 body. The source method allows a session author to send an external
991 resource as the message body. Please see section 5.2.26 <source>
992 Tag. The plain-text method allows a session author to communicate
993 using only text characters and whitespace. Please see section
994 5.2.29. <plain-text> Tag. The markup method allows a section author
995 to use MML markup to describe the data. Please see section 5.2.30.
996 <markup> Tag and section 5.3. <markup> Organization of Types and
997 Groups and 5.4. <markup> Attributes and 5.5. <markup> Elements.
998
999 The time-stamp attribute is described in section 4.1.6. Session
1000 Time-stamp. The optional language attribute allows a session author
1001 to describe the majority language of the session. The default value
1002 is "EN" if none is specified. Mail client software SHOULD allow a
1003 user to specify a default value for the language attribute.
1004
1005
1006
1007
1008Cheney Standards Track [Page 18]
1009
1010Internet-Draft Mail Markup Language - Version 1.0 April 2009
1011
10125.2.3. <address> Tag
1013 The address tag is a high level tag designed to store child tags
1014 containing email address information. The child tags are:
1015 * <to> +
1016 * <copy> 0+
1017 * <blind-copy> 0+
1018 * <reply-to>
1019 * <from>
1020
10215.2.4. <to>, <copy>, <blind-Copy>, and <from> Tags
1022 The <to>, <copy>, <blind-copy>, and <from> are identical in their
1023 syntax. They only differ in their use by the MML processor. These
1024 tags store only the value of a properly formed email address. These
1025 tags may contain the optional attributes of alias and public-key.
1026 The alias is designed to contain a value that is a more human
1027 readable representation of an email address, such as a person's name.
1028 The public-key attribute is intended to store text characters that
1029 represent a hashed public-key for asymmetric encryption.
1030
1031 The <to>, <copy>, <blind-Copy>, and <from> tag's attributes:
1032 * alias (optional)
1033     * public-key (optional)
1034
10355.2.5. <reply-to> Tag
1036 The <reply-to> tag is identical to the <from> tag except that it may
1037 contain either a valid email address or a value of no-reply. This
1038 tag is used to set an address for deflecting email replys from the
1039 address used to send the email or to establish an alternate
1040 destination for receiving replies.
1041
10425.2.6. <attachments> Tag
1043 The <attachments> tag is a high level tag for specifying file to be
1044 attached to the document. Attached files are not intended for
1045 processing in the message body. This tag has two children which may
1046 occur as many times as needed. At a minimum only one of these child
1047 elements MUST occur:
1048 * <collection> + and/or <file> +
1049
10505.2.7 <collection> Tag
1051 The <collection> tag is intended to serve as a collection of multiple
1052 files of the same specified type. This tag has four child tags:
1053 * <collection-name>
1054 * <collection-file> +
1055 * <collection-type> 0
1056 * <collection-description>
1057
10585.2.8. <collection-name> Tag
1059 <collection-name> tag is a REQUIRED child of <collection>. This may
1060 be any string value on a single line. The intent of this tag is to
1061 provide a simple name or label for the attached collection.
1062
1063
1064Cheney Standards Track [Page 19]
1065
1066Internet-Draft Mail Markup Language - Version 1.0 April 2009
1067
10685.2.9. <collection-file> Tag
1069 <collection-file> tag stores the file name of a particular file in a
1070 collection. This tag MUST exist for each file that is to exist in
1071 the collection.
1072
10735.2.10. <collection-type> Tag
1074 The <collection-type> tag is a "mime-type" complex-type tag as
1075 specified in mime.xsd. The value provided for this tag MUST
1076 represent every file in the collection. This tag is optional. If
1077 this tag is not present the files present in the collection MUST NOT
1078 be processed by the MML processor. See section 4.1.11. Attachments
1079 for information on processing requirements. Please see section 5.1.
1080 MIME Type Usage and mime.xsd for information about the specified type
1081 "mime-type". MML processors are not REQUIRED to process attached
1082 collections.
1083
10845.2.11. <collection-description> Tag
1085 This tag exists to specify a description of the collection. Examples
1086 of content for this tag MAY be examples of intended use,
1087 explanations, file ownership, origin information, and so forth.
1088
10895.2.12. <file> Tag
1090 The <file> tag is intended to serve as a single attached file. This
1091 tag has three child tags:
1092 * <file-name>
1093 * <file-type>
1094 * <file-description>
1095
10965.2.13. <file-name> Tag
1097 <file-name> tag is a REQUIRED child of <file>. The value for this
1098 tag MUST be a non-colonized name. This tag represents the name of
1099 the file being attached.
1100
11015.2.14. <file-type> Tag
1102 This tag is of type "mime-type". The attached file MUST be processed
1103 according to the value supplied in this tag, or it MUST NOT be
1104 processed by a MML processor. MML processors are not required to
1105 process attached files.
1106
11075.2.15. <file-description> Tag
1108 This tag allows a session author to enter any normalized string value
1109 that describes the attached file. This tag is REQUIRED.
1110
11115.2.16. <subject> Tag
1112 The <subject> tag value id a normalized string. This REQUIRED tag
1113 sets the subject of the document session. This tag is equivalent to
1114 the subject of traditional email.
1115
1116
1117
1118
1119
1120Cheney Standards Track [Page 20]
1121
1122Internet-Draft Mail Markup Language - Version 1.0 April 2009
1123
11245.2.17. <presentation> Tag
1125 All presentation, aside from MML default presentation, is set for a
1126 session in this high level tag. This tag is nothing more than a
1127 container for its one child element that may occur more than once.
1128 * <stylesheet> +
1129
11305.2.18. <stylesheet> Tag
1131 Each <stylesheet> tag represents a single stylesheet reference. This
1132 tag MUST have a valid URI as its value and has two required
1133 attributes and one optional attribute. The optional media attribute
1134 identifies the output media the stylesheet is attempting to supply
1135 presentation for. If this attribute is not specified its default
1136 value of "screen" MUST be assumed. The required attribute
1137 style-namespace is a named value that will serve as named prefix for
1138 stylesheet declarations from this stylesheet. The prefix is REQUIRED
1139 for stylesheet references using the "style" attribute that is
1140 available to elements in the <markup> section of the session. See
1141 section 5.4.3. style Attribute for more information. The REQUIRED
1142 attribute, "style-type", accepts only one of three values:
1143 * application/xml
1144 * text/xsl
1145 * text/css
1146
11475.2.19. <source> Tag
1148 The <source> tag is one of three methods of creating the message
1149 body. The intent of this tag is to allow an external resource to act
1150 as the message body. There is no requirement for a MML processor to
1151 process any external resource, so the content established by the
1152 <source> tag may not always be communicated. This tag has two
1153 REQUIRED children:
1154 * <source-uri>
1155 * <source-type>
1156
11575.2.20. <source-uri> Tag
1158 This tag MUST only contain a URI of the requested resource that is to
1159 act as the body of the session.
1160
11615.2.21. <source-type> Tag
1162 This tag is of element type "mime-type". The type determines how or
1163 if the external resource described in <source-uri> will be processed
1164 by the document's destination.
1165
11665.2.22. <plain-text> Tag
1167 This tag is the second of the three methods for communicating the
1168 body of the session. This tag MUST contain only plain text. Code
1169 MUST NOT be processed in this tag. The intent of this tag is to
1170 allow session authors to communicate using text without interference
1171 to the processing of that content. Presentation MAY be applied to
1172 <plain-text> content if the MML processor so allows and a stylesheet
1173 is provided.
1174
1175
1176Cheney Standards Track [Page 21]
1177
1178Internet-Draft Mail Markup Language - Version 1.0 April 2009
1179
11805.2.23. <markup> Tag
1181 This tag allows the use of MML to describe and organize content.
1182 This is the advised method of communicating content in MML. See
1183 section 5.3. <markup> Element Documentation for more information.
1184
11855.3. <markup> Organization of Types and Groups
1186 This section is intended to providing descriptive documentation for
1187 the part of the language dedicated to describing information that is
1188 intended to be read by an email recipient as a message body.
1189
11905.3.1. <markup> Element Organization
1191 The elements in this section of MML are arranged in three groups:
1192 complex-blocks, simple-blocks, and inline elements.
1193
1194 A complex-block is a tag that is capable of containing of either
1195 simple-blocks or simple-blocks plus other complex-blocks. Complex-
1196 blocks are not capable of containing text content of inline elements.
1197 These following tags are the high level complex-blocks:
1198 * <define-list>
1199 * <navigation-list>
1200 * <order-list>
1201 * <unorder-list>
1202 * <table>
1203 * <section>
1204 * <form>
1205
1206 A simple-block is a tag that is capable of containing text and inline
1207 elements, but is not capable of containing other simple-blocks or
1208 complex-blocks.
1209 * <block-code>
1210 * <block-quote>
1211 * <citation>
1212 * <heading>
1213 * <object>
1214 * <paragraph>
1215 * <separator>
1216
1217 Inline elements are not structural elements. These elements MUST
1218 exist in a simple-block container. Inline elements are intended to
1219 describe text content, supply additional meta-data, or apply more
1220 specific presentation.
1221 * form controls (XForms)
1222 * <short>
1223 * <button>
1224 * <cite>
1225 * <emphasis>
1226 * <identifier>
1227 * <quote>
1228 * <format>
1229 * <strong>
1230 * <title>
1231
1232Cheney Standards Track [Page 22]
1233
1234Internet-Draft Mail Markup Language - Version 1.0 April 2009
1235
12365.3.2. <markup> Attribute Organization
1237 The attributes in the <markup> section of MML are arranged in the
1238 following attribute groups: "core attributes", "core attributes plus
1239 uri", "internationalization attributes", and "cell attributes".
1240 The "core attributes" are applied to nearly every element in the
1241 markup section. This attribute group is always optional. The group
1242 contains the following attributes:
1243 * id
1244 * title
1245 * style
1246 * role
1247
1248 The "core attributes plus uri" group is literally the "core
1249 attributes" group with the added uri attribute. It was necessary to
1250 specify these two groups separately because many elements require a
1251 URI and many MUST NOT receive a URI. These attributes are in the
1252 "core attributes plus uri" group:
1253 * id
1254 * title
1255 * style
1256 * role
1257 * uri
1258
1259 The "internationalization attributes" exist only to alter the order
1260 in which text is rendered. This is not a presentation issue of
1261 altering how text appears, but how it appears to work to the computer
1262 for the benefit of assistive technologies and other languages. This
1263 group contains these attributes:
1264 * direction
1265 * orientation
1266 * wrap
1267 * section-language
1268
1269 The "cell attributes" group is a set of attributes specific to table
1270 cell elements. These attributes include the following:
1271 * span-column
1272 * span-row
1273
12745.4. <markup> Attributes
1275 This section is a per attribute list of attributes used by variou
1276 tags in the <markup> section of a MML document.
1277
12785.4.1. id Attribute
1279 This attribute exists to assign a unique identification to an
1280 element. The value for this attribute MUST contain only lowercase
1281 alpha characters, uppercase alpha characters, and/or numbers. The
1282 value MUST NOT contain any other characters including whitespace.
1283 This attribute is intended to create a unique hook to a particular
1284 element for MML processor specific behavior or presentation. There
1285 are some elements that exist as a pair set and require the id
1286
1287
1288Cheney Standards Track [Page 23]
1289
1290Internet-Draft Mail Markup Language - Version 1.0 April 2009
1291
1292 attribute to refer to each other. The id attribute MUST be unique
1293 per <session> section and MAY NOT be unique per a MML document of
1294 multiple sessions.
1295
12965.4.2. title Attribute
1297 The title attribute is intended to supply additional content to an
1298 element beyond its contained text. The value for this attribute MUST
1299 be whitespace normalized text. This attribute is supplied for the
1300 semantic and accessibility benefits of expanded meta-data for human
1301 consumption.
1302
13035.4.3. style Attribute
1304 This attribute exists to reference a reusable stylesheet property.
1305 The value for this attribute MUST be a set of lowercase alpha
1306 characters, uppercase alpha characters, and/or numbers plus a colon
1307 (:) plus lowercase alpha characters, uppercase alpha characters,
1308 and/or numbers. The value before the colon MUST represent the
1309 value of any supplied <stylesheet-namespace> element. This tells the
1310 MML processor which stylesheet the style reference is referring to.
1311 The value after the colon MUST represent some value defined in the
1312 stylesheet, such as a CSS class name. An example is:
1313 "namespace:CSSclass09".
1314
13155.4.4. role Attribute
1316 This attribute is intended to allow for specific semantic
1317 redefinition of any element where its use is allowed. If a session
1318 author had the ability to rename a tag to something more semantically
1319 specific that new name is the value that SHOULD fill the role
1320 attribute. The value of the role attribute SHOULD NOT challenge or
1321 contradict the intent of the named element it is used with.
1322
1323 This attribute is expected to offer significantly expanded utility in
1324 future versions of MML. The WAI-ARIA technology and RDF derived
1325 technologies are expected to benefit from use of the role attribute.
1326
13275.4.5. uri Attribute
1328 This attribute MUST contain only a URI value as defined by RFC 3986
1329 or RFC 2368 for email addresses specifically. Use of this attribute
1330 is equivalent to imposing a webpage hyperlink. A same-document
1331 referrence MUST refer only to the value of a specified id attribute
1332 value within the same session.
1333
13345.4.6. direction Attribute
1335 The direction Attribute determines which direction the text is to
1336 flow as it is typed. The default value is left to right if
1337 orientation has a value of horizontal or top to bottom if
1338 orientation has a value of vertical. The acceptable values are "tl",
1339 which indicates starting from the top or left, or "br", which
1340 indicates starting from the bottom or right.
1341
1342
1343
1344Cheney Standards Track [Page 24]
1345
1346Internet-Draft Mail Markup Language - Version 1.0 April 2009
1347
13485.4.7. orientation Attribute
1349 This attribute determines whether text characters render in a
1350 vertical or horizontal manner. The acceptable values are
1351 "horizontal" or "vertical". Horizontal is the default value.
1352
13535.4.8. wrap Attribute
1354 This attribute determines how lines of text are rendered to the page.
1355 The acceptable values for this attribute are "standard", "reverse",
1356 or "none". A value of "standard" does nothing different and is the
1357 default value. The value "reverse" MUST force text render opposite
1358 of its standard behavior.
1359
1360 Assuming direction and orientation are at default standard behavior
1361 is to wrap a line of text below the prior existing text. Under those
1362 conditions a value of "reverse" MUST force the line of text to wrap
1363 above the prior existing line of text.
1364
1365 A value of "none" forces the text to not wrap. Under the condition
1366 that non-wrapping text is wider or taller than its container the
1367 container MUST stretch and the page MUST scroll to keep the text
1368 visibly legible so long as there are not presentation specifications
1369 to the contrary.
1370
13715.4.9. section-language Attribute
1372 The attribute section-language specifies the language of a particular
1373 section, container, or element in the <markup> section. This is
1374 absolutely necessary to alert readers and semantic devices that the
1375 language has changed from the default specified language. The values
1376 for this attribute MUST be a two digit XML language code.
1377
13785.4.10. span-column Attribute
1379 This attribute allows a <table-cell> or <head-cell> to occupy more
1380 than one column in a table. The values for this attribute MUST be a
1381 positive integer. The default value is "1".
1382
13835.4.11. span-row Attribute
1384 The attribute span-row allows a <table-cell> or <head-cell> to occupy
1385 more than one row in a table. The values for this attribute MUST be
1386 a positive integer. The default value is "1".
1387
13885.4.12. refer Attribute
1389 This attribute is a reference to the value of an id attribute
1390 supplied on another element of the same <markup> section. If the
1391 value of this attribute does not match an existent id attribute value
1392 the document MUST NOT validate.
1393
13945.4.13. scope Attribute
1395 This attribute is used in table header cells to determine which table
1396 cells the header is providing a heading for. The values for this
1397 attribute MUST be: column, row, group-column, or group-row.
1398
1399
1400Cheney Standards Track [Page 25]
1401
1402Internet-Draft Mail Markup Language - Version 1.0 April 2009
1403
1404 The value "column" dictates that a header cell is providing a heading
1405 for only the first column of cells the header cell occupies. The
1406 value "row" dictates that a header cell is providing a heading for
1407 only the first row of cells the header cell occupies. A value of
1408 "group-column" dictates that a header cell provides a heading for all
1409 cells in all columns that it occupies. The value "group-row"
1410 dictates the header cell is providing a heading for all cells in all
1411 rows it occupies.
1412
1413 The word first, as used in defining column and row as values to the
1414 scope attribute, MUST refer to the first group of elements as
1415 dictated by the rendering direction of text set using
1416 internationalization attributes.
1417
14185.4.14. long-form Attribute
1419 This attribute MUST serve to represent the expanded text that is
1420 described by the <short> element. An example is: <short
1421 long-form="Mail Markup Language">MML</short>.
1422
14235.5. <markup> Elements
1424 This section is a per element list of all elements that MAY exist in
1425 the <markup> section of a MML document.
1426
14275.5.1. <define-list> Tag
1428 This element is intended to establish a list of definitions by
1429 matching any number of defining terms to any number of definitions.
1430 This element contains only one child element, but that element may be
1431 used more than once.
1432 Child:
1433 * <define-item> +
1434
1435 Attributes:
1436 * core attributes 0
1437
14385.5.2. <define-item> Tag
1439 The <define-item> tag represents a single defining instance.
1440 The associations draw by the child tags are as follows: multiple
1441 defining terms mapped to a single definition, a single term mapped
1442 against multiple definitions, or multiple terms that commonly share
1443 multiple definitions. As a result of these three possible
1444 associations at least one of each child element MUST occur.
1445 Children:
1446 * <define-term> +
1447 * <definition> +
1448
1449 Attributes:
1450 * core attributes 0
1451
1452
1453
1454
1455
1456Cheney Standards Track [Page 26]
1457
1458Internet-Draft Mail Markup Language - Version 1.0 April 2009
1459
14605.5.3. <define-term> Tag
1461 This tag is intended to contain a single term, phrase, or clause to
1462 be defined. The value for this tag MUST be whitespace collapsed
1463 text.
1464
1465 Attributes:
1466 * core attributes plus uri 0
1467 * internationalization attributes 0
1468
14695.5.4. <definition> Tag
1470 This tag is intended to contain the definition text that defines the
1471 associated terms. The value for this tag can be text and inline
1472 elements.
1473 Children:
1474 * inline elements 0+
1475
1476 Attributes:
1477 * core attributes 0
1478 * internationalization attributes 0
1479
14805.5.5. <navigation-list> Tag
1481 The <navigation-list> tag establishes a list of items that exist to
1482 either direct traffic or create a menu of URIs. This tag allows for
1483 either a heading or a set of descriptive text and at least one
1484 navigation item.
1485 Children:
1486 * <heading> 0 or <identifier> 0
1487 * <navigation-item> +
1488
1489 Attributes:
1490 * core attributes 0
1491
14925.5.6. <navigation-item> Tag
1493 This element is a single instance of navigation in a list of
1494 navigation choices. This element may contain either an object for
1495 navigation or text for navigation as determined by its child tags.
1496 A uri attribute is REQUIRED on this element.
1497 Children:
1498 * <navigation-object> or <navigation-text>
1499
1500 Attributes:
1501 * core attributes 0
1502 * uri
1503
15045.5.7. <navigation-object> Tag
1505 The <navigation-object> is a standard <object> that is modified to
1506 not allow use of the uri attribute. This tag SHOULD only be used if
1507 the focus of navigation for the <navigation-item> of concern is an
1508 external resource expected to be processed into the content of the
1509
1510
1511
1512Cheney Standards Track [Page 27]
1513
1514Internet-Draft Mail Markup Language - Version 1.0 April 2009
1515
1516 message body. Two children elements are REQUIRED. For information
1517 on the child elements see sections 5.5.25. <object-uri> Tag and
1518 5.5.26. <object-type> Tag.
1519
1520 It is important that an object contain text content that describes
1521 its resource. There is no requirement for MML processors to process
1522 any external resource. If the resource does fail to process the text
1523 contained by the object MUST display.
1524 Children:
1525 * <object-text>
1526 * <object-uri>
1527 * <object-type>
1528
1529 Attributes:
1530 * core attributes 0
1531 * internationalization attributes 0
1532
15335.5.8. <navigation-text> Tag
1534 The content of this element is text and whitespace that is the focus
1535 of navigation. This tag has no child elements.
1536 Attributes:
1537 * core attributes 0
1538 * internationalization attributes 0
1539
15405.5.9. <order-list> Tag
1541 An ordered list is a list where each item in that list is enumerated
1542 in the meta-data so that the position of elements in the list
1543 relative to other list items is valid data. Whether or not this
1544 enumeration appears is to a human reader is strictly a presentation
1545 concern. This element is allowed descriptive text in the form of a
1546 <heading> or <identifier> child. Each occurs in the list MUST exist
1547 in the <list-item> child. An example of a list that must be ordered
1548 is step-by-step directions, such as a recipie.
1549 Children:
1550 * <heading> 0 or <identifier> 0
1551 * <list-item> +
1552
1553 Attributes:
1554 * core attributes 0
1555
15565.5.10. <unorder-list> Tag
1557 An unordered list is nearly identical to an ordered list except that
1558 list items are not enumerated. This means position of items in the
1559 list is irrelevant.
1560 Children:
1561 * <heading> 0 or <identifier> 0
1562 * <list-item> +
1563
1564 Attributes:
1565 * core attributes 0
1566
1567    
1568Cheney Standards Track [Page 28]
1569
1570Internet-Draft Mail Markup Language - Version 1.0 April 2009
1571
15725.5.11. <list-item> Tag
1573 This element represents a single listed instantiation in a either an
1574 ordered or unordered list. This element may contain a single simple
1575 block element or text plus 0 or more inline elements.
1576 Children:
1577 * simple block element or text plus inline elements 0+
1578
1579 Attributes:
1580 * core attributes 0
1581 * internationalization attributes 0
1582
15835.5.12. <form> Tag
1584 The <form> tag is the high level parent container of a form. A form
1585 allows organized controls upon input and submission of information in
1586 a method different than a standard email reply.
1587 Children:
1588 * <model> (XForms)
1589 * <form-body>
1590
15915.5.13. <form-body>
1592 The <form-body> element is intended to contain all the form controls
1593 that a user could interact with plus other MML elements.
1594 Children:
1595 * <define-list> 0+
1596 * <navigation-list> 0+
1597 * <order-list> 0+
1598 * <unorder-list> 0+
1599 * <table> 0+
1600 * simple blocks 0+
1601 * form controls 0+ (XForms)
1602
16035.5.14. <table> Tag
1604 The <table> element allows authors to store and organize data in a
1605 grid or chart fashion.
1606 Children:
1607 * <head-row> 0
1608 * <table-row> +
1609
1610 Attributes:
1611 * core attributes 0
1612
16135.5.15. <head-row> Tag
1614 The header row is a container of header cells to provide meta-data
1615 for tables.
1616 Child:
1617 * <head-cell> +
1618
1619 Attributes:
1620 * core attributes 0
1621
1622
1623
1624Cheney Standards Track [Page 29]
1625
1626Internet-Draft Mail Markup Language - Version 1.0 April 2009
1627
16285.5.16. <table-row> Tag
1629 A <table-row> MAY carry header cells or standard table cells. A
1630 row is the standard unit of organization in a MML table.
1631 Children:
1632 * <head-cell> + or <table-cell> +
1633
1634 Attributes:
1635 * core attributes 0
1636
16375.5.17. <head-cell> Tag
1638 A header cell provides meta-data that either labels or describes the
1639 data contained within its scope. The scope of the header cell is
1640 determined by use of the scope attribute. See section 5.4.13. scope
1641 Attribute for more information. A header cell MUST contain either a
1642 single simple block or text plus any number of inline elements.
1643 Children:
1644 * simple blocks 0 or text plus inline elements 0+
1645
1646 Attributes:
1647 * cell attributes 0
1648 * core attributes 0
1649 * internationalization attributes 0
1650 * scope 0
1651
16525.5.18. <table-cell> Tag
1653 The table cell is the standard unit of data in a table cell. A table
1654 cell is not intended to provide any meta-data about the table or the
1655 structure of the table. A table cell is intended to provide data
1656 directly to the user. A table cell MUST contain either a single
1657 complex block or text plus any number of inline elements.
1658 Children:
1659 * simple blocks 0 or text plus inline elements 0+
1660
1661 Attributes:
1662 * cell attributes 0
1663 * core attributes 0
1664 * internationalization attributes 0
1665
16665.5.19. <section> Tag
1667 A section is a high level structural organization block. This is the
1668 only complex block capable of containing itself, such as nesting.
1669 The intent of the <section> tag is to subdivide the markup into
1670 various smaller areas for content organization, separation, and
1671 semantics.
1672 Children:
1673 * complex blocks 0+ and/or simple blocks 0+
1674
1675 Attributes:
1676 * core attributes 0
1677
1678
1679
1680Cheney Standards Track [Page 30]
1681
1682Internet-Draft Mail Markup Language - Version 1.0 April 2009
1683
16845.5.20. <block-code> Tag
1685 The block code simple block is intended to convey and describe code.
1686 The contents of this container MUST NOT directly contain XML reserved
1687 characters. An XML processor cannot be told to not process
1688 characters that construct its syntax. These reserved characters can
1689 be used if they are escaped with a character entity reference. Mail
1690 client software SHOULD automatically transform the reserved
1691 characters into hex character entities. The reserved characters and
1692 their corresponding character entity references are:
1693 Character Hex Name
1694 < &#60; &lt;
1695 > &#62; &gt;
1696 & &#38; &amp;
1697 " &#34; &quot;
1698 ' &#39; &apos;
1699 Children:
1700 * text and inline elements 0+
1701
1702 Attributes:
1703 * core attributes 0
1704 * internationalization attributes 0
1705
17065.5.21. <block-quote> Tag
1707 A block quote is a large quotation that MAY span several statements.
1708 This element can contain text and any number of inline elements.
1709 Children:
1710 * text and inline elements 0+
1711
1712 Attributes:
1713 * core attributes 0
1714 * internationalization attributes 0
1715
17165.5.22. <citation> Tag
1717 A citation is a descriptive reference to a piece of information used
1718 in content by a session author. The information referenced by the
1719 <citation> tag automatically points to the content that requires it
1720 by use of a REQUIRED id attribute, which is referred to by the inline
1721 tag <cite>. See section 5.5.29 <cite> Tag. This element contains
1722 text and any number of inline elements.
1723 Children:
1724 *text and inline elements 0+
1725
1726 Attributes:
1727 * id
1728 * title 0
1729 * style 0
1730 * role 0
1731 * internationalization attributes 0
1732
1733
1734
1735
1736Cheney Standards Track [Page 31]
1737
1738Internet-Draft Mail Markup Language - Version 1.0 April 2009
1739
17405.5.23. <heading> Tag
1741 A heading is a short block of text that describes the content that is
1742 to follow. The <heading> tag MUST contain text and MAY contain 0 or
1743 more inline elements.
1744 Children:
1745 * text and inline elements 0+
1746
1747 Attributes:
1748 * core attributes 0
1749 * internationalization attributes 0
1750
17515.5.24. <object> Tag
1752 An object is any external resource that is intended to be processed
1753 among the content of the message body, such as an image or video.
1754 Objects have two REQUIRED child tags and are intended to contain text
1755 content.
1756
1757 It is important that an object contain text content that describes
1758 its resource. There is no requirement for MML processors to process
1759 any external resource. If the resource does fail to process the text
1760 contained by the object MUST display.
1761 Children:
1762 * <object-text>
1763 * <object-uri>
1764 * <object-type>
1765 * inline elements 0+
1766
1767 Attributes:
1768 * core attributes
1769 * internationalization attributes
1770
17715.5.25. <object-text> Tag
1772 Object text is the alternative text content that is to be rendered as
1773 content if the object cannot be resolved or processed.
1774
17755.5.26. <object-uri> Tag
1776 This element MUST only contain a URI value and that URI MUST point to
1777 the location of a resource to appear in the message body. This
1778 element allows no child elements or attributes.
1779
17805.5.27. <object-type> Tag
1781 This element is of type "mime-type". The object pointed to by the
1782 sibling <object-uri> tag MUST be processed only according to the type
1783 specified by this tag.
1784
17855.5.28. <paragraph> Tag
1786 This element is the standard generic container of text and inline
1787 elements in a MML document. This element represents a paragraph and
1788 text is most typically grouped in paragraphs.
1789 Children:
1790 * text and inline elements 0+
1791
1792Cheney Standards Track [Page 32]
1793
1794Internet-Draft Mail Markup Language - Version 1.0 April 2009
1795
1796 Attributes:
1797 * core attributes 0
1798 * internationalization attributes 0
1799
18005.5.29. <separator> Tag
1801 This element is intended for semantic and structural purposes only.
1802 Use of this element indicates a structural obstruction in the flow or
1803 organization of content within a single section. This element MAY
1804 contain text, which would indicate or explain the nature or reasoning
1805 of separation mandated by use of this element.
1806 Children:
1807 * text and inline elements 0+
1808
1809 Attributes:
1810 * core attributes 0
1811 * internationalization attributes 0
1812
18135.5.30. <short> Tag
1814 This inline element describes text that is a short-hand value, such
1815 as an abbreviation or acronym.
1816 Attributes:
1817 * long-form
1818 * core attributes plus uri 0
1819
18205.5.31. <button> Tag
1821 This element exists to encourage interaction from a user. This version
1822 of MML does not allow for client-side scripting, limiting the potential
1823 of a button, although a button MAY be able to interact with media that
1824 performs its own internal scripting, such as Flash media.
1825 Attributes:
1826 * refer 0
1827 * core attributes plus uri 0
1828
18295.5.32. <cite> Tag
1830 The <cite> tag is intended to contain text begging a citation. The
1831 refer attribute is REQUIRED as it MUST point to the id attribute of a
1832 <citation> in the same <markup> section of the document.
1833 Attributes:
1834 * refer
1835 * core attributes 0
1836
18375.5.33. <emphasis> Tag
1838 This tag indicates the text it contains is more important than other
1839 text of the same context.
1840 Attributes:
1841 * core attributes plus uri 0
1842
1843
1844
1845
1846
1847
1848Cheney Standards Track [Page 33]
1849
1850Internet-Draft Mail Markup Language - Version 1.0 April 2009
1851
18525.5.34. <identifier> Tag
1853 This element is intended to provide a text label that describes some
1854 other element. This element has a REQUIRED attribute of refer so
1855 that it may refer to the id of the element it is attempting to
1856 describe.
1857
1858 Attributes:
1859 * refer
1860 * core attributes plus uri 0
1861
18625.5.35. <quote> Tag
1863 This element indicates the content it contains is a quotation.
1864 Attributes:
1865 * core attributes plus uri 0
1866
18675.5.36. <format> Tag
1868 The format tag is a special tag. This is the only tag in the entire
1869 MML tag set that is deliberately intended to provide no semantic
1870 data. This tag is available to provide access to the core attributes
1871 without imposing semantic considerations. A session author MAY need
1872 to apply style or a uri attribute to some text that is otherwise no
1873 different than the text around it. This is also the only inline tag
1874 that MAY contain a child tag.
1875 Child:
1876 * <format> 0+
1877
1878 Attributes:
1879 * core attributes plus uri 0
1880
18815.5.37. <strong> Tag
1882 This tag indicates the content it contains is begging attention
1883 regardless of the importantce or relevance of the content in its
1884 given context.
1885 Attributes:
1886 * core attributes plus uri 0
1887
18885.5.38. <title> Tag
1889 This element indicates either a person's official title or the title
1890 of a work.
1891 Attributes:
1892 * core attributes plus uri 0
1893
18946. Protocol Compatibility
1895 It is important to determine if there is any interference to existing
1896 communication protocols imposed by the formal structuring of data.
1897 This section intends to determine if there are any incompatibilities
1898 with existing protocol standards and not whether existing services
1899 fail. It is anticipated there will likely be natural
1900 incompatibilities with existing technology that MAY perform
1901 sophisticated processing and relay of data across a network without
1902 expectation to uniformity to the definitions imposed upon that data.
1903
1904Cheney Standards Track [Page 34]
1905
1906Internet-Draft Mail Markup Language - Version 1.0 April 2009
1907
1908 Application oriented concerns not defined by this specification,
1909 especially vender-specific concerns, exceed the scope of this
1910 specification. If the standard imposed by this specification is not
1911 incompatible with existing standards it will be necessary for
1912 software vendors to modify their applications to ensure support of
1913 this technology without service interference.
1914
1915 This section will explore considerations for the gathering of data
1916 from a MML document necessary to conduct transportation of the
1917 document. This section is subdivided by mail distribution protocol.
1918
19196.1. Simple Mail Transfer Protocol (SMTP)
1920 SMTP [RFC5321] is the backbone protocol of email distribution. This
1921 protocol is responsible for sending all email and often for receiving
1922 mail. In order to be compatible to the requirements of RFC 5321
1923 (SMTP) RFC 5322 (Format) MUST be obsolete by this document. This
1924 specification seeks to replace RFC 5322 as the standard method for
1925 describing data in email.
1926
1927 RFC 5321 sets specific methods and requirements for the use of header
1928 fields from a mail document for use in defining transport and
1929 response necessary information. There is no guidance specified for
1930 precise movement of header information from a document to protocol
1931 use under any particular circumstances. The result is that MML
1932 processors MUST extract header information from the concerned header
1933 tags in a way that it deems most efficient and convenient to its
1934 logic so long as transport can be achieved in accordance with RFC
1935 5321 and without harm to the document. Please see section 3. The
1936 SMTP Procedures: An Overview and Appendix B. Generating SMTP Commands
1937 from RFC 822 Headers from RFC 5321 for specific details.
1938
19396.2. Post Office Protocol - Version 3 (POP3)
1940 POP3 [RFC1939] is incompatible with this specification due its
1941 section 11. Message Format. In order to be compatible with the
1942 protocol of higher priority, SMTP, as a standards specification
1943 RFC 5322 is obsolete by this document. POP3 is therefore
1944 incompatible by direct result of the following statement:
1945
1946 "All messages transmitted during a POP3 session are assumed to
1947 conform to the standard for the format of Internet text messages
1948 [RFC822]."
1949 It is important to note that RFC 822 is obsolete by RFC 5322.
1950
1951 The result is that RFC 1939 MUST be obsolete. If POP is to remain a
1952 standard it MUST be revised to either expect header information in
1953 MML specific format or be format non-specific.
1954
19556.3. Internet Message Access Protocol - Version 4rev1 (IMAP)
1956 IMAP [RFC3501] is inherently dependant on formatting specified by RFC
1957 5322, and so it MUST be rendered obsolete as a result.
1958
1959
1960Cheney Standards Track [Page 35]
1961
1962Internet-Draft Mail Markup Language - Version 1.0 April 2009
1963
19646.4. Requirements for Web Mail
1965 At this time of this writing Web Mail is inherently dependant upon
1966 POP3 and/or IMAP protocols. Since these protocols are rendered
1967 obsolete by this specification it can be assumed that MML is
1968 incompatible with web mail as it exists during the time of this
1969 writing.
1970
1971 In order for MML to be compatible with web mail the following
1972 conditions, beyond protocol compatibility, MUST be enforced:
1973
1974 * The containing document, such as a page of Extensible Hypertext
1975 Markup Language ((X)HTML), MUST be served, processed, and rendered
1976 as a subset of XML.
1977
1978 * The MML processor specific requirements specified in section 4.
1979 Processor Roles are REQUIRED.
1980
1981 * Components of the containing document, such as a page of
1982 (X)HTML, MUST NOT mix or interfere with the MML code. MML, and
1983 its subsets; if any, MUST exist as a preserved code island.
1984
1985 * MML MUST be sent without interference or supplication to its
1986 code or structure from its containing document, as a page of
1987 (X)HTML.
1988
1989 * Scripting that exists or is allowed by a containing document,
1990 such as a page of (X)HTML, MUST NOT be allowed to execute against
1991 the code, content, or structure imposed by the MML code island.
1992
1993 * MML presentation requirements MUST be enforced. Presentation
1994 from the containing document, such as a page of (X)HTML, MUST NOT
1995 act upon or interfere with presentation imposed by MML referenced
1996 stylesheets. The containing page MAY establish lowest priority
1997 default presentation exactly as a MML processor might.
1998
1999 * The containing document MUST be served only to the authorized
2000 user through an encrypted transmission.
2001
2002 * An XML compliant web browser SHOULD be capable of processing,
2003 presenting, and transmitting a MML document without any need for a
2004 containing document or any use of HTML or reformulation thereof.
2005
20067. Default mime.xsd
2007<?xml version="1.0" encoding="utf-8" ?>
2008<xs:schema elementFormDefault="qualified"
2009xmlns:xs="http://www.w3.org/2001/XMLSchema">
2010 <xs:simpleType name="application-type">
2011 <xs:restriction base="xs:token">
2012 <xs:enumeration value="activemessage" />872<?xml version="1.0" encoding="utf-8" ?>
2013 <xs:enumeration value="andrew-inset" />873<xs:schema elementFormDefault="qualified"
2014 <xs:enumeration value="applefile" />874xmlns:xs="http://www.w3.org/2001/XMLSchema">
2015875 <xs:simpleType name="application-type">
2016Cheney Standards Track [Page 36]876 <xs:restriction base="xs:token">
2017877 <xs:enumeration value="activemessage" />
2018Internet-Draft Mail Markup Language - Version 1.0 April 2009878 <xs:enumeration value="andrew-inset" />
2019879 <xs:enumeration value="applefile" />
2020 <xs:enumeration value="atom+xml" />880 <xs:enumeration value="atom+xml" />
2021 <xs:enumeration value="atomicmail" />881 <xs:enumeration value="atomicmail" />
2022 <xs:enumeration value="atomcat+xml" />882 <xs:enumeration value="atomcat+xml" />
2023 <xs:enumeration value="atomsvc+xml" />883 <xs:enumeration value="atomsvc+xml" />
2024 <xs:enumeration value="auth-policy+xml" />884 <xs:enumeration value="auth-policy+xml" />
2025 <xs:enumeration value="batch-SMTP" />885 <xs:enumeration value="batch-SMTP" />
2026 <xs:enumeration value="beep+xml" />886 <xs:enumeration value="beep+xml" />
2027 <xs:enumeration value="cals-1840" />887 <xs:enumeration value="cals-1840" />
2028 <xs:enumeration value="ccxml+xml" />888 <xs:enumeration value="ccxml+xml" />
2029 <xs:enumeration value="cellml+xml" />889 <xs:enumeration value="cellml+xml" />
2030 <xs:enumeration value="cnrp+xml" />890 <xs:enumeration value="cnrp+xml" />
2031 <xs:enumeration value="commonground" />891 <xs:enumeration value="commonground" />
2032 <xs:enumeration value="conference-info+xml" />892 <xs:enumeration value="conference-info+xml" />
2033 <xs:enumeration value="cpl+xml" />893 <xs:enumeration value="cpl+xml" />
2034 <xs:enumeration value="csta+xml" />894 <xs:enumeration value="csta+xml" />
2035 <xs:enumeration value="CSTAdata+xml" />895
2036 <xs:enumeration value="cybercash" /> 896Cheney Standards Track [Page 16]
2037 <xs:enumeration value="davmount+xml" />897
2038 <xs:enumeration value="dca-rft" /> 898Internet-Draft Mail Markup Language - Version 1.0 February 2009
2039 <xs:enumeration value="dec-dx" />899
2040 <xs:enumeration value="dialog-info+xml" />900 <xs:enumeration value="CSTAdata+xml" />
2041 <xs:enumeration value="dicom" />901 <xs:enumeration value="cybercash" />
2042 <xs:enumeration value="dns" />902 <xs:enumeration value="davmount+xml" />
2043 <xs:enumeration value="dvcs" />903 <xs:enumeration value="dca-rft" />
2044 <xs:enumeration value="ecmascript" />904 <xs:enumeration value="dec-dx" />
2045 <xs:enumeration value="EDI-Consent" />905 <xs:enumeration value="dialog-info+xml" />
2046 <xs:enumeration value="EDIFACT" />906 <xs:enumeration value="dicom" />
2047 <xs:enumeration value="EDI-X12" />907 <xs:enumeration value="dns" />
2048 <xs:enumeration value="epp+xml" />908 <xs:enumeration value="dvcs" />
2049 <xs:enumeration value="eshop" />909 <xs:enumeration value="ecmascript" />
2050 <xs:enumeration value="example" />910 <xs:enumeration value="EDI-Consent" />
2051 <xs:enumeration value="fastinfoset" />911 <xs:enumeration value="EDIFACT" />
2052 <xs:enumeration value="fastsoap" />912 <xs:enumeration value="EDI-X12" />
2053 <xs:enumeration value="fits" />913 <xs:enumeration value="epp+xml" />
2054 <xs:enumeration value="font-tdpfr" />914 <xs:enumeration value="eshop" />
2055 <xs:enumeration value="H224" />915 <xs:enumeration value="example" />
2056 <xs:enumeration value="http" />916 <xs:enumeration value="fastinfoset" />
2057 <xs:enumeration value="hyperstudio" />917 <xs:enumeration value="fastsoap" />
2058 <xs:enumeration value="iges" />918 <xs:enumeration value="fits" />
2059 <xs:enumeration value="im-iscomposing+xml" />919 <xs:enumeration value="font-tdpfr" />
2060 <xs:enumeration value="index" />920 <xs:enumeration value="H224" />
2061 <xs:enumeration value="index.cmd" />921 <xs:enumeration value="http" />
2062 <xs:enumeration value="index.obj" />922 <xs:enumeration value="hyperstudio" />
2063 <xs:enumeration value="index.response" />923 <xs:enumeration value="iges" />
2064 <xs:enumeration value="index.vnd" />924 <xs:enumeration value="im-iscomposing+xml" />
2065 <xs:enumeration value="iotp" />925 <xs:enumeration value="index" />
2066 <xs:enumeration value="ipp" />926 <xs:enumeration value="index.cmd" />
2067 <xs:enumeration value="isup" />927 <xs:enumeration value="index.obj" />
2068 <xs:enumeration value="javascript" />928 <xs:enumeration value="index.response" />
2069 <xs:enumeration value="json" />929 <xs:enumeration value="index.vnd" />
2070 <xs:enumeration value="kpml-request+xml" />930 <xs:enumeration value="iotp" />
2071931 <xs:enumeration value="ipp" />
2072Cheney Standards Track [Page 37]932 <xs:enumeration value="isup" />
2073933 <xs:enumeration value="javascript" />
2074Internet-Draft Mail Markup Language - Version 1.0 April 2009934 <xs:enumeration value="json" />
2075935 <xs:enumeration value="kpml-request+xml" />
2076 <xs:enumeration value="kpml-response+xml" />936 <xs:enumeration value="kpml-response+xml" />
2077 <xs:enumeration value="lost+xml" />937 <xs:enumeration value="lost+xml" />
2078 <xs:enumeration value="mac-binhex40" />938 <xs:enumeration value="mac-binhex40" />
2079 <xs:enumeration value="macwriteii" />939 <xs:enumeration value="macwriteii" />
2080 <xs:enumeration value="marc" />940 <xs:enumeration value="marc" />
2081 <xs:enumeration value="mathematica" />941 <xs:enumeration value="mathematica" />
2082 <xs:enumeration942 <xs:enumeration
2083 value="mbms-associated-procedure-description+xml" />943 value="mbms-associated-procedure-description+xml" />
2084 <xs:enumeration value="mbms-deregister+xml" />944 <xs:enumeration value="mbms-deregister+xml" />
2085 <xs:enumeration value="mbms-envelope+xml" />945 <xs:enumeration value="mbms-envelope+xml" />
2086 <xs:enumeration value="mbms-msk-response+xml" />946 <xs:enumeration value="mbms-msk-response+xml" />
2087 <xs:enumeration value="mbms-msk+xml" />947 <xs:enumeration value="mbms-msk+xml" />
2088 <xs:enumeration value="mbms-protection-description+xml" />948 <xs:enumeration value="mbms-protection-description+xml" />
2089 <xs:enumeration value="mbms-reception-report+xml" />949 <xs:enumeration value="mbms-reception-report+xml" />
2090 <xs:enumeration value="mbms-register-response+xml" />950 <xs:enumeration value="mbms-register-response+xml" />
2091 <xs:enumeration value="mbms-register+xml" />951
2092 <xs:enumeration value="mbms-user-service-description+xml" /> 952Cheney Standards Track [Page 17]
2093 <xs:enumeration value="mbox" />953
2094 <xs:enumeration value="media_control+xml" /> 954Internet-Draft Mail Markup Language - Version 1.0 February 2009
2095 <xs:enumeration value="mediaservercontrol+xml" />955
2096 <xs:enumeration value="mikey" />956 <xs:enumeration value="mbms-register+xml" />
2097 <xs:enumeration value="moss-keys" />957 <xs:enumeration value="mbms-user-service-description+xml" />
2098 <xs:enumeration value="moss-signature" />958 <xs:enumeration value="mbox" />
2099 <xs:enumeration value="mosskey-data" />959 <xs:enumeration value="media_control+xml" />
2100 <xs:enumeration value="mosskey-request" />960 <xs:enumeration value="mediaservercontrol+xml" />
2101 <xs:enumeration value="mpeg4-generic" />961 <xs:enumeration value="mikey" />
2102 <xs:enumeration value="mpeg4-iod" />962 <xs:enumeration value="moss-keys" />
2103 <xs:enumeration value="mpeg4-iod-xmt" />963 <xs:enumeration value="moss-signature" />
2104 <xs:enumeration value="mp4" />964 <xs:enumeration value="mosskey-data" />
2105 <xs:enumeration value="msword" />965 <xs:enumeration value="mosskey-request" />
2106 <xs:enumeration value="mxf" />966 <xs:enumeration value="mpeg4-generic" />
2107 <xs:enumeration value="nasdata" />967 <xs:enumeration value="mpeg4-iod" />
2108 <xs:enumeration value="news-transmission" />968 <xs:enumeration value="mpeg4-iod-xmt" />
2109 <xs:enumeration value="nss" />969 <xs:enumeration value="mp4" />
2110 <xs:enumeration value="ocsp-request" />970 <xs:enumeration value="msword" />
2111 <xs:enumeration value="ocsp-response" />971 <xs:enumeration value="mxf" />
2112 <xs:enumeration value="octet-stream" />972 <xs:enumeration value="nasdata" />
2113 <xs:enumeration value="oda" />973 <xs:enumeration value="news-transmission" />
2114 <xs:enumeration value="oebps-package+xml" />974 <xs:enumeration value="nss" />
2115 <xs:enumeration value="ogg" />975 <xs:enumeration value="ocsp-request" />
2116 <xs:enumeration value="parityfec" />976 <xs:enumeration value="ocsp-response" />
2117 <xs:enumeration value="patch-ops-error+xml" />977 <xs:enumeration value="octet-stream" />
2118 <xs:enumeration value="pdf" />978 <xs:enumeration value="oda" />
2119 <xs:enumeration value="pgp-encrypted" />979 <xs:enumeration value="oebps-package+xml" />
2120 <xs:enumeration value="pgp-keys" />980 <xs:enumeration value="ogg" />
2121 <xs:enumeration value="pgp-signature" />981 <xs:enumeration value="parityfec" />
2122 <xs:enumeration value="pidf+xml" />982 <xs:enumeration value="patch-ops-error+xml" />
2123 <xs:enumeration value="pidf-diff+xml" />983 <xs:enumeration value="pdf" />
2124 <xs:enumeration value="pkcs10" />984 <xs:enumeration value="pgp-encrypted" />
2125 <xs:enumeration value="pkcs7-mime" />985 <xs:enumeration value="pgp-keys" />
2126 <xs:enumeration value="pkcs7-signature" />986 <xs:enumeration value="pgp-signature" />
2127987 <xs:enumeration value="pidf+xml" />
2128Cheney Standards Track [Page 38]988 <xs:enumeration value="pidf-diff+xml" />
2129989 <xs:enumeration value="pkcs10" />
2130Internet-Draft Mail Markup Language - Version 1.0 April 2009990 <xs:enumeration value="pkcs7-mime" />
2131991 <xs:enumeration value="pkcs7-signature" />
2132 <xs:enumeration value="pkix-cert" />992 <xs:enumeration value="pkix-cert" />
2133 <xs:enumeration value="pkixcmp" />993 <xs:enumeration value="pkixcmp" />
2134 <xs:enumeration value="pkix-crl" />994 <xs:enumeration value="pkix-crl" />
2135 <xs:enumeration value="pkix-pkipath" />995 <xs:enumeration value="pkix-pkipath" />
2136 <xs:enumeration value="pls+xml" />996 <xs:enumeration value="pls+xml" />
2137 <xs:enumeration value="poc-settings+xml" />997 <xs:enumeration value="poc-settings+xml" />
2138 <xs:enumeration value="postscript" />998 <xs:enumeration value="postscript" />
2139 <xs:enumeration value="prs.alvestrand.titrax-sheet" />999 <xs:enumeration value="prs.alvestrand.titrax-sheet" />
2140 <xs:enumeration value="prs.cww" />1000 <xs:enumeration value="prs.cww" />
2141 <xs:enumeration value="prs.nprend" />1001 <xs:enumeration value="prs.nprend" />
2142 <xs:enumeration value="prs.plucker" />1002 <xs:enumeration value="prs.plucker" />
2143 <xs:enumeration value="qsig" />1003 <xs:enumeration value="qsig" />
2144 <xs:enumeration value="rdf+xml" />1004 <xs:enumeration value="rdf+xml" />
2145 <xs:enumeration value="reginfo+xml" />1005 <xs:enumeration value="reginfo+xml" />
2146 <xs:enumeration value="relax-ng-compact-syntax" />1006 <xs:enumeration value="relax-ng-compact-syntax" />
2147 <xs:enumeration value="remote-printing" />1007
2148 <xs:enumeration value="resource-lists+xml" /> 1008Cheney Standards Track [Page 18]
2149 <xs:enumeration value="riscos" />1009
2150 <xs:enumeration value="rlmi+xml" /> 1010Internet-Draft Mail Markup Language - Version 1.0 February 2009
2151 <xs:enumeration value="rls-services+xml" />1011
2152 <xs:enumeration value="rtf" />1012 <xs:enumeration value="remote-printing" />
2153 <xs:enumeration value="rtx" />1013 <xs:enumeration value="resource-lists+xml" />
2154 <xs:enumeration value="samlassertion+xml" />1014 <xs:enumeration value="riscos" />
2155 <xs:enumeration value="samlmetadata+xml" />1015 <xs:enumeration value="rlmi+xml" />
2156 <xs:enumeration value="sbml+xml" />1016 <xs:enumeration value="rls-services+xml" />
2157 <xs:enumeration value="scvp-cv-request" />1017 <xs:enumeration value="rtf" />
2158 <xs:enumeration value="scvp-cv-response" />1018 <xs:enumeration value="rtx" />
2159 <xs:enumeration value="scvp-vp-request" />1019 <xs:enumeration value="samlassertion+xml" />
2160 <xs:enumeration value="scvp-vp-response" />1020 <xs:enumeration value="samlmetadata+xml" />
2161 <xs:enumeration value="sdp" />1021 <xs:enumeration value="sbml+xml" />
2162 <xs:enumeration value="set-payment" />1022 <xs:enumeration value="scvp-cv-request" />
2163 <xs:enumeration value="set-payment-initiation" />1023 <xs:enumeration value="scvp-cv-response" />
2164 <xs:enumeration value="set-registration" />1024 <xs:enumeration value="scvp-vp-request" />
2165 <xs:enumeration value="set-registration-initiation" />1025 <xs:enumeration value="scvp-vp-response" />
2166 <xs:enumeration value="sgml" />1026 <xs:enumeration value="sdp" />
2167 <xs:enumeration value="sgml-open-catalog" />1027 <xs:enumeration value="set-payment" />
2168 <xs:enumeration value="shf+xml" />1028 <xs:enumeration value="set-payment-initiation" />
2169 <xs:enumeration value="sieve" />1029 <xs:enumeration value="set-registration" />
2170 <xs:enumeration value="simple-filter+xml" />1030 <xs:enumeration value="set-registration-initiation" />
2171 <xs:enumeration value="simple-message-summary" />1031 <xs:enumeration value="sgml" />
2172 <xs:enumeration value="simpleSymbolContainer" />1032 <xs:enumeration value="sgml-open-catalog" />
2173 <xs:enumeration value="slate" />1033 <xs:enumeration value="shf+xml" />
2174 <xs:enumeration value="smil+xml" />1034 <xs:enumeration value="sieve" />
2175 <xs:enumeration value="soap+fastinfoset" />1035 <xs:enumeration value="simple-filter+xml" />
2176 <xs:enumeration value="soap+xml" />1036 <xs:enumeration value="simple-message-summary" />
2177 <xs:enumeration value="sparql-query" />1037 <xs:enumeration value="simpleSymbolContainer" />
2178 <xs:enumeration value="sparql-results+xml" />1038 <xs:enumeration value="slate" />
2179 <xs:enumeration value="spirits-event+xml" />1039 <xs:enumeration value="smil+xml" />
2180 <xs:enumeration value="srgs" />1040 <xs:enumeration value="soap+fastinfoset" />
2181 <xs:enumeration value="srgs+xml" />1041 <xs:enumeration value="soap+xml" />
2182 <xs:enumeration value="ssml+xml" />1042 <xs:enumeration value="sparql-query" />
21831043 <xs:enumeration value="sparql-results+xml" />
2184Cheney Standards Track [Page 39]1044 <xs:enumeration value="spirits-event+xml" />
21851045 <xs:enumeration value="srgs" />
2186Internet-Draft Mail Markup Language - Version 1.0 April 20091046 <xs:enumeration value="srgs+xml" />
21871047 <xs:enumeration value="ssml+xml" />
2188 <xs:enumeration value="timestamp-query" />1048 <xs:enumeration value="timestamp-query" />
2189 <xs:enumeration value="timestamp-reply" />1049 <xs:enumeration value="timestamp-reply" />
2190 <xs:enumeration value="tve-trigger" />1050 <xs:enumeration value="tve-trigger" />
2191 <xs:enumeration value="ulpfec" />1051 <xs:enumeration value="ulpfec" />
2192 <xs:enumeration value="vemmi" />1052 <xs:enumeration value="vemmi" />
2193 <xs:enumeration value="vnd.3gpp.bsf+xml" />1053 <xs:enumeration value="vnd.3gpp.bsf+xml" />
2194 <xs:enumeration value="vnd.3gp.pic-bw-large" />1054 <xs:enumeration value="vnd.3gp.pic-bw-large" />
2195 <xs:enumeration value="vnd.3gp.pic-bw-small" />1055 <xs:enumeration value="vnd.3gp.pic-bw-small" />
2196 <xs:enumeration value="vnd.3gp.pic-bw-var" />1056 <xs:enumeration value="vnd.3gp.pic-bw-var" />
2197 <xs:enumeration value="vnd.3gp.sms" />1057 <xs:enumeration value="vnd.3gp.sms" />
2198 <xs:enumeration value="vnd.3gp2.bcmcsinfo+xml" />1058 <xs:enumeration value="vnd.3gp2.bcmcsinfo+xml" />
2199 <xs:enumeration value="vnd.3gp2.sms" />1059 <xs:enumeration value="vnd.3gp2.sms" />
2200 <xs:enumeration value="vnd.3gp2.tcap" />1060 <xs:enumeration value="vnd.3gp2.tcap" />
2201 <xs:enumeration value="vnd.3M.Post-in-Notes" />1061 <xs:enumeration value="vnd.3M.Post-in-Notes" />
2202 <xs:enumeration value="vnd.accpac.simply.aso" />1062 <xs:enumeration value="vnd.accpac.simply.aso" />
2203 <xs:enumeration value="vnd.accpac.simply.imp" />1063
2204 <xs:enumeration value="vnd.acucobol" /> 1064Cheney Standards Track [Page 19]
2205 <xs:enumeration value="vnd.acucorp" />1065
2206 <xs:enumeration value="vnd.adobe.xdp+xml" /> 1066Internet-Draft Mail Markup Language - Version 1.0 February 2009
2207 <xs:enumeration value="vnd.adobe.xfdf" />1067
2208 <xs:enumeration value="vnd.aether.imp" />1068 <xs:enumeration value="vnd.accpac.simply.imp" />
2209 <xs:enumeration value="vnd.americandynamics.acc" />1069 <xs:enumeration value="vnd.acucobol" />
2210 <xs:enumeration value="vnd.amiga.ami" />1070 <xs:enumeration value="vnd.acucorp" />
2211 <xs:enumeration1071 <xs:enumeration value="vnd.adobe.xdp+xml" />
2212 value="vnd.anser-web-certificate-issue-initiation" />1072 <xs:enumeration value="vnd.adobe.xfdf" />
2213 <xs:enumeration value="vnd.antix.game-component" />1073 <xs:enumeration value="vnd.aether.imp" />
2214 <xs:enumeration value="vnd.apple.installer+xml" />1074 <xs:enumeration value="vnd.americandynamics.acc" />
2215 <xs:enumeration value="vnd.arastra.swi" />1075 <xs:enumeration value="vnd.amiga.ami" />
2216 <xs:enumeration value="vnd.audiograph" />1076 <xs:enumeration
2217 <xs:enumeration value="vnd.autopackage" />1077 value="vnd.anser-web-certificate-issue-initiation" />
2218 <xs:enumeration value="vnd.avistar+xml" />1078 <xs:enumeration value="vnd.antix.game-component" />
2219 <xs:enumeration value="vnd.blueice.multipass" />1079 <xs:enumeration value="vnd.apple.installer+xml" />
2220 <xs:enumeration value="vnd.bmi" />1080 <xs:enumeration value="vnd.arastra.swi" />
2221 <xs:enumeration value="vnd.businessobjects" />1081 <xs:enumeration value="vnd.audiograph" />
2222 <xs:enumeration value="vnd.cab-jscript" />1082 <xs:enumeration value="vnd.autopackage" />
2223 <xs:enumeration value="vnd.canon-cpdl" />1083 <xs:enumeration value="vnd.avistar+xml" />
2224 <xs:enumeration value="vnd.canon-lips" />1084 <xs:enumeration value="vnd.blueice.multipass" />
2225 <xs:enumeration value="vnd.cendio.thinlinc.clientconf" / 1085 <xs:enumeration value="vnd.bmi" />
2226 <xs:enumeration value="vnd.chemdraw+xml" />1086 <xs:enumeration value="vnd.businessobjects" />
2227 <xs:enumeration value="vnd.chipnuts.karaoke-mmd" />1087 <xs:enumeration value="vnd.cab-jscript" />
2228 <xs:enumeration value="vnd.cinderella" />1088 <xs:enumeration value="vnd.canon-cpdl" />
2229 <xs:enumeration value="vnd.cirpack.isdn-ext" />1089 <xs:enumeration value="vnd.canon-lips" />
2230 <xs:enumeration value="vnd.claymore" />1090 <xs:enumeration value="vnd.cendio.thinlinc.clientconf" /
2231 <xs:enumeration value="vnd.clonk.c4group" />1091 <xs:enumeration value="vnd.chemdraw+xml" />
2232 <xs:enumeration value="vnd.commerce-battelle" />1092 <xs:enumeration value="vnd.chipnuts.karaoke-mmd" />
2233 <xs:enumeration value="vnd.comonspace" />1093 <xs:enumeration value="vnd.cinderella" />
2234 <xs:enumeration value="vnd.cosmocaller" />1094 <xs:enumeration value="vnd.cirpack.isdn-ext" />
2235 <xs:enumeration value="vnd.contact.cmsg" />1095 <xs:enumeration value="vnd.claymore" />
2236 <xs:enumeration value="vnd.crick.clicker" />1096 <xs:enumeration value="vnd.clonk.c4group" />
2237 <xs:enumeration value="vnd.crick.clicker.keyboard" />1097 <xs:enumeration value="vnd.commerce-battelle" />
2238 <xs:enumeration value="vnd.crick.clicker.palette" />1098 <xs:enumeration value="vnd.comonspace" />
22391099 <xs:enumeration value="vnd.cosmocaller" />
2240Cheney Standards Track [Page 40]1100 <xs:enumeration value="vnd.contact.cmsg" />
22411101 <xs:enumeration value="vnd.crick.clicker" />
2242Internet-Draft Mail Markup Language - Version 1.0 April 20091102 <xs:enumeration value="vnd.crick.clicker.keyboard" />
22431103 <xs:enumeration value="vnd.crick.clicker.palette" />
2244 <xs:enumeration value="vnd.crick.clicker.template" />1104 <xs:enumeration value="vnd.crick.clicker.template" />
2245 <xs:enumeration value="vnd.crick.clicker.wordbank" />1105 <xs:enumeration value="vnd.crick.clicker.wordbank" />
2246 <xs:enumeration value="vnd.criticaltools.wbs+xml" />1106 <xs:enumeration value="vnd.criticaltools.wbs+xml" />
2247 <xs:enumeration value="vnd.ctc-posml" />1107 <xs:enumeration value="vnd.ctc-posml" />
2248 <xs:enumeration value="vnd.ctct.ws+xml" />1108 <xs:enumeration value="vnd.ctct.ws+xml" />
2249 <xs:enumeration value="vnd.cups-pdf" />1109 <xs:enumeration value="vnd.cups-pdf" />
2250 <xs:enumeration value="vnd.cups-postscript" />1110 <xs:enumeration value="vnd.cups-postscript" />
2251 <xs:enumeration value="vnd.cups-ppd" />1111 <xs:enumeration value="vnd.cups-ppd" />
2252 <xs:enumeration value="vnd.cups-raster" />1112 <xs:enumeration value="vnd.cups-raster" />
2253 <xs:enumeration value="vnd.cups-raw" />1113 <xs:enumeration value="vnd.cups-raw" />
2254 <xs:enumeration value="vnd.curl" />1114 <xs:enumeration value="vnd.curl" />
2255 <xs:enumeration value="vnd.cybank" />1115 <xs:enumeration value="vnd.cybank" />
2256 <xs:enumeration value="vnd.data-vision.rdf" />1116 <xs:enumeration value="vnd.data-vision.rdf" />
2257 <xs:enumeration value="vnd.denovo.fcselayout-link" />1117 <xs:enumeration value="vnd.denovo.fcselayout-link" />
2258 <xs:enumeration value="vnd.dna" />1118 <xs:enumeration value="vnd.dna" />
2259 <xs:enumeration value="vnd.dpgraph" />1119
2260 <xs:enumeration value="vnd.dreamfactory" /> 1120Cheney Standards Track [Page 20]
2261 <xs:enumeration value="vnd.dvb.esgcontainer" />1121
2262 <xs:enumeration value="vnd.dvb.ipdcesgaccess" /> 1122Internet-Draft Mail Markup Language - Version 1.0 February 2009
2263 <xs:enumeration value="vnd.dvb.iptv.alfec-base" />1123
2264 <xs:enumeration value="vnd.dvb.iptv.alfec-enhancement" />1124 <xs:enumeration value="vnd.dpgraph" />
2265 <xs:enumeration value="vnd.dxr" />1125 <xs:enumeration value="vnd.dreamfactory" />
2266 <xs:enumeration value="vnd.ecdis-update" />1126 <xs:enumeration value="vnd.dvb.esgcontainer" />
2267 <xs:enumeration value="vnd.ecowin.chart" />1127 <xs:enumeration value="vnd.dvb.ipdcesgaccess" />
2268 <xs:enumeration value="vnd.ecowin.filerequest" />1128 <xs:enumeration value="vnd.dvb.iptv.alfec-base" />
2269 <xs:enumeration value="vnd.ecowin.fileupdate" />1129 <xs:enumeration value="vnd.dvb.iptv.alfec-enhancement" />
2270 <xs:enumeration value="vnd.ecowin.series" />1130 <xs:enumeration value="vnd.dxr" />
2271 <xs:enumeration value="vnd.ecowin.seriesrequest" />1131 <xs:enumeration value="vnd.ecdis-update" />
2272 <xs:enumeration value="vnd.ecowin.seriesupdate" />1132 <xs:enumeration value="vnd.ecowin.chart" />
2273 <xs:enumeration value="vnd.enliven" />1133 <xs:enumeration value="vnd.ecowin.filerequest" />
2274 <xs:enumeration value="vnd.epson.esf" />1134 <xs:enumeration value="vnd.ecowin.fileupdate" />
2275 <xs:enumeration value="vnd.epson.msf" />1135 <xs:enumeration value="vnd.ecowin.series" />
2276 <xs:enumeration value="vnd.epson.quickanime" />1136 <xs:enumeration value="vnd.ecowin.seriesrequest" />
2277 <xs:enumeration value="vnd.epson.salt" />1137 <xs:enumeration value="vnd.ecowin.seriesupdate" />
2278 <xs:enumeration value="vnd.epson.ssf" />1138 <xs:enumeration value="vnd.enliven" />
2279 <xs:enumeration value="vnd.ericsson.quickcall" />1139 <xs:enumeration value="vnd.epson.esf" />
2280 <xs:enumeration value="vnd.eszigno3+xml" />1140 <xs:enumeration value="vnd.epson.msf" />
2281 <xs:enumeration value="vnd.eudora.data" />1141 <xs:enumeration value="vnd.epson.quickanime" />
2282 <xs:enumeration value="vnd.ezpix-album" />1142 <xs:enumeration value="vnd.epson.salt" />
2283 <xs:enumeration value="vnd.fdf" />1143 <xs:enumeration value="vnd.epson.ssf" />
2284 <xs:enumeration value="vnd.ffsns" />1144 <xs:enumeration value="vnd.ericsson.quickcall" />
2285 <xs:enumeration value="vnd.fints" />1145 <xs:enumeration value="vnd.eszigno3+xml" />
2286 <xs:enumeration value="vnd.FloGraphIt" />1146 <xs:enumeration value="vnd.eudora.data" />
2287 <xs:enumeration value="vnd.fluxtime.clip" />1147 <xs:enumeration value="vnd.ezpix-album" />
2288 <xs:enumeration value="vnd.font-fontforge-sfd" />1148 <xs:enumeration value="vnd.fdf" />
2289 <xs:enumeration value="vnd.framemaker" />1149 <xs:enumeration value="vnd.ffsns" />
2290 <xs:enumeration value="vnd.frogans.fnc" />1150 <xs:enumeration value="vnd.fints" />
2291 <xs:enumeration value="vnd.frogans.ltf" />1151 <xs:enumeration value="vnd.FloGraphIt" />
2292 <xs:enumeration value="vnd.fsc.weblaunch" />1152 <xs:enumeration value="vnd.fluxtime.clip" />
2293 <xs:enumeration value="vnd.fujitsu.oasys" />1153 <xs:enumeration value="vnd.font-fontforge-sfd" />
2294 <xs:enumeration value="vnd.fujitsu.oasys2" />1154 <xs:enumeration value="vnd.framemaker" />
22951155 <xs:enumeration value="vnd.frogans.fnc" />
2296Cheney Standards Track [Page 41]1156 <xs:enumeration value="vnd.frogans.ltf" />
22971157 <xs:enumeration value="vnd.fsc.weblaunch" />
2298Internet-Draft Mail Markup Language - Version 1.0 April 20091158 <xs:enumeration value="vnd.fujitsu.oasys" />
22991159 <xs:enumeration value="vnd.fujitsu.oasys2" />
2300 <xs:enumeration value="vnd.fujitsu.oasys3" />1160 <xs:enumeration value="vnd.fujitsu.oasys3" />
2301 <xs:enumeration value="vnd.fujitsu.oasysgp" />1161 <xs:enumeration value="vnd.fujitsu.oasysgp" />
2302 <xs:enumeration value="vnd.fujitsu.oasysprs" />1162 <xs:enumeration value="vnd.fujitsu.oasysprs" />
2303 <xs:enumeration value="vnd.fujixerox.ART4" />1163 <xs:enumeration value="vnd.fujixerox.ART4" />
2304 <xs:enumeration value="vnd.fujixerox.ART-EX" />1164 <xs:enumeration value="vnd.fujixerox.ART-EX" />
2305 <xs:enumeration value="vnd.fujixerox.ddd" />1165 <xs:enumeration value="vnd.fujixerox.ddd" />
2306 <xs:enumeration value="vnd.fujixerox.docuworks" />1166 <xs:enumeration value="vnd.fujixerox.docuworks" />
2307 <xs:enumeration value="vnd.fujixerox.docuworks.binder" />1167 <xs:enumeration value="vnd.fujixerox.docuworks.binder" />
2308 <xs:enumeration value="vnd.fujixerox.HBPL" />1168 <xs:enumeration value="vnd.fujixerox.HBPL" />
2309 <xs:enumeration value="vnd.fut-misnet" />1169 <xs:enumeration value="vnd.fut-misnet" />
2310 <xs:enumeration value="vnd.fuzzysheet" />1170 <xs:enumeration value="vnd.fuzzysheet" />
2311 <xs:enumeration value="vnd.genomatix.tuxedo" />1171 <xs:enumeration value="vnd.genomatix.tuxedo" />
2312 <xs:enumeration value="vnd.google-earth.kml+xml" />1172 <xs:enumeration value="vnd.google-earth.kml+xml" />
2313 <xs:enumeration value="vnd.google-earth.kmz" />1173 <xs:enumeration value="vnd.google-earth.kmz" />
2314 <xs:enumeration value="vnd.grafeq" />1174 <xs:enumeration value="vnd.grafeq" />
2315 <xs:enumeration value="vnd.gridmp" />1175
2316 <xs:enumeration value="vnd.groove-account" /> 1176Cheney Standards Track [Page 21]
2317 <xs:enumeration value="vnd.groove-help" />1177
2318 <xs:enumeration value="vnd.groove-identity-message" /> 1178Internet-Draft Mail Markup Language - Version 1.0 February 2009
2319 <xs:enumeration value="vnd.groove-injector" />1179
2320 <xs:enumeration value="vnd.groove-tool-message" />1180 <xs:enumeration value="vnd.gridmp" />
2321 <xs:enumeration value="vnd.groove-tool-template" />1181 <xs:enumeration value="vnd.groove-account" />
2322 <xs:enumeration value="vnd.groove-vcard" />1182 <xs:enumeration value="vnd.groove-help" />
2323 <xs:enumeration value="vnd.HandHeld-Entertainment+xml" />1183 <xs:enumeration value="vnd.groove-identity-message" />
2324 <xs:enumeration value="vnd.hbci" />1184 <xs:enumeration value="vnd.groove-injector" />
2325 <xs:enumeration value="vnd.hcl-bireports" />1185 <xs:enumeration value="vnd.groove-tool-message" />
2326 <xs:enumeration value="vnd.hhe.lesson-player" />1186 <xs:enumeration value="vnd.groove-tool-template" />
2327 <xs:enumeration value="vnd.hp-HPGL" />1187 <xs:enumeration value="vnd.groove-vcard" />
2328 <xs:enumeration value="vnd.hp-hpid" />1188 <xs:enumeration value="vnd.HandHeld-Entertainment+xml" />
2329 <xs:enumeration value="vnd.hp-hps" />1189 <xs:enumeration value="vnd.hbci" />
2330 <xs:enumeration value="vnd.hp-jlyt" />1190 <xs:enumeration value="vnd.hcl-bireports" />
2331 <xs:enumeration value="vnd.hp-PCL" />1191 <xs:enumeration value="vnd.hhe.lesson-player" />
2332 <xs:enumeration value="vnd.hp-PCLXL" />1192 <xs:enumeration value="vnd.hp-HPGL" />
2333 <xs:enumeration value="vnd.httphone" />1193 <xs:enumeration value="vnd.hp-hpid" />
2334 <xs:enumeration value="vnd.hydrostatix.sof-data" />1194 <xs:enumeration value="vnd.hp-hps" />
2335 <xs:enumeration value="vnd.hzn-3d-crossword" />1195 <xs:enumeration value="vnd.hp-jlyt" />
2336 <xs:enumeration value="vnd.ibm.afplinedata" />1196 <xs:enumeration value="vnd.hp-PCL" />
2337 <xs:enumeration value="vnd.ibm.electronic-media" />1197 <xs:enumeration value="vnd.hp-PCLXL" />
2338 <xs:enumeration value="vnd.ibm.MiniPay" />1198 <xs:enumeration value="vnd.httphone" />
2339 <xs:enumeration value="vnd.ibm.modcap" />1199 <xs:enumeration value="vnd.hydrostatix.sof-data" />
2340 <xs:enumeration value="vnd.ibm.rights-management" />1200 <xs:enumeration value="vnd.hzn-3d-crossword" />
2341 <xs:enumeration value="vnd.ibm.secure-container" />1201 <xs:enumeration value="vnd.ibm.afplinedata" />
2342 <xs:enumeration value="vnd.iccprofile" />1202 <xs:enumeration value="vnd.ibm.electronic-media" />
2343 <xs:enumeration value="vnd.igloader" />1203 <xs:enumeration value="vnd.ibm.MiniPay" />
2344 <xs:enumeration value="vnd.immervision-ivp" />1204 <xs:enumeration value="vnd.ibm.modcap" />
2345 <xs:enumeration value="vnd.immervision-ivu" />1205 <xs:enumeration value="vnd.ibm.rights-management" />
2346 <xs:enumeration value="vnd.informedcontrol.rms+xml" />1206 <xs:enumeration value="vnd.ibm.secure-container" />
2347 <xs:enumeration value="vnd.informix-visionary" />1207 <xs:enumeration value="vnd.iccprofile" />
2348 <xs:enumeration value="vnd.intercon.formnet" />1208 <xs:enumeration value="vnd.igloader" />
2349 <xs:enumeration value="vnd.intertrust.digibox" />1209 <xs:enumeration value="vnd.immervision-ivp" />
2350 <xs:enumeration value="vnd.intertrust.nncp" />1210 <xs:enumeration value="vnd.immervision-ivu" />
23511211 <xs:enumeration value="vnd.informedcontrol.rms+xml" />
2352Cheney Standards Track [Page 42]1212 <xs:enumeration value="vnd.informix-visionary" />
23531213 <xs:enumeration value="vnd.intercon.formnet" />
2354Internet-Draft Mail Markup Language - Version 1.0 April 20091214 <xs:enumeration value="vnd.intertrust.digibox" />
23551215 <xs:enumeration value="vnd.intertrust.nncp" />
2356 <xs:enumeration value="vnd.intu.qbo" />1216 <xs:enumeration value="vnd.intu.qbo" />
2357 <xs:enumeration value="vnd.intu.qfx" />1217 <xs:enumeration value="vnd.intu.qfx" />
2358 <xs:enumeration value="vnd.iptc.g2.conceptitem+xml" />1218 <xs:enumeration value="vnd.iptc.g2.conceptitem+xml" />
2359 <xs:enumeration value="vnd.iptc.g2.knowledgeitem+xml" />1219 <xs:enumeration value="vnd.iptc.g2.knowledgeitem+xml" />
2360 <xs:enumeration value="vnd.iptc.g2.newsitem+xml" />1220 <xs:enumeration value="vnd.iptc.g2.newsitem+xml" />
2361 <xs:enumeration value="vnd.iptc.g2.packageitem+xml" />1221 <xs:enumeration value="vnd.iptc.g2.packageitem+xml" />
2362 <xs:enumeration value="vnd.ipunplugged.rcprofile" />1222 <xs:enumeration value="vnd.ipunplugged.rcprofile" />
2363 <xs:enumeration value="vnd.irepository.package+xml" />1223 <xs:enumeration value="vnd.irepository.package+xml" />
2364 <xs:enumeration value="vnd.is-xpr" />1224 <xs:enumeration value="vnd.is-xpr" />
2365 <xs:enumeration value="vnd.jam" />1225 <xs:enumeration value="vnd.jam" />
2366 <xs:enumeration value="vnd.japannet-directory-service" />1226 <xs:enumeration value="vnd.japannet-directory-service" />
2367 <xs:enumeration value="vnd.japannet-ipnstore-wakeup" />1227 <xs:enumeration value="vnd.japannet-ipnstore-wakeup" />
2368 <xs:enumeration value="vnd.japannet-payment-wakeup" />1228 <xs:enumeration value="vnd.japannet-payment-wakeup" />
2369 <xs:enumeration value="vnd.japannet-registration" />1229 <xs:enumeration value="vnd.japannet-registration" />
2370 <xs:enumeration value="vnd.japannet-registration-wakeup" />1230 <xs:enumeration value="vnd.japannet-registration-wakeup" />
2371 <xs:enumeration value="vnd.japannet-setstore-wakeup" />1231
2372 <xs:enumeration value="vnd.japannet-verification" /> 1232Cheney Standards Track [Page 22]
2373 <xs:enumeration value="vnd.japannet-japannet--wakeup" />1233
2374 <xs:enumeration value="vnd.jcp.javame.midlet-rms" /> 1234Internet-Draft Mail Markup Language - Version 1.0 February 2009
2375 <xs:enumeration value="vnd.jisp" />1235
2376 <xs:enumeration value="vnd.joost.joda-archive" />1236 <xs:enumeration value="vnd.japannet-setstore-wakeup" />
2377 <xs:enumeration value="vnd.kahootz" />1237 <xs:enumeration value="vnd.japannet-verification" />
2378 <xs:enumeration value="vnd.kde.karbon" />1238 <xs:enumeration value="vnd.japannet-japannet--wakeup" />
2379 <xs:enumeration value="vnd.kde.kchart" />1239 <xs:enumeration value="vnd.jcp.javame.midlet-rms" />
2380 <xs:enumeration value="vnd.kde.kformula" />1240 <xs:enumeration value="vnd.jisp" />
2381 <xs:enumeration value="vnd.kde.kivio" />1241 <xs:enumeration value="vnd.joost.joda-archive" />
2382 <xs:enumeration value="vnd.kde.kontour" />1242 <xs:enumeration value="vnd.kahootz" />
2383 <xs:enumeration value="vnd.kde.kpresenter" />1243 <xs:enumeration value="vnd.kde.karbon" />
2384 <xs:enumeration value="vnd.kde.kspread" />1244 <xs:enumeration value="vnd.kde.kchart" />
2385 <xs:enumeration value="vnd.kde.kword" />1245 <xs:enumeration value="vnd.kde.kformula" />
2386 <xs:enumeration value="vnd.ken meaapp" />1246 <xs:enumeration value="vnd.kde.kivio" />
2387 <xs:enumeration value="vnd.kidspiration" />1247 <xs:enumeration value="vnd.kde.kontour" />
2388 <xs:enumeration value="vnd.Kinar" />1248 <xs:enumeration value="vnd.kde.kpresenter" />
2389 <xs:enumeration value="vnd.koan" />1249 <xs:enumeration value="vnd.kde.kspread" />
2390 <xs:enumeration value="vnd.kodak-descriptor" />1250 <xs:enumeration value="vnd.kde.kword" />
2391 <xs:enumeration value="vnd.liberty-request+xml" />1251 <xs:enumeration value="vnd.ken meaapp" />
2392 <xs:enumeration value="vnd.llamagraphics.life-balance.desktop" />1252 <xs:enumeration value="vnd.kidspiration" />
2393 <xs:enumeration1253 <xs:enumeration value="vnd.Kinar" />
2394 value="vnd.llamagraphics.life-balance.exchange+xml" />1254 <xs:enumeration value="vnd.koan" />
2395 <xs:enumeration value="vnd.lotus-1-2-3" />1255 <xs:enumeration value="vnd.kodak-descriptor" />
2396 <xs:enumeration value="vnd.lotus-approach" />1256 <xs:enumeration value="vnd.liberty-request+xml" />
2397 <xs:enumeration value="vnd.lotus-freelance" />1257 <xs:enumeration value="vnd.llamagraphics.life-balance.desktop" />
2398 <xs:enumeration value="vnd.lotus-notes" />1258 <xs:enumeration
2399 <xs:enumeration value="vnd.lotus-organizer" />1259 value="vnd.llamagraphics.life-balance.exchange+xml" />
2400 <xs:enumeration value="vnd.lotus-screencam" />1260 <xs:enumeration value="vnd.lotus-1-2-3" />
2401 <xs:enumeration value="vnd.lotus-wordpro" />1261 <xs:enumeration value="vnd.lotus-approach" />
2402 <xs:enumeration value="vnd.macports.portpkg" />1262 <xs:enumeration value="vnd.lotus-freelance" />
2403 <xs:enumeration value="vnd.marlin.drm.actiontoken+xml" />1263 <xs:enumeration value="vnd.lotus-notes" />
2404 <xs:enumeration value="vnd.marlin.drm.conftoken+xml" />1264 <xs:enumeration value="vnd.lotus-organizer" />
2405 <xs:enumeration value="vnd.marlin.drm.license+xml" />1265 <xs:enumeration value="vnd.lotus-screencam" />
2406 <xs:enumeration value="vnd.marlin.drm.mdcf" />1266 <xs:enumeration value="vnd.lotus-wordpro" />
24071267 <xs:enumeration value="vnd.macports.portpkg" />
2408Cheney Standards Track [Page 43]1268 <xs:enumeration value="vnd.marlin.drm.actiontoken+xml" />
24091269 <xs:enumeration value="vnd.marlin.drm.conftoken+xml" />
2410Internet-Draft Mail Markup Language - Version 1.0 April 20091270 <xs:enumeration value="vnd.marlin.drm.license+xml" />
24111271 <xs:enumeration value="vnd.marlin.drm.mdcf" />
2412 <xs:enumeration value="vnd.mcd" />1272 <xs:enumeration value="vnd.mcd" />
2413 <xs:enumeration value="vnd.medcalcdata" />1273 <xs:enumeration value="vnd.medcalcdata" />
2414 <xs:enumeration value="vnd.mediastation.cdkey" />1274 <xs:enumeration value="vnd.mediastation.cdkey" />
2415 <xs:enumeration value="vnd.meridian-slingshot" />1275 <xs:enumeration value="vnd.meridian-slingshot" />
2416 <xs:enumeration value="vnd.MFER" />1276 <xs:enumeration value="vnd.MFER" />
2417 <xs:enumeration value="vnd.mfmp" />1277 <xs:enumeration value="vnd.mfmp" />
2418 <xs:enumeration value="vnd.micrografx.flo" />1278 <xs:enumeration value="vnd.micrografx.flo" />
2419 <xs:enumeration value="vnd.micrografx.igx" />1279 <xs:enumeration value="vnd.micrografx.igx" />
2420 <xs:enumeration value="vnd.mif" />1280 <xs:enumeration value="vnd.mif" />
2421 <xs:enumeration value="vnd.minisoft-hp3000-save" />1281 <xs:enumeration value="vnd.minisoft-hp3000-save" />
2422 <xs:enumeration value="vnd.mitsubishi.misty-guard.trustweb" />1282 <xs:enumeration value="vnd.mitsubishi.misty-guard.trustweb" />
2423 <xs:enumeration value="vnd.Mobius.DAF" />1283 <xs:enumeration value="vnd.Mobius.DAF" />
2424 <xs:enumeration value="vnd.Mobius.DIS" />1284 <xs:enumeration value="vnd.Mobius.DIS" />
2425 <xs:enumeration value="vnd.Mobius.MBK" />1285 <xs:enumeration value="vnd.Mobius.MBK" />
2426 <xs:enumeration value="vnd.Mobius.MQY" />1286 <xs:enumeration value="vnd.Mobius.MQY" />
2427 <xs:enumeration value="vnd.Mobius.MSL" />1287
2428 <xs:enumeration value="vnd.Mobius.PLC" /> 1288Cheney Standards Track [Page 23]
2429 <xs:enumeration value="vnd.Mobius.TXF" />1289
2430 <xs:enumeration value="vnd.mophun.application" /> 1290Internet-Draft Mail Markup Language - Version 1.0 February 2009
2431 <xs:enumeration value="vnd.mophun.certificate" />1291
2432 <xs:enumeration value="vnd.motorola.flexsuite" />1292 <xs:enumeration value="vnd.Mobius.MSL" />
2433 <xs:enumeration value="vnd.motorola.flexsuite.adsi" />1293 <xs:enumeration value="vnd.Mobius.PLC" />
2434 <xs:enumeration value="vnd.motorola.flexsuite.fis" />1294 <xs:enumeration value="vnd.Mobius.TXF" />
2435 <xs:enumeration value="vnd.motorola.flexsuite.gotap" />1295 <xs:enumeration value="vnd.mophun.application" />
2436 <xs:enumeration value="vnd.motorola.flexsuite.kmr" />1296 <xs:enumeration value="vnd.mophun.certificate" />
2437 <xs:enumeration value="vnd.motorola.flexsuite.ttc" />1297 <xs:enumeration value="vnd.motorola.flexsuite" />
2438 <xs:enumeration value="vnd.motorola.flexsuite.wem" />1298 <xs:enumeration value="vnd.motorola.flexsuite.adsi" />
2439 <xs:enumeration value="vnd.mozilla.xul+xml" />1299 <xs:enumeration value="vnd.motorola.flexsuite.fis" />
2440 <xs:enumeration value="vnd.ms-artgalry" />1300 <xs:enumeration value="vnd.motorola.flexsuite.gotap" />
2441 <xs:enumeration value="vnd.ms-asf" />1301 <xs:enumeration value="vnd.motorola.flexsuite.kmr" />
2442 <xs:enumeration value="vnd.ms-cab-compressed" />1302 <xs:enumeration value="vnd.motorola.flexsuite.ttc" />
2443 <xs:enumeration value="vnd.ms-excel" />1303 <xs:enumeration value="vnd.motorola.flexsuite.wem" />
2444 <xs:enumeration value="vnd.ms-fontobject" />1304 <xs:enumeration value="vnd.mozilla.xul+xml" />
2445 <xs:enumeration value="vnd.ms-htmlhelp" />1305 <xs:enumeration value="vnd.ms-artgalry" />
2446 <xs:enumeration value="vnd.ms-ims" />1306 <xs:enumeration value="vnd.ms-asf" />
2447 <xs:enumeration value="vnd.ms-lrm" />1307 <xs:enumeration value="vnd.ms-cab-compressed" />
2448 <xs:enumeration value="vnd.ms-playready.initiator+xml" />1308 <xs:enumeration value="vnd.ms-excel" />
2449 <xs:enumeration value="vnd.ms-powerpoint" />1309 <xs:enumeration value="vnd.ms-fontobject" />
2450 <xs:enumeration value="vnd.ms-project" />1310 <xs:enumeration value="vnd.ms-htmlhelp" />
2451 <xs:enumeration value="vnd.ms-tnef" />1311 <xs:enumeration value="vnd.ms-ims" />
2452 <xs:enumeration value="vnd.ms-wmdrm.lic-chlg-req" />1312 <xs:enumeration value="vnd.ms-lrm" />
2453 <xs:enumeration value="vnd.ms-wmdrm.lic-resp" />1313 <xs:enumeration value="vnd.ms-playready.initiator+xml" />
2454 <xs:enumeration value="vnd.ms-wmdrm.meter-chlg-req" />1314 <xs:enumeration value="vnd.ms-powerpoint" />
2455 <xs:enumeration value="vnd.ms-wmdrm.meter-resp" />1315 <xs:enumeration value="vnd.ms-project" />
2456 <xs:enumeration value="vnd.ms-works" />1316 <xs:enumeration value="vnd.ms-tnef" />
2457 <xs:enumeration value="vnd.ms-wpl" />1317 <xs:enumeration value="vnd.ms-wmdrm.lic-chlg-req" />
2458 <xs:enumeration value="vnd.ms-xpsdocument" />1318 <xs:enumeration value="vnd.ms-wmdrm.lic-resp" />
2459 <xs:enumeration value="vnd.mseq" />1319 <xs:enumeration value="vnd.ms-wmdrm.meter-chlg-req" />
2460 <xs:enumeration value="vnd.msign" />1320 <xs:enumeration value="vnd.ms-wmdrm.meter-resp" />
2461 <xs:enumeration value="vnd.multiad.creator" />1321 <xs:enumeration value="vnd.ms-works" />
2462 <xs:enumeration value="vnd.multiad.creator.cif" />1322 <xs:enumeration value="vnd.ms-wpl" />
24631323 <xs:enumeration value="vnd.ms-xpsdocument" />
2464Cheney Standards Track [Page 44]1324 <xs:enumeration value="vnd.mseq" />
24651325 <xs:enumeration value="vnd.msign" />
2466Internet-Draft Mail Markup Language - Version 1.0 April 20091326 <xs:enumeration value="vnd.multiad.creator" />
24671327 <xs:enumeration value="vnd.multiad.creator.cif" />
2468 <xs:enumeration value="vnd.musician" />1328 <xs:enumeration value="vnd.musician" />
2469 <xs:enumeration value="vnd.music-niff" />1329 <xs:enumeration value="vnd.music-niff" />
2470 <xs:enumeration value="vnd.muvee.style" />1330 <xs:enumeration value="vnd.muvee.style" />
2471 <xs:enumeration value="vnd.ncd.control" />1331 <xs:enumeration value="vnd.ncd.control" />
2472 <xs:enumeration value="vnd.ncd.reference" />1332 <xs:enumeration value="vnd.ncd.reference" />
2473 <xs:enumeration value="vnd.nervana" />1333 <xs:enumeration value="vnd.nervana" />
2474 <xs:enumeration value="vnd.netfpx" />1334 <xs:enumeration value="vnd.netfpx" />
2475 <xs:enumeration value="vnd.neurolanguage.nlu" />1335 <xs:enumeration value="vnd.neurolanguage.nlu" />
2476 <xs:enumeration value="vnd.noblenet-directory" />1336 <xs:enumeration value="vnd.noblenet-directory" />
2477 <xs:enumeration value="vnd.noblenet-sealer" />1337 <xs:enumeration value="vnd.noblenet-sealer" />
2478 <xs:enumeration value="vnd.noblenet-web" />1338 <xs:enumeration value="vnd.noblenet-web" />
2479 <xs:enumeration value="vnd.nokia.catalogs" />1339 <xs:enumeration value="vnd.nokia.catalogs" />
2480 <xs:enumeration value="vnd.nokia.conml+wbxml" />1340 <xs:enumeration value="vnd.nokia.conml+wbxml" />
2481 <xs:enumeration value="vnd.nokia.conml+xml" />1341 <xs:enumeration value="vnd.nokia.conml+xml" />
2482 <xs:enumeration value="vnd.nokia.iptv.config+xml" />1342 <xs:enumeration value="vnd.nokia.iptv.config+xml" />
2483 <xs:enumeration value="vnd.nokia.iSDS-radio-presets" />1343
2484 <xs:enumeration value="vnd.nokia.landmark+xml" /> 1344Cheney Standards Track [Page 24]
2485 <xs:enumeration value="vnd.nokia.landmarkcollection+xml" />1345
2486 <xs:enumeration value="vnd.nokia.ncd" /> 1346Internet-Draft Mail Markup Language - Version 1.0 February 2009
2487 <xs:enumeration value="vnd.nokia.n-gage.ac+xml" />1347
2488 <xs:enumeration value="vnd.nokia.n-gage.data" />1348 <xs:enumeration value="vnd.nokia.iSDS-radio-presets" />
2489 <xs:enumeration value="vnd.nokia.n-gage.symbian.install" />1349 <xs:enumeration value="vnd.nokia.landmark+xml" />
2490 <xs:enumeration value="vnd.nokia.pcd+wbxml" />1350 <xs:enumeration value="vnd.nokia.landmarkcollection+xml" />
2491 <xs:enumeration value="vnd.nokia.pcd+xml" />1351 <xs:enumeration value="vnd.nokia.ncd" />
2492 <xs:enumeration value="vnd.nokia.radio-preset" />1352 <xs:enumeration value="vnd.nokia.n-gage.ac+xml" />
2493 <xs:enumeration value="vnd.nokia.radio-presets" />1353 <xs:enumeration value="vnd.nokia.n-gage.data" />
2494 <xs:enumeration value="vnd.novadigm.EDM" />1354 <xs:enumeration value="vnd.nokia.n-gage.symbian.install" />
2495 <xs:enumeration value="vnd.novadigm.EDX" />1355 <xs:enumeration value="vnd.nokia.pcd+wbxml" />
2496 <xs:enumeration value="vnd.novadigm.EXT" />1356 <xs:enumeration value="vnd.nokia.pcd+xml" />
2497 <xs:enumeration value="vnd.oasis.opendocument.chart" />1357 <xs:enumeration value="vnd.nokia.radio-preset" />
2498 <xs:enumeration value="vnd.oasis.opendocument.chart-template" />1358 <xs:enumeration value="vnd.nokia.radio-presets" />
2499 <xs:enumeration value="vnd.oasis.opendocument.formula" />1359 <xs:enumeration value="vnd.novadigm.EDM" />
2500 <xs:enumeration value="vnd.oasis.opendocument.formula-template" />1360 <xs:enumeration value="vnd.novadigm.EDX" />
2501 <xs:enumeration value="vnd.oasis.opendocument.graphics" />1361 <xs:enumeration value="vnd.novadigm.EXT" />
2502 <xs:enumeration1362 <xs:enumeration value="vnd.oasis.opendocument.chart" />
2503 value="vnd.oasis.opendocument.graphics-template" />1363 <xs:enumeration value="vnd.oasis.opendocument.chart-template" />
2504 <xs:enumeration value="vnd.oasis.opendocument.image" />1364 <xs:enumeration value="vnd.oasis.opendocument.formula" />
2505 <xs:enumeration value="vnd.oasis.opendocument.image-template" />1365 <xs:enumeration value="vnd.oasis.opendocument.formula-template" />
2506 <xs:enumeration value="vnd.oasis.opendocument.presentation" />1366 <xs:enumeration value="vnd.oasis.opendocument.graphics" />
2507 <xs:enumeration1367 <xs:enumeration
2508 value="vnd.oasis.opendocument.presentation-template" />1368 value="vnd.oasis.opendocument.graphics-template" />
2509 <xs:enumeration value="vnd.oasis.opendocument.spreadsheet" />1369 <xs:enumeration value="vnd.oasis.opendocument.image" />
2510 <xs:enumeration1370 <xs:enumeration value="vnd.oasis.opendocument.image-template" />
2511 value="vnd.oasis.opendocument.spreadsheet-template" />1371 <xs:enumeration value="vnd.oasis.opendocument.presentation" />
2512 <xs:enumeration value="vnd.oasis.opendocument.text" />1372 <xs:enumeration
2513 <xs:enumeration value="vnd.oasis.opendocument.text-master" />1373 value="vnd.oasis.opendocument.presentation-template" />
2514 <xs:enumeration value="vnd.oasis.opendocument.text-template" />1374 <xs:enumeration value="vnd.oasis.opendocument.spreadsheet" />
2515 <xs:enumeration value="vnd.oasis.opendocument.text-web" />1375 <xs:enumeration
2516 <xs:enumeration value="vnd.obn" />1376 value="vnd.oasis.opendocument.spreadsheet-template" />
2517 <xs:enumeration value="vnd.olpc-sugar" />1377 <xs:enumeration value="vnd.oasis.opendocument.text" />
2518 <xs:enumeration1378 <xs:enumeration value="vnd.oasis.opendocument.text-master" />
25191379 <xs:enumeration value="vnd.oasis.opendocument.text-template" />
2520Cheney Standards Track [Page 45]1380 <xs:enumeration value="vnd.oasis.opendocument.text-web" />
25211381 <xs:enumeration value="vnd.obn" />
2522Internet-Draft Mail Markup Language - Version 1.0 April 20091382 <xs:enumeration value="vnd.olpc-sugar" />
25231383 <xs:enumeration
2524 value="vnd.oma.bcast.asssociated-procedure-parameter+xml" />1384 value="vnd.oma.bcast.asssociated-procedure-parameter+xml" />
2525 <xs:enumeration value="vnd.oma.bcast.drm-trigger+xml" />1385 <xs:enumeration value="vnd.oma.bcast.drm-trigger+xml" />
2526 <xs:enumeration value="vnd.oma.bcast.imd+xml" />1386 <xs:enumeration value="vnd.oma.bcast.imd+xml" />
2527 <xs:enumeration value="vnd.oma.bcast.ltkm" />1387 <xs:enumeration value="vnd.oma.bcast.ltkm" />
2528 <xs:enumeration value="vnd.oma.bcast.notification+xml" />1388 <xs:enumeration value="vnd.oma.bcast.notification+xml" />
2529 <xs:enumeration value="vnd.oma.bcast.sgboot" />1389 <xs:enumeration value="vnd.oma.bcast.sgboot" />
2530 <xs:enumeration value="vnd.oma.bcast.sgdd+xml" />1390 <xs:enumeration value="vnd.oma.bcast.sgdd+xml" />
2531 <xs:enumeration value="vnd.oma.bcast.sgdu" />1391 <xs:enumeration value="vnd.oma.bcast.sgdu" />
2532 <xs:enumeration value="vnd.oma.bcast.simple-symbol-container" />1392 <xs:enumeration value="vnd.oma.bcast.simple-symbol-container" />
2533 <xs:enumeration value="vnd.oma.bcast.smartcard-trigger+xml" />1393 <xs:enumeration value="vnd.oma.bcast.smartcard-trigger+xml" />
2534 <xs:enumeration value="vnd.oma.bcast.sprov+xml" />1394 <xs:enumeration value="vnd.oma.bcast.sprov+xml" />
2535 <xs:enumeration value="vnd.oma.bcast.stkm" />1395 <xs:enumeration value="vnd.oma.bcast.stkm" />
2536 <xs:enumeration value="vnd.oma.dcd" />1396 <xs:enumeration value="vnd.oma.dcd" />
2537 <xs:enumeration value="vnd.oma.dcdc" />1397 <xs:enumeration value="vnd.oma.dcdc" />
2538 <xs:enumeration value="vnd.oma.dd2+xml" />1398 <xs:enumeration value="vnd.oma.dd2+xml" />
2539 <xs:enumeration value="vnd.oma.drm.risd+xml" />1399
2540 <xs:enumeration value="vnd.oma.group-usage-list+xml" /> 1400Cheney Standards Track [Page 25]
2541 <xs:enumeration1401
2542 value="vnd.oma.poc.detailed-progress-report+xml" /> 1402Internet-Draft Mail Markup Language - Version 1.0 February 2009
2543 <xs:enumeration value="vnd.oma.poc.final-report+xml" />1403
2544 <xs:enumeration value="vnd.oma.groups+xml" />1404 <xs:enumeration value="vnd.oma.drm.risd+xml" />
2545 <xs:enumeration value="vnd.oma.invocation-descriptor+xml" />1405 <xs:enumeration value="vnd.oma.group-usage-list+xml" />
2546 <xs:enumeration value="vnd.oma.optimized-progress-report+xml" />1406 <xs:enumeration
2547 <xs:enumeration value="vnd.oma.xcap-directory+xml" />1407 value="vnd.oma.poc.detailed-progress-report+xml" />
2548 <xs:enumeration value="vnd.omads-email+xml" />1408 <xs:enumeration value="vnd.oma.poc.final-report+xml" />
2549 <xs:enumeration value="vnd.omads-file+xml" />1409 <xs:enumeration value="vnd.oma.groups+xml" />
2550 <xs:enumeration value="vnd.omads-folder+xml" />1410 <xs:enumeration value="vnd.oma.invocation-descriptor+xml" />
2551 <xs:enumeration value="vnd.omaloc-sup-init" />1411 <xs:enumeration value="vnd.oma.optimized-progress-report+xml" />
2552 <xs:enumeration value="vnd.oma-scws-http-request" />1412 <xs:enumeration value="vnd.oma.xcap-directory+xml" />
2553 <xs:enumeration value="vnd.oma-scws-http-response" />1413 <xs:enumeration value="vnd.omads-email+xml" />
2554 <xs:enumeration value="vnd.openofficeorg.extension" />1414 <xs:enumeration value="vnd.omads-file+xml" />
2555 <xs:enumeration value="vnd.osa.netdeploy" />1415 <xs:enumeration value="vnd.omads-folder+xml" />
2556 <xs:enumeration value="vnd.osgi.bundle" />1416 <xs:enumeration value="vnd.omaloc-sup-init" />
2557 <xs:enumeration value="vnd.osgi.dp" />1417 <xs:enumeration value="vnd.oma-scws-http-request" />
2558 <xs:enumeration value="vnd.otps.ct-kip+xml" />1418 <xs:enumeration value="vnd.oma-scws-http-response" />
2559 <xs:enumeration value="vnd.palm" />1419 <xs:enumeration value="vnd.openofficeorg.extension" />
2560 <xs:enumeration value="vnd.paos.xml" />1420 <xs:enumeration value="vnd.osa.netdeploy" />
2561 <xs:enumeration value="vnd.pg.format" />1421 <xs:enumeration value="vnd.osgi.bundle" />
2562 <xs:enumeration value="vnd.pg.osasli" />1422 <xs:enumeration value="vnd.osgi.dp" />
2563 <xs:enumeration value="vnd.piacess.application-license" />1423 <xs:enumeration value="vnd.otps.ct-kip+xml" />
2564 <xs:enumeration value="vnd.picsel" />1424 <xs:enumeration value="vnd.palm" />
2565 <xs:enumeration value="vnd.poc.group-advertisement+xml" />1425 <xs:enumeration value="vnd.paos.xml" />
2566 <xs:enumeration value="vnd.pocketlearn" />1426 <xs:enumeration value="vnd.pg.format" />
2567 <xs:enumeration value="vnd.powerbuilder6" />1427 <xs:enumeration value="vnd.pg.osasli" />
2568 <xs:enumeration value="vnd.powerbuilder6-s" />1428 <xs:enumeration value="vnd.piacess.application-license" />
2569 <xs:enumeration value="vnd.powerbuilder7" />1429 <xs:enumeration value="vnd.picsel" />
2570 <xs:enumeration value="vnd.powerbuilder75" />1430 <xs:enumeration value="vnd.poc.group-advertisement+xml" />
2571 <xs:enumeration value="vnd.powerbuilder75-s" />1431 <xs:enumeration value="vnd.pocketlearn" />
2572 <xs:enumeration value="vnd.powerbuilder7-s" />1432 <xs:enumeration value="vnd.powerbuilder6" />
2573 <xs:enumeration value="vnd.preminet" />1433 <xs:enumeration value="vnd.powerbuilder6-s" />
2574 <xs:enumeration value="vnd.previewsystems.box" />1434 <xs:enumeration value="vnd.powerbuilder7" />
25751435 <xs:enumeration value="vnd.powerbuilder75" />
2576Cheney Standards Track [Page 46]1436 <xs:enumeration value="vnd.powerbuilder75-s" />
25771437 <xs:enumeration value="vnd.powerbuilder7-s" />
2578Internet-Draft Mail Markup Language - Version 1.0 April 20091438 <xs:enumeration value="vnd.preminet" />
25791439 <xs:enumeration value="vnd.previewsystems.box" />
2580 <xs:enumeration value="vnd.proteus.magazine" />1440 <xs:enumeration value="vnd.proteus.magazine" />
2581 <xs:enumeration value="vnd.publishare-delta-tree" />1441 <xs:enumeration value="vnd.publishare-delta-tree" />
2582 <xs:enumeration value="vnd.pvi.ptid1" />1442 <xs:enumeration value="vnd.pvi.ptid1" />
2583 <xs:enumeration value="vnd.pwg-multiplexed" />1443 <xs:enumeration value="vnd.pwg-multiplexed" />
2584 <xs:enumeration value="vnd.pwg-xhtml-print+xml" />1444 <xs:enumeration value="vnd.pwg-xhtml-print+xml" />
2585 <xs:enumeration value="vnd.qualcomm.brew-app-res" />1445 <xs:enumeration value="vnd.qualcomm.brew-app-res" />
2586 <xs:enumeration value="vnd.Quark.QuarkXPress" />1446 <xs:enumeration value="vnd.Quark.QuarkXPress" />
2587 <xs:enumeration value="vnd.rapid" />1447 <xs:enumeration value="vnd.rapid" />
2588 <xs:enumeration value="vnd.recordare.musicxml" />1448 <xs:enumeration value="vnd.recordare.musicxml" />
2589 <xs:enumeration value="vnd.recordare.musicxml+xml" />1449 <xs:enumeration value="vnd.recordare.musicxml+xml" />
2590 <xs:enumeration value="vnd.RenLearn.rlprint" />1450 <xs:enumeration value="vnd.RenLearn.rlprint" />
2591 <xs:enumeration value="vnd.route66.link66+xml" />1451 <xs:enumeration value="vnd.route66.link66+xml" />
2592 <xs:enumeration value="vnd.ruckus.download" />1452 <xs:enumeration value="vnd.ruckus.download" />
2593 <xs:enumeration value="vnd.s3sms" />1453 <xs:enumeration value="vnd.s3sms" />
2594 <xs:enumeration value="vnd.sbm.cid" />1454 <xs:enumeration value="vnd.sbm.cid" />
2595 <xs:enumeration value="vnd.sbm.mid2" />1455
2596 <xs:enumeration value="vnd.scribus" /> 1456Cheney Standards Track [Page 26]
2597 <xs:enumeration value="vnd.sealed.3df" />1457
2598 <xs:enumeration value="vnd.sealed.csf" /> 1458Internet-Draft Mail Markup Language - Version 1.0 February 2009
2599 <xs:enumeration value="vnd.sealed.doc" />1459
2600 <xs:enumeration value="vnd.sealed.eml" />1460 <xs:enumeration value="vnd.sbm.mid2" />
2601 <xs:enumeration value="vnd.sealed.mht" />1461 <xs:enumeration value="vnd.scribus" />
2602 <xs:enumeration value="vnd.sealed.net" />1462 <xs:enumeration value="vnd.sealed.3df" />
2603 <xs:enumeration value="vnd.sealed.ppt" />1463 <xs:enumeration value="vnd.sealed.csf" />
2604 <xs:enumeration value="vnd.sealed.tiff" />1464 <xs:enumeration value="vnd.sealed.doc" />
2605 <xs:enumeration value="vnd.sealed.xls" />1465 <xs:enumeration value="vnd.sealed.eml" />
2606 <xs:enumeration value="vnd.sealedmedia.softseal.html" />1466 <xs:enumeration value="vnd.sealed.mht" />
2607 <xs:enumeration value="vnd.sealedmedia.softseal.pdf" />1467 <xs:enumeration value="vnd.sealed.net" />
2608 <xs:enumeration value="vnd.seemail" />1468 <xs:enumeration value="vnd.sealed.ppt" />
2609 <xs:enumeration value="vnd.sema" />1469 <xs:enumeration value="vnd.sealed.tiff" />
2610 <xs:enumeration value="vnd.semd" />1470 <xs:enumeration value="vnd.sealed.xls" />
2611 <xs:enumeration value="vnd.semf" />1471 <xs:enumeration value="vnd.sealedmedia.softseal.html" />
2612 <xs:enumeration value="vnd.shana.informed.formdata" />1472 <xs:enumeration value="vnd.sealedmedia.softseal.pdf" />
2613 <xs:enumeration value="vnd.shana.informed.formtemplate" />1473 <xs:enumeration value="vnd.seemail" />
2614 <xs:enumeration value="vnd.shana.informed.interchange" />1474 <xs:enumeration value="vnd.sema" />
2615 <xs:enumeration value="vnd.shana.informed.package" />1475 <xs:enumeration value="vnd.semd" />
2616 <xs:enumeration value="vnd.SimTech-MindMapper" />1476 <xs:enumeration value="vnd.semf" />
2617 <xs:enumeration value="vnd.smaf" />1477 <xs:enumeration value="vnd.shana.informed.formdata" />
2618 <xs:enumeration value="vnd.solent.sdkm+xml" />1478 <xs:enumeration value="vnd.shana.informed.formtemplate" />
2619 <xs:enumeration value="vnd.spotfire.dxp" />1479 <xs:enumeration value="vnd.shana.informed.interchange" />
2620 <xs:enumeration value="vnd.spotfire.sfs" />1480 <xs:enumeration value="vnd.shana.informed.package" />
2621 <xs:enumeration value="vnd.sss-cod" />1481 <xs:enumeration value="vnd.SimTech-MindMapper" />
2622 <xs:enumeration value="vnd.sss-dtf" />1482 <xs:enumeration value="vnd.smaf" />
2623 <xs:enumeration value="vnd.sss-ntf" />1483 <xs:enumeration value="vnd.solent.sdkm+xml" />
2624 <xs:enumeration value="vnd.street-stream" />1484 <xs:enumeration value="vnd.spotfire.dxp" />
2625 <xs:enumeration value="vnd.sun.wadl+xml" />1485 <xs:enumeration value="vnd.spotfire.sfs" />
2626 <xs:enumeration value="vnd.sus-calendar" />1486 <xs:enumeration value="vnd.sss-cod" />
2627 <xs:enumeration value="vnd.svd" />1487 <xs:enumeration value="vnd.sss-dtf" />
2628 <xs:enumeration value="vnd.swiftview-ics" />1488 <xs:enumeration value="vnd.sss-ntf" />
2629 <xs:enumeration value="vnd.syncml.dm+wbxml" />1489 <xs:enumeration value="vnd.street-stream" />
2630 <xs:enumeration value="vnd.syncml.dm+xml" />1490 <xs:enumeration value="vnd.sun.wadl+xml" />
26311491 <xs:enumeration value="vnd.sus-calendar" />
2632Cheney Standards Track [Page 47]1492 <xs:enumeration value="vnd.svd" />
26331493 <xs:enumeration value="vnd.swiftview-ics" />
2634Internet-Draft Mail Markup Language - Version 1.0 April 20091494 <xs:enumeration value="vnd.syncml.dm+wbxml" />
26351495 <xs:enumeration value="vnd.syncml.dm+xml" />
2636 <xs:enumeration value="vnd.syncml.ds.notification" />1496 <xs:enumeration value="vnd.syncml.ds.notification" />
2637 <xs:enumeration value="vnd.syncml+xml" />1497 <xs:enumeration value="vnd.syncml+xml" />
2638 <xs:enumeration value="vnd.tao.intent-module-archive" />1498 <xs:enumeration value="vnd.tao.intent-module-archive" />
2639 <xs:enumeration value="vnd.tmobile-livetv" />1499 <xs:enumeration value="vnd.tmobile-livetv" />
2640 <xs:enumeration value="vnd.trid.tpt" />1500 <xs:enumeration value="vnd.trid.tpt" />
2641 <xs:enumeration value="vnd.triscape.mxs" />1501 <xs:enumeration value="vnd.triscape.mxs" />
2642 <xs:enumeration value="vnd.trueapp" />1502 <xs:enumeration value="vnd.trueapp" />
2643 <xs:enumeration value="vnd.truedoc" />1503 <xs:enumeration value="vnd.truedoc" />
2644 <xs:enumeration value="vnd.ufdl" />1504 <xs:enumeration value="vnd.ufdl" />
2645 <xs:enumeration value="vnd.uig.theme" />1505 <xs:enumeration value="vnd.uig.theme" />
2646 <xs:enumeration value="vnd.umajin" />1506 <xs:enumeration value="vnd.umajin" />
2647 <xs:enumeration value="vnd.unity" />1507 <xs:enumeration value="vnd.unity" />
2648 <xs:enumeration value="vnd.uoml+xml" />1508 <xs:enumeration value="vnd.uoml+xml" />
2649 <xs:enumeration value="vnd.uplanet.alert" />1509 <xs:enumeration value="vnd.uplanet.alert" />
2650 <xs:enumeration value="vnd.uplanet.alert-wbxml" />1510 <xs:enumeration value="vnd.uplanet.alert-wbxml" />
2651 <xs:enumeration value="vnd.uplanet.bearer-choice" />1511
2652 <xs:enumeration value="vnd.uplanet.bearer-choice-wbxml" /> 1512Cheney Standards Track [Page 27]
2653 <xs:enumeration value="vnd.uplanet.cacheop" />1513
2654 <xs:enumeration value="vnd.uplanet.cacheop-wbxml" /> 1514Internet-Draft Mail Markup Language - Version 1.0 February 2009
2655 <xs:enumeration value="vnd.uplanet.channel" />1515
2656 <xs:enumeration value="vnd.uplanet.channel-wbxml" />1516 <xs:enumeration value="vnd.uplanet.bearer-choice" />
2657 <xs:enumeration value="vnd.uplanet.list" />1517 <xs:enumeration value="vnd.uplanet.bearer-choice-wbxml" />
2658 <xs:enumeration value="vnd.uplanet.listcmd" />1518 <xs:enumeration value="vnd.uplanet.cacheop" />
2659 <xs:enumeration value="vnd.uplanet.listcmd-wbxml" />1519 <xs:enumeration value="vnd.uplanet.cacheop-wbxml" />
2660 <xs:enumeration value="vnd.uplanet.list-wbxml" />1520 <xs:enumeration value="vnd.uplanet.channel" />
2661 <xs:enumeration value="vnd.uplanet.signal" />1521 <xs:enumeration value="vnd.uplanet.channel-wbxml" />
2662 <xs:enumeration value="vnd.vcx" />1522 <xs:enumeration value="vnd.uplanet.list" />
2663 <xs:enumeration value="vnd.vectorworks" />1523 <xs:enumeration value="vnd.uplanet.listcmd" />
2664 <xs:enumeration value="vnd.vd-study" />1524 <xs:enumeration value="vnd.uplanet.listcmd-wbxml" />
2665 <xs:enumeration value="vnd.vidsoft.vidconfer" />1525 <xs:enumeration value="vnd.uplanet.list-wbxml" />
2666 <xs:enumeration value="vnd.visio" />1526 <xs:enumeration value="vnd.uplanet.signal" />
2667 <xs:enumeration value="vnd.visionary" />1527 <xs:enumeration value="vnd.vcx" />
2668 <xs:enumeration value="vnd.vividence.scriptfile" />1528 <xs:enumeration value="vnd.vectorworks" />
2669 <xs:enumeration value="vnd.vsf" />1529 <xs:enumeration value="vnd.vd-study" />
2670 <xs:enumeration value="vnd.wap.sic" />1530 <xs:enumeration value="vnd.vidsoft.vidconfer" />
2671 <xs:enumeration value="vnd.wap.slc" />1531 <xs:enumeration value="vnd.visio" />
2672 <xs:enumeration value="vnd.wap.wbxml" />1532 <xs:enumeration value="vnd.visionary" />
2673 <xs:enumeration value="vnd.wap.wmlc" />1533 <xs:enumeration value="vnd.vividence.scriptfile" />
2674 <xs:enumeration value="vnd.wmlscriptc" />1534 <xs:enumeration value="vnd.vsf" />
2675 <xs:enumeration value="vnd.webturbo" />1535 <xs:enumeration value="vnd.wap.sic" />
2676 <xs:enumeration value="vnd.wfa.wsc" />1536 <xs:enumeration value="vnd.wap.slc" />
2677 <xs:enumeration value="vnd.wmc" />1537 <xs:enumeration value="vnd.wap.wbxml" />
2678 <xs:enumeration value="vnd.wmf.bootstrap" />1538 <xs:enumeration value="vnd.wap.wmlc" />
2679 <xs:enumeration value="vnd.wordperfect" />1539 <xs:enumeration value="vnd.wmlscriptc" />
2680 <xs:enumeration value="vnd.wqd" />1540 <xs:enumeration value="vnd.webturbo" />
2681 <xs:enumeration value="vnd.wrq-hp3000-labelled" />1541 <xs:enumeration value="vnd.wfa.wsc" />
2682 <xs:enumeration value="vnd.wt.stf" />1542 <xs:enumeration value="vnd.wmc" />
2683 <xs:enumeration value="vnd.wv.csp+xml" />1543 <xs:enumeration value="vnd.wmf.bootstrap" />
2684 <xs:enumeration value="vnd.wv.csp+wbxml" />1544 <xs:enumeration value="vnd.wordperfect" />
2685 <xs:enumeration value="vnd.wv.ssp+xml" />1545 <xs:enumeration value="vnd.wqd" />
2686 <xs:enumeration value="vnd.xara" />1546 <xs:enumeration value="vnd.wrq-hp3000-labelled" />
26871547 <xs:enumeration value="vnd.wt.stf" />
2688Cheney Standards Track [Page 48]1548 <xs:enumeration value="vnd.wv.csp+xml" />
26891549 <xs:enumeration value="vnd.wv.csp+wbxml" />
2690Internet-Draft Mail Markup Language - Version 1.0 April 20091550 <xs:enumeration value="vnd.wv.ssp+xml" />
26911551 <xs:enumeration value="vnd.xara" />
2692 <xs:enumeration value="vnd.xfdl" />1552 <xs:enumeration value="vnd.xfdl" />
2693 <xs:enumeration value="vnd.xmi+xml" />1553 <xs:enumeration value="vnd.xmi+xml" />
2694 <xs:enumeration value="vnd.xmpie.cpkg" />1554 <xs:enumeration value="vnd.xmpie.cpkg" />
2695 <xs:enumeration value="vnd.xmpie.dpkg" />1555 <xs:enumeration value="vnd.xmpie.dpkg" />
2696 <xs:enumeration value="vnd.xmpie.plan" />1556 <xs:enumeration value="vnd.xmpie.plan" />
2697 <xs:enumeration value="vnd.xmpie.ppkq" />1557 <xs:enumeration value="vnd.xmpie.ppkq" />
2698 <xs:enumeration value="vnd.xmpie.xlim" />1558 <xs:enumeration value="vnd.xmpie.xlim" />
2699 <xs:enumeration value="vnd.yamaha.hv-dic" />1559 <xs:enumeration value="vnd.yamaha.hv-dic" />
2700 <xs:enumeration value="vnd.yamaha.hv-script" />1560 <xs:enumeration value="vnd.yamaha.hv-script" />
2701 <xs:enumeration value="vnd.yamaha.hv-voice" />1561 <xs:enumeration value="vnd.yamaha.hv-voice" />
2702 <xs:enumeration value="vnd.yamaha.smaf-audio" />1562 <xs:enumeration value="vnd.yamaha.smaf-audio" />
2703 <xs:enumeration value="vnd.yamaha.smaf-phrase" />1563 <xs:enumeration value="vnd.yamaha.smaf-phrase" />
2704 <xs:enumeration value="vnd.yellowriver-custom-menu" />1564 <xs:enumeration value="vnd.yellowriver-custom-menu" />
2705 <xs:enumeration value="vnd.zzazz.deck+xml" />1565 <xs:enumeration value="vnd.zzazz.deck+xml" />
2706 <xs:enumeration value="voicexml+xml" />1566 <xs:enumeration value="voicexml+xml" />
2707 <xs:enumeration value="watcherinfo+xml" />1567
2708 <xs:enumeration value="whoispp-query" /> 1568Cheney Standards Track [Page 28]
2709 <xs:enumeration value="whoispp-response" />1569
2710 <xs:enumeration value="wita" /> 1570Internet-Draft Mail Markup Language - Version 1.0 February 2009
2711 <xs:enumeration value="wordperfect5.1" />1571
2712 <xs:enumeration value="wsdl+xml" />1572 <xs:enumeration value="watcherinfo+xml" />
2713 <xs:enumeration value="wspolicy+xml" />1573 <xs:enumeration value="whoispp-query" />
2714 <xs:enumeration value="x400-bp" />1574 <xs:enumeration value="whoispp-response" />
2715 <xs:enumeration value="xcap-att+xml" />1575 <xs:enumeration value="wita" />
2716 <xs:enumeration value="xcap-caps+xml" />1576 <xs:enumeration value="wordperfect5.1" />
2717 <xs:enumeration value="xcap-el+xml" />1577 <xs:enumeration value="wsdl+xml" />
2718 <xs:enumeration value="xcap-error+xml" />1578 <xs:enumeration value="wspolicy+xml" />
2719 <xs:enumeration value="xcap-ns+xml" />1579 <xs:enumeration value="x400-bp" />
2720 <xs:enumeration value="xenc+xml" />1580 <xs:enumeration value="xcap-att+xml" />
2721 <xs:enumeration value="xhtml+xml" />1581 <xs:enumeration value="xcap-caps+xml" />
2722 <xs:enumeration value="xml" />1582 <xs:enumeration value="xcap-el+xml" />
2723 <xs:enumeration value="xml-dtd" />1583 <xs:enumeration value="xcap-error+xml" />
2724 <xs:enumeration value="xml-external-parsed-entity" />1584 <xs:enumeration value="xcap-ns+xml" />
2725 <xs:enumeration value="xmpp+xml" />1585 <xs:enumeration value="xenc+xml" />
2726 <xs:enumeration value="xop+xml" />1586 <xs:enumeration value="xhtml+xml" />
2727 <xs:enumeration value="xv+xml" />1587 <xs:enumeration value="xml" />
2728 <xs:enumeration value="zip" />1588 <xs:enumeration value="xml-dtd" />
2729 </xs:restriction>1589 <xs:enumeration value="xml-external-parsed-entity" />
2730 </xs:simpleType>1590 <xs:enumeration value="xmpp+xml" />
2731 <xs:simpleType name="audio-type">1591 <xs:enumeration value="xop+xml" />
2732 <xs:restriction base="xs:token">1592 <xs:enumeration value="xv+xml" />
2733 <xs:enumeration value="32kadpcm" />1593 <xs:enumeration value="zip" />
2734 <xs:enumeration value="3gpp" />1594 </xs:restriction>
2735 <xs:enumeration value="3gpp2" />1595 </xs:simpleType>
2736 <xs:enumeration value="ac3" />1596 <xs:simpleType name="audio-type">
2737 <xs:enumeration value="AMR" />1597 <xs:restriction base="xs:token">
2738 <xs:enumeration value="AMR-WB" />1598 <xs:enumeration value="32kadpcm" />
2739 <xs:enumeration value="amr-wb+" />1599 <xs:enumeration value="3gpp" />
2740 <xs:enumeration value="asc" />1600 <xs:enumeration value="3gpp2" />
2741 <xs:enumeration value="basic" />1601 <xs:enumeration value="ac3" />
2742 <xs:enumeration value="BV16" />1602 <xs:enumeration value="AMR" />
27431603 <xs:enumeration value="AMR-WB" />
2744Cheney Standards Track [Page 49]1604 <xs:enumeration value="amr-wb+" />
27451605 <xs:enumeration value="asc" />
2746Internet-Draft Mail Markup Language - Version 1.0 April 20091606 <xs:enumeration value="basic" />
27471607 <xs:enumeration value="BV16" />
2748 <xs:enumeration value="BV32" />1608 <xs:enumeration value="BV32" />
2749 <xs:enumeration value="clearmode" />1609 <xs:enumeration value="clearmode" />
2750 <xs:enumeration value="CN" />1610 <xs:enumeration value="CN" />
2751 <xs:enumeration value="DAT12" />1611 <xs:enumeration value="DAT12" />
2752 <xs:enumeration value="dls" />1612 <xs:enumeration value="dls" />
2753 <xs:enumeration value="dsr-es201108" />1613 <xs:enumeration value="dsr-es201108" />
2754 <xs:enumeration value="dsr-es202050" />1614 <xs:enumeration value="dsr-es202050" />
2755 <xs:enumeration value="dsr-es202211" />1615 <xs:enumeration value="dsr-es202211" />
2756 <xs:enumeration value="dsr-es202212" />1616 <xs:enumeration value="dsr-es202212" />
2757 <xs:enumeration value="eac3" />1617 <xs:enumeration value="eac3" />
2758 <xs:enumeration value="DVI4" />1618 <xs:enumeration value="DVI4" />
2759 <xs:enumeration value="EVRC" />1619 <xs:enumeration value="EVRC" />
2760 <xs:enumeration value="EVRC0" />1620 <xs:enumeration value="EVRC0" />
2761 <xs:enumeration value="EVRC1" />1621 <xs:enumeration value="EVRC1" />
2762 <xs:enumeration value="EVRCB" />1622 <xs:enumeration value="EVRCB" />
2763 <xs:enumeration value="EVRCB0" />1623
2764 <xs:enumeration value="EVRCB1" /> 1624Cheney Standards Track [Page 29]
2765 <xs:enumeration value="EVRC-QCP" />1625
2766 <xs:enumeration value="EVRCWB" /> 1626Internet-Draft Mail Markup Language - Version 1.0 February 2009
2767 <xs:enumeration value="EVRCWB0" />1627
2768 <xs:enumeration value="EVRCWB1" />1628 <xs:enumeration value="EVRCB0" />
2769 <xs:enumeration value="example" />1629 <xs:enumeration value="EVRCB1" />
2770 <xs:enumeration value="G722" />1630 <xs:enumeration value="EVRC-QCP" />
2771 <xs:enumeration value="G7221" />1631 <xs:enumeration value="EVRCWB" />
2772 <xs:enumeration value="G723" />1632 <xs:enumeration value="EVRCWB0" />
2773 <xs:enumeration value="G726-16" />1633 <xs:enumeration value="EVRCWB1" />
2774 <xs:enumeration value="G726-24" />1634 <xs:enumeration value="example" />
2775 <xs:enumeration value="G726-32" />1635 <xs:enumeration value="G722" />
2776 <xs:enumeration value="G726-40" />1636 <xs:enumeration value="G7221" />
2777 <xs:enumeration value="G728" />1637 <xs:enumeration value="G723" />
2778 <xs:enumeration value="G729" />1638 <xs:enumeration value="G726-16" />
2779 <xs:enumeration value="G7291" />1639 <xs:enumeration value="G726-24" />
2780 <xs:enumeration value="G72D" />1640 <xs:enumeration value="G726-32" />
2781 <xs:enumeration value="G72E" />1641 <xs:enumeration value="G726-40" />
2782 <xs:enumeration value="GSM" />1642 <xs:enumeration value="G728" />
2783 <xs:enumeration value="GSM-EFR" />1643 <xs:enumeration value="G729" />
2784 <xs:enumeration value="iLBC" />1644 <xs:enumeration value="G7291" />
2785 <xs:enumeration value="L8" />1645 <xs:enumeration value="G72D" />
2786 <xs:enumeration value="L16" />1646 <xs:enumeration value="G72E" />
2787 <xs:enumeration value="L20" />1647 <xs:enumeration value="GSM" />
2788 <xs:enumeration value="L24" />1648 <xs:enumeration value="GSM-EFR" />
2789 <xs:enumeration value="LPC" />1649 <xs:enumeration value="iLBC" />
2790 <xs:enumeration value="mobile-xml" />1650 <xs:enumeration value="L8" />
2791 <xs:enumeration value="MPA" />1651 <xs:enumeration value="L16" />
2792 <xs:enumeration value="mp4" />1652 <xs:enumeration value="L20" />
2793 <xs:enumeration value="MP4A-LATM" />1653 <xs:enumeration value="L24" />
2794 <xs:enumeration value="mpa-robust" />1654 <xs:enumeration value="LPC" />
2795 <xs:enumeration value="mpeg" />1655 <xs:enumeration value="mobile-xml" />
2796 <xs:enumeration value="mpeg4-generic" />1656 <xs:enumeration value="MPA" />
2797 <xs:enumeration value="ogg" />1657 <xs:enumeration value="mp4" />
2798 <xs:enumeration value="parityfec" />1658 <xs:enumeration value="MP4A-LATM" />
27991659 <xs:enumeration value="mpa-robust" />
2800Cheney Standards Track [Page 50]1660 <xs:enumeration value="mpeg" />
28011661 <xs:enumeration value="mpeg4-generic" />
2802Internet-Draft Mail Markup Language - Version 1.0 April 20091662 <xs:enumeration value="ogg" />
28031663 <xs:enumeration value="parityfec" />
2804 <xs:enumeration value="PCMA" />1664 <xs:enumeration value="PCMA" />
2805 <xs:enumeration value="PCMU" />1665 <xs:enumeration value="PCMU" />
2806 <xs:enumeration value="prs.sid" />1666 <xs:enumeration value="prs.sid" />
2807 <xs:enumeration value="QCELP" />1667 <xs:enumeration value="QCELP" />
2808 <xs:enumeration value="RED" />1668 <xs:enumeration value="RED" />
2809 <xs:enumeration value="rtp-enc-aescm128" />1669 <xs:enumeration value="rtp-enc-aescm128" />
2810 <xs:enumeration value="rtp-midi" />1670 <xs:enumeration value="rtp-midi" />
2811 <xs:enumeration value="rtx" />1671 <xs:enumeration value="rtx" />
2812 <xs:enumeration value="SMV" />1672 <xs:enumeration value="SMV" />
2813 <xs:enumeration value="SMV0" />1673 <xs:enumeration value="SMV0" />
2814 <xs:enumeration value="SMV-QCP" />1674 <xs:enumeration value="SMV-QCP" />
2815 <xs:enumeration value="sp-midi" />1675 <xs:enumeration value="sp-midi" />
2816 <xs:enumeration value="t140c" />1676 <xs:enumeration value="t140c" />
2817 <xs:enumeration value="t38" />1677 <xs:enumeration value="t38" />
2818 <xs:enumeration value="telephone-event" />1678 <xs:enumeration value="telephone-event" />
2819 <xs:enumeration value="tone" />1679
2820 <xs:enumeration value="ulpfec" /> 1680Cheney Standards Track [Page 30]
2821 <xs:enumeration value="VDVI" />1681
2822 <xs:enumeration value="VRM-WB" /> 1682Internet-Draft Mail Markup Language - Version 1.0 February 2009
2823 <xs:enumeration value="vnd.3gpp.iufp" />1683
2824 <xs:enumeration value="vnd.4SB" />1684 <xs:enumeration value="tone" />
2825 <xs:enumeration value="vnd.audiokoz" />1685 <xs:enumeration value="ulpfec" />
2826 <xs:enumeration value="vnd.CELP" />1686 <xs:enumeration value="VDVI" />
2827 <xs:enumeration value="vnd.cisco.nse" />1687 <xs:enumeration value="VRM-WB" />
2828 <xs:enumeration value="vnd.cmles.radio-events" />1688 <xs:enumeration value="vnd.3gpp.iufp" />
2829 <xs:enumeration value="vnd.cns.anp1" />1689 <xs:enumeration value="vnd.4SB" />
2830 <xs:enumeration value="vnd.cns.inf1" />1690 <xs:enumeration value="vnd.audiokoz" />
2831 <xs:enumeration value="vnd.digital-winds" />1691 <xs:enumeration value="vnd.CELP" />
2832 <xs:enumeration value="vnd.dlna.adts" />1692 <xs:enumeration value="vnd.cisco.nse" />
2833 <xs:enumeration value="vnd.dolby.mlp" />1693 <xs:enumeration value="vnd.cmles.radio-events" />
2834 <xs:enumeration value="vnd.everad.plj" />1694 <xs:enumeration value="vnd.cns.anp1" />
2835 <xs:enumeration value="vnd.hns.audio" />1695 <xs:enumeration value="vnd.cns.inf1" />
2836 <xs:enumeration value="vnd.lucent.voice" />1696 <xs:enumeration value="vnd.digital-winds" />
2837 <xs:enumeration value="vnd.ms-playready.media.pya" />1697 <xs:enumeration value="vnd.dlna.adts" />
2838 <xs:enumeration value="vnd.mokia.mobile-xmf" />1698 <xs:enumeration value="vnd.dolby.mlp" />
2839 <xs:enumeration value="vnd.nortel.vbk" />1699 <xs:enumeration value="vnd.everad.plj" />
2840 <xs:enumeration value="vnd.nuera.ecelp4800" />1700 <xs:enumeration value="vnd.hns.audio" />
2841 <xs:enumeration value="vnd.nuera.ecelp7470" />1701 <xs:enumeration value="vnd.lucent.voice" />
2842 <xs:enumeration value="vnd.nuera.ecelp9600" />1702 <xs:enumeration value="vnd.ms-playready.media.pya" />
2843 <xs:enumeration value="vnd.octel.sbc" />1703 <xs:enumeration value="vnd.mokia.mobile-xmf" />
2844 <xs:enumeration value="vnd.rhetorex.32kadpcm" />1704 <xs:enumeration value="vnd.nortel.vbk" />
2845 <xs:enumeration value="vnd.sealedmedia.softseal.mpeg" />1705 <xs:enumeration value="vnd.nuera.ecelp4800" />
2846 <xs:enumeration value="vnd.vmx.cvsd" />1706 <xs:enumeration value="vnd.nuera.ecelp7470" />
2847 <xs:enumeration value="vorbis" />1707 <xs:enumeration value="vnd.nuera.ecelp9600" />
2848 <xs:enumeration value="vorbis.config" />1708 <xs:enumeration value="vnd.octel.sbc" />
2849 </xs:restriction>1709 <xs:enumeration value="vnd.rhetorex.32kadpcm" />
2850 </xs:simpleType>1710 <xs:enumeration value="vnd.sealedmedia.softseal.mpeg" />
2851 <xs:simpleType name="example-type">1711 <xs:enumeration value="vnd.vmx.cvsd" />
2852 <xs:restriction base="xs:token" />1712 <xs:enumeration value="vorbis" />
2853 </xs:simpleType>1713 <xs:enumeration value="vorbis.config" />
2854 <xs:simpleType name="image-type">1714 </xs:restriction>
28551715 </xs:simpleType>
2856Cheney Standards Track [Page 51]1716 <xs:simpleType name="example-type">
28571717 <xs:restriction base="xs:token" />
2858Internet-Draft Mail Markup Language - Version 1.0 April 20091718 </xs:simpleType>
28591719 <xs:simpleType name="image-type">
2860 <xs:restriction base="xs:token">1720 <xs:restriction base="xs:token">
2861 <xs:enumeration value="cgm" />1721 <xs:enumeration value="cgm" />
2862 <xs:enumeration value="example" />1722 <xs:enumeration value="example" />
2863 <xs:enumeration value="fits" />1723 <xs:enumeration value="fits" />
2864 <xs:enumeration value="g3fax" />1724 <xs:enumeration value="g3fax" />
2865 <xs:enumeration value="gif" />1725 <xs:enumeration value="gif" />
2866 <xs:enumeration value="ief" />1726 <xs:enumeration value="ief" />
2867 <xs:enumeration value="jp2" />1727 <xs:enumeration value="jp2" />
2868 <xs:enumeration value="jpeg" />1728 <xs:enumeration value="jpeg" />
2869 <xs:enumeration value="jpm" />1729 <xs:enumeration value="jpm" />
2870 <xs:enumeration value="jpx" />1730 <xs:enumeration value="jpx" />
2871 <xs:enumeration value="naplps" />1731 <xs:enumeration value="naplps" />
2872 <xs:enumeration value="png" />1732 <xs:enumeration value="png" />
2873 <xs:enumeration value="prs.btif" />1733 <xs:enumeration value="prs.btif" />
2874 <xs:enumeration value="prs.pti" />1734 <xs:enumeration value="prs.pti" />
2875 <xs:enumeration value="t38" />1735
2876 <xs:enumeration value="tiff" /> 1736Cheney Standards Track [Page 31]
2877 <xs:enumeration value="tiff-fx" />1737
2878 <xs:enumeration value="vnd.adobe.photoshop" /> 1738Internet-Draft Mail Markup Language - Version 1.0 February 2009
2879 <xs:enumeration value="vnd.cns.inf2" />1739
2880 <xs:enumeration value="vnd.djvu" />1740 <xs:enumeration value="t38" />
2881 <xs:enumeration value="vnd.dwg" />1741 <xs:enumeration value="tiff" />
2882 <xs:enumeration value="vnd.dxf" />1742 <xs:enumeration value="tiff-fx" />
2883 <xs:enumeration value="vnd.fastbidsheet" />1743 <xs:enumeration value="vnd.adobe.photoshop" />
2884 <xs:enumeration value="vnd.fpx" />1744 <xs:enumeration value="vnd.cns.inf2" />
2885 <xs:enumeration value="vnd.fst" />1745 <xs:enumeration value="vnd.djvu" />
2886 <xs:enumeration value="vnd.fujixerox.edmics-mmr" />1746 <xs:enumeration value="vnd.dwg" />
2887 <xs:enumeration value="vnd.fujixerox.edmics-rlc" />1747 <xs:enumeration value="vnd.dxf" />
2888 <xs:enumeration value="vnd.microsoft.icon" />1748 <xs:enumeration value="vnd.fastbidsheet" />
2889 <xs:enumeration value="vnd.mix" />1749 <xs:enumeration value="vnd.fpx" />
2890 <xs:enumeration value="vnd.ms-modi" />1750 <xs:enumeration value="vnd.fst" />
2891 <xs:enumeration value="vnd.net-fpx" />1751 <xs:enumeration value="vnd.fujixerox.edmics-mmr" />
2892 <xs:enumeration value="vnd.sealed.png" />1752 <xs:enumeration value="vnd.fujixerox.edmics-rlc" />
2893 <xs:enumeration value="vnd.sealedmedia.softseal.gif" />1753 <xs:enumeration value="vnd.microsoft.icon" />
2894 <xs:enumeration value="vnd.sealedmedia.softseal.jpg" />1754 <xs:enumeration value="vnd.mix" />
2895 <xs:enumeration value="vnd.svf" />1755 <xs:enumeration value="vnd.ms-modi" />
2896 <xs:enumeration value="vnd.wap.wbmp" />1756 <xs:enumeration value="vnd.net-fpx" />
2897 <xs:enumeration value="vnd.xiff" />1757 <xs:enumeration value="vnd.sealed.png" />
2898 </xs:restriction>1758 <xs:enumeration value="vnd.sealedmedia.softseal.gif" />
2899 </xs:simpleType>1759 <xs:enumeration value="vnd.sealedmedia.softseal.jpg" />
2900 <xs:simpleType name="message-type">1760 <xs:enumeration value="vnd.svf" />
2901 <xs:restriction base="xs:token">1761 <xs:enumeration value="vnd.wap.wbmp" />
2902 <xs:enumeration value="CPIM" />1762 <xs:enumeration value="vnd.xiff" />
2903 <xs:enumeration value="delivery-status" />1763 </xs:restriction>
2904 <xs:enumeration value="disposition-notification" />1764 </xs:simpleType>
2905 <xs:enumeration value="example" />1765 <xs:simpleType name="message-type">
2906 <xs:enumeration value="external-body" />1766 <xs:restriction base="xs:token">
2907 <xs:enumeration value="global" />1767 <xs:enumeration value="CPIM" />
2908 <xs:enumeration value="global-delivery-status" />1768 <xs:enumeration value="delivery-status" />
2909 <xs:enumeration value="global-disposition-notification" />1769 <xs:enumeration value="disposition-notification" />
2910 <xs:enumeration value="global-headers" />1770 <xs:enumeration value="example" />
29111771 <xs:enumeration value="external-body" />
2912Cheney Standards Track [Page 52]1772 <xs:enumeration value="global" />
29131773 <xs:enumeration value="global-delivery-status" />
2914Internet-Draft Mail Markup Language - Version 1.0 April 20091774 <xs:enumeration value="global-disposition-notification" />
29151775 <xs:enumeration value="global-headers" />
2916 <xs:enumeration value="http" />1776 <xs:enumeration value="http" />
2917 <xs:enumeration value="news" />1777 <xs:enumeration value="news" />
2918 <xs:enumeration value="partial" />1778 <xs:enumeration value="partial" />
2919 <xs:enumeration value="rfc822" />1779 <xs:enumeration value="rfc822" />
2920 <xs:enumeration value="s-http" />1780 <xs:enumeration value="s-http" />
2921 <xs:enumeration value="sip" />1781 <xs:enumeration value="sip" />
2922 <xs:enumeration value="sipfrag" />1782 <xs:enumeration value="sipfrag" />
2923 <xs:enumeration value="tracking-status" />1783 <xs:enumeration value="tracking-status" />
2924 <xs:enumeration value="vnd.si.simp" />1784 <xs:enumeration value="vnd.si.simp" />
2925 </xs:restriction>1785 </xs:restriction>
2926 </xs:simpleType>1786 </xs:simpleType>
2927 <xs:simpleType name="model-type">1787 <xs:simpleType name="model-type">
2928 <xs:restriction base="xs:token">1788 <xs:restriction base="xs:token">
2929 <xs:enumeration value="example" />1789 <xs:enumeration value="example" />
2930 <xs:enumeration value="iges" />1790 <xs:enumeration value="iges" />
2931 <xs:enumeration value="mesh" />1791
2932 <xs:enumeration value="vnd.dwf" /> 1792Cheney Standards Track [Page 32]
2933 <xs:enumeration value="vnd.flatland.3dml" />1793
2934 <xs:enumeration value="vnd.gdl" /> 1794Internet-Draft Mail Markup Language - Version 1.0 February 2009
2935 <xs:enumeration value="vnd.gs-gdl" />1795
2936 <xs:enumeration value="vnd.gtw" />1796 <xs:enumeration value="mesh" />
2937 <xs:enumeration value="vnd.moml+xml" />1797 <xs:enumeration value="vnd.dwf" />
2938 <xs:enumeration value="vnd.mts" />1798 <xs:enumeration value="vnd.flatland.3dml" />
2939 <xs:enumeration value="vnd.parasolid.transmit.binary" />1799 <xs:enumeration value="vnd.gdl" />
2940 <xs:enumeration value="vnd.parasolid.transmit.text" />1800 <xs:enumeration value="vnd.gs-gdl" />
2941 <xs:enumeration value="vnd.vtu" />1801 <xs:enumeration value="vnd.gtw" />
2942 <xs:enumeration value="vrml" />1802 <xs:enumeration value="vnd.moml+xml" />
2943 </xs:restriction>1803 <xs:enumeration value="vnd.mts" />
2944 </xs:simpleType>1804 <xs:enumeration value="vnd.parasolid.transmit.binary" />
2945 <xs:simpleType name="multipart-type">1805 <xs:enumeration value="vnd.parasolid.transmit.text" />
2946 <xs:restriction base="xs:token">1806 <xs:enumeration value="vnd.vtu" />
2947 <xs:enumeration value="alternative" />1807 <xs:enumeration value="vrml" />
2948 <xs:enumeration value="appledouble" />1808 </xs:restriction>
2949 <xs:enumeration value="byteranges" />1809 </xs:simpleType>
2950 <xs:enumeration value="digest" />1810 <xs:simpleType name="multipart-type">
2951 <xs:enumeration value="encrypted" />1811 <xs:restriction base="xs:token">
2952 <xs:enumeration value="example" />1812 <xs:enumeration value="alternative" />
2953 <xs:enumeration value="form-data" />1813 <xs:enumeration value="appledouble" />
2954 <xs:enumeration value="header-set" />1814 <xs:enumeration value="byteranges" />
2955 <xs:enumeration value="mixed" />1815 <xs:enumeration value="digest" />
2956 <xs:enumeration value="parallel" />1816 <xs:enumeration value="encrypted" />
2957 <xs:enumeration value="related" />1817 <xs:enumeration value="example" />
2958 <xs:enumeration value="report" />1818 <xs:enumeration value="form-data" />
2959 <xs:enumeration value="signed" />1819 <xs:enumeration value="header-set" />
2960 <xs:enumeration value="voice-message" />1820 <xs:enumeration value="mixed" />
2961 </xs:restriction>1821 <xs:enumeration value="parallel" />
2962 </xs:simpleType>1822 <xs:enumeration value="related" />
2963 <xs:simpleType name="text-type">1823 <xs:enumeration value="report" />
2964 <xs:restriction base="xs:token">1824 <xs:enumeration value="signed" />
2965 <xs:enumeration value="calendar" />1825 <xs:enumeration value="voice-message" />
2966 <xs:enumeration value="css" />1826 </xs:restriction>
29671827 </xs:simpleType>
2968Cheney Standards Track [Page 53]1828 <xs:simpleType name="text-type">
29691829 <xs:restriction base="xs:token">
2970Internet-Draft Mail Markup Language - Version 1.0 April 20091830 <xs:enumeration value="calendar" />
29711831 <xs:enumeration value="css" />
2972 <xs:enumeration value="csv" />1832 <xs:enumeration value="csv" />
2973 <xs:enumeration value="directory" />1833 <xs:enumeration value="directory" />
2974 <xs:enumeration value="dns" />1834 <xs:enumeration value="dns" />
2975 <xs:enumeration value="enriched" />1835 <xs:enumeration value="enriched" />
2976 <xs:enumeration value="example" />1836 <xs:enumeration value="example" />
2977 <xs:enumeration value="html" />1837 <xs:enumeration value="html" />
2978 <xs:enumeration value="parityfec" />1838 <xs:enumeration value="parityfec" />
2979 <xs:enumeration value="plain" />1839 <xs:enumeration value="plain" />
2980 <xs:enumeration value="prs.fallenstein.rst" />1840 <xs:enumeration value="prs.fallenstein.rst" />
2981 <xs:enumeration value="prs.lines.tag" />1841 <xs:enumeration value="prs.lines.tag" />
2982 <xs:enumeration value="RED" />1842 <xs:enumeration value="RED" />
2983 <xs:enumeration value="rfc822-headers" />1843 <xs:enumeration value="rfc822-headers" />
2984 <xs:enumeration value="richtext" />1844 <xs:enumeration value="richtext" />
2985 <xs:enumeration value="rtf" />1845 <xs:enumeration value="rtf" />
2986 <xs:enumeration value="rtp-enc-aescm128" />1846 <xs:enumeration value="rtp-enc-aescm128" />
2987 <xs:enumeration value="rtx" />1847
2988 <xs:enumeration value="sgml" /> 1848Cheney Standards Track [Page 33]
2989 <xs:enumeration value="t140" />1849
2990 <xs:enumeration value="tab-separated-values" /> 1850Internet-Draft Mail Markup Language - Version 1.0 February 2009
2991 <xs:enumeration value="troff" />1851
2992 <xs:enumeration value="ulpfec" />1852 <xs:enumeration value="rtx" />
2993 <xs:enumeration value="uri-list" />1853 <xs:enumeration value="sgml" />
2994 <xs:enumeration value="vnd.abc" />1854 <xs:enumeration value="t140" />
2995 <xs:enumeration value="vnd.curl" />1855 <xs:enumeration value="tab-separated-values" />
2996 <xs:enumeration value="vnd.DMClientScript" />1856 <xs:enumeration value="troff" />
2997 <xs:enumeration value="vnd.esmertec.theme-descriptor" />1857 <xs:enumeration value="ulpfec" />
2998 <xs:enumeration value="vnd.fly" />1858 <xs:enumeration value="uri-list" />
2999 <xs:enumeration value="vnd.fmi.flexstor" />1859 <xs:enumeration value="vnd.abc" />
3000 <xs:enumeration value="vnd.graphviz" />1860 <xs:enumeration value="vnd.curl" />
3001 <xs:enumeration value="vnd.in3d.3dml" />1861 <xs:enumeration value="vnd.DMClientScript" />
3002 <xs:enumeration value="vnd.in3d.spot" />1862 <xs:enumeration value="vnd.esmertec.theme-descriptor" />
3003 <xs:enumeration value="vnd.IPTC.NewsML" />1863 <xs:enumeration value="vnd.fly" />
3004 <xs:enumeration value="vnd.IPTC.NITF" />1864 <xs:enumeration value="vnd.fmi.flexstor" />
3005 <xs:enumeration value="vnd.latex-z" />1865 <xs:enumeration value="vnd.graphviz" />
3006 <xs:enumeration value="vnd.motorola.reflex" />1866 <xs:enumeration value="vnd.in3d.3dml" />
3007 <xs:enumeration value="vnd.ms-mediapackage" />1867 <xs:enumeration value="vnd.in3d.spot" />
3008 <xs:enumeration value="vnd.net2phone.commcenter.command" />1868 <xs:enumeration value="vnd.IPTC.NewsML" />
3009 <xs:enumeration value="vnd.si.uricatalogue" />1869 <xs:enumeration value="vnd.IPTC.NITF" />
3010 <xs:enumeration value="vnd.sun.j2me.app-descriptor" />1870 <xs:enumeration value="vnd.latex-z" />
3011 <xs:enumeration value="vnd.trolltech.linguist" />1871 <xs:enumeration value="vnd.motorola.reflex" />
3012 <xs:enumeration value="vnd.wap.si" />1872 <xs:enumeration value="vnd.ms-mediapackage" />
3013 <xs:enumeration value="vnd.wap.sl" />1873 <xs:enumeration value="vnd.net2phone.commcenter.command" />
3014 <xs:enumeration value="vnd.wap.wml" />1874 <xs:enumeration value="vnd.si.uricatalogue" />
3015 <xs:enumeration value="vnd.wap.wmlscript" />1875 <xs:enumeration value="vnd.sun.j2me.app-descriptor" />
3016 <xs:enumeration value="xml" />1876 <xs:enumeration value="vnd.trolltech.linguist" />
3017 <xs:enumeration value="xml-external-parsed-entity" />1877 <xs:enumeration value="vnd.wap.si" />
3018 </xs:restriction>1878 <xs:enumeration value="vnd.wap.sl" />
3019 </xs:simpleType>1879 <xs:enumeration value="vnd.wap.wml" />
3020 <xs:simpleType name="video-type">1880 <xs:enumeration value="vnd.wap.wmlscript" />
3021 <xs:restriction base="xs:token">1881 <xs:enumeration value="xml" />
3022 <xs:enumeration value="3gpp" />1882 <xs:enumeration value="xml-external-parsed-entity" />
30231883 </xs:restriction>
3024Cheney Standards Track [Page 54]1884 </xs:simpleType>
30251885 <xs:simpleType name="video-type">
3026Internet-Draft Mail Markup Language - Version 1.0 April 20091886 <xs:restriction base="xs:token">
30271887 <xs:enumeration value="3gpp" />
3028 <xs:enumeration value="3gpp2" />1888 <xs:enumeration value="3gpp2" />
3029 <xs:enumeration value="3gpp-tt" />1889 <xs:enumeration value="3gpp-tt" />
3030 <xs:enumeration value="BMPEG" />1890 <xs:enumeration value="BMPEG" />
3031 <xs:enumeration value="BT656" />1891 <xs:enumeration value="BT656" />
3032 <xs:enumeration value="CelB" />1892 <xs:enumeration value="CelB" />
3033 <xs:enumeration value="DV" />1893 <xs:enumeration value="DV" />
3034 <xs:enumeration value="example" />1894 <xs:enumeration value="example" />
3035 <xs:enumeration value="H261" />1895 <xs:enumeration value="H261" />
3036 <xs:enumeration value="H263" />1896 <xs:enumeration value="H263" />
3037 <xs:enumeration value="H263-1998" />1897 <xs:enumeration value="H263-1998" />
3038 <xs:enumeration value="H263-2000" />1898 <xs:enumeration value="H263-2000" />
3039 <xs:enumeration value="H264" />1899 <xs:enumeration value="H264" />
3040 <xs:enumeration value="JPEG" />1900 <xs:enumeration value="JPEG" />
3041 <xs:enumeration value="MJ2" />1901 <xs:enumeration value="MJ2" />
3042 <xs:enumeration value="MP1S" />1902 <xs:enumeration value="MP1S" />
3043 <xs:enumeration value="MP2P" />1903
3044 <xs:enumeration value="MP2T" /> 1904Cheney Standards Track [Page 34]
3045 <xs:enumeration value="mp4" />1905
3046 <xs:enumeration value="MP4V-ES" /> 1906Internet-Draft Mail Markup Language - Version 1.0 February 2009
3047 <xs:enumeration value="MPV" />1907
3048 <xs:enumeration value="mpeg" />1908 <xs:enumeration value="MP2P" />
3049 <xs:enumeration value="mpeg4-generic" />1909 <xs:enumeration value="MP2T" />
3050 <xs:enumeration value="nv" />1910 <xs:enumeration value="mp4" />
3051 <xs:enumeration value="ogg" />1911 <xs:enumeration value="MP4V-ES" />
3052 <xs:enumeration value="parityfec" />1912 <xs:enumeration value="MPV" />
3053 <xs:enumeration value="pointer" />1913 <xs:enumeration value="mpeg" />
3054 <xs:enumeration value="quicktime" />1914 <xs:enumeration value="mpeg4-generic" />
3055 <xs:enumeration value="raw" />1915 <xs:enumeration value="nv" />
3056 <xs:enumeration value="rtp-enc-aescm128" />1916 <xs:enumeration value="ogg" />
3057 <xs:enumeration value="rtx" />1917 <xs:enumeration value="parityfec" />
3058 <xs:enumeration value="SMTPE292M" />1918 <xs:enumeration value="pointer" />
3059 <xs:enumeration value="ulpfec" />1919 <xs:enumeration value="quicktime" />
3060 <xs:enumeration value="vc1" />1920 <xs:enumeration value="raw" />
3061 <xs:enumeration value="vnd.CCTV" />1921 <xs:enumeration value="rtp-enc-aescm128" />
3062 <xs:enumeration value="vnd.dlna.mpeg-tts" />1922 <xs:enumeration value="rtx" />
3063 <xs:enumeration value="vnd.fvt" />1923 <xs:enumeration value="SMTPE292M" />
3064 <xs:enumeration value="vnd.hns.video" />1924 <xs:enumeration value="ulpfec" />
3065 <xs:enumeration value="vnd.iptvforum.1dparityfec-1010" />1925 <xs:enumeration value="vc1" />
3066 <xs:enumeration value="vnd.iptvforum.1dparityfec-2005" />1926 <xs:enumeration value="vnd.CCTV" />
3067 <xs:enumeration value="vnd.iptvforum.2dparityfec-1010" />1927 <xs:enumeration value="vnd.dlna.mpeg-tts" />
3068 <xs:enumeration value="vnd.iptvforum.2dparityfec-2005" />1928 <xs:enumeration value="vnd.fvt" />
3069 <xs:enumeration value="vnd.iptvforum.ttsavc" />1929 <xs:enumeration value="vnd.hns.video" />
3070 <xs:enumeration value="vnd.iptvforum.ttsmpeg2" />1930 <xs:enumeration value="vnd.iptvforum.1dparityfec-1010" />
3071 <xs:enumeration value="vnd.motorola.video" />1931 <xs:enumeration value="vnd.iptvforum.1dparityfec-2005" />
3072 <xs:enumeration value="vnd.motorola.videop" />1932 <xs:enumeration value="vnd.iptvforum.2dparityfec-1010" />
3073 <xs:enumeration value="vnd.mpegurl" />1933 <xs:enumeration value="vnd.iptvforum.2dparityfec-2005" />
3074 <xs:enumeration value="vnd.ms-playready.mediapyv" />1934 <xs:enumeration value="vnd.iptvforum.ttsavc" />
3075 <xs:enumeration value="vnd.nokia.interleaved-multimedia" />1935 <xs:enumeration value="vnd.iptvforum.ttsmpeg2" />
3076 <xs:enumeration value="vnd.nokia.videovoip" />1936 <xs:enumeration value="vnd.motorola.video" />
3077 <xs:enumeration value="vnd.objectvideo" />1937 <xs:enumeration value="vnd.motorola.videop" />
3078 <xs:enumeration value="vnd.sealed.mpeg1" />1938 <xs:enumeration value="vnd.mpegurl" />
30791939 <xs:enumeration value="vnd.ms-playready.mediapyv" />
3080Cheney Standards Track [Page 55]1940 <xs:enumeration value="vnd.nokia.interleaved-multimedia" />
30811941 <xs:enumeration value="vnd.nokia.videovoip" />
3082Internet-Draft Mail Markup Language - Version 1.0 April 20091942 <xs:enumeration value="vnd.objectvideo" />
30831943 <xs:enumeration value="vnd.sealed.mpeg1" />
3084 <xs:enumeration value="vnd.sealed.mpeg4" />1944 <xs:enumeration value="vnd.sealed.mpeg4" />
3085 <xs:enumeration value="vnd.sealed.swf" />1945 <xs:enumeration value="vnd.sealed.swf" />
3086 <xs:enumeration value="vnd.sealedmedia.softseal.mov" />1946 <xs:enumeration value="vnd.sealedmedia.softseal.mov" />
3087 <xs:enumeration value="vnd.vivo" />1947 <xs:enumeration value="vnd.vivo" />
3088 </xs:restriction>1948 </xs:restriction>
3089 </xs:simpleType>1949 </xs:simpleType>
3090 <xs:group name="super-types">1950 <xs:group name="super-types">
3091 <xs:choice>1951 <xs:choice>
3092 <xs:element name="application" type="application-type" />1952 <xs:element name="application" type="application-type" />
3093 <xs:element name="audio" type="audio-type" />1953 <xs:element name="audio" type="audio-type" />
3094 <xs:element name="example" type="example-type" />1954 <xs:element name="example" type="example-type" />
3095 <xs:element name="image" type="image-type" />1955 <xs:element name="image" type="image-type" />
3096 <xs:element name="message" type="message-type" />1956 <xs:element name="message" type="message-type" />
3097 <xs:element name="model" type="model-type" />1957 <xs:element name="model" type="model-type" />
3098 <xs:element name="multipa t" type="multipart-type" />1958 <xs:element name="multipa t" type="multipart-type" />
1959
1960Cheney Standards Track [Page 35]
1961
1962Internet-Draft Mail Markup Language - Version 1.0 February 2009
1963
3099 <xs:element name="text" type="text-type" />1964 <xs:element name="text" type="text-type" />
3100 <xs:element name="video" type="video-type" />1965 <xs:element name="video" type="video-type" />
3101 </xs:choice>1966 </xs:choice>
3102 </xs:group>1967 </xs:group>
3103 <xs:complexType name="mime-type">1968 <xs:complexType name="mime-type">
3104 <xs:group ref="super-types" />1969 <xs:group ref="super-types" />
3105 </xs:complexType>1970 </xs:complexType>
3106</xs:schema>1971</xs:schema>
31071972
31088. MML Schema19736. MML Schema
3109<?xml version="1.0" encoding="utf-8"?><xs:schema 1974<?xml version="1.0" encoding="utf-8" ?><xs:schema
3110 xmlns:xfm="http://www.w3.org/2002/xforms" version="1.1"1975 xmlns:xfm="http://www.w3.org/2002/xforms"
1976 elementFormDefault="qualified" version="1.1"
3111 xmlns:xs="http://www.w3.org/2001/XMLSchema"><xs:import1977 xmlns:xs="http://www.w3.org/2001/XMLSchema"><xs:import
3112 schemaLocation="http://www.w3.org/MarkUp/Forms/2002/XForms-Schema.xsd"1978 schemaLocation="http://www.w3.org/MarkUp/Forms/2002/XForms-Schema.xsd"
3113 namespace="http://www.w3.org/2002/xforms" /><xs:import1979 namespace="http://www.w3.org/2002/xforms" />
3114 schemaLocation="http://www.w3.org/2001/XMLSchema.xsd"
3115 namespace="http://www.w3.org/2001/XMLSchema" />
3116 <xs:include schemaLocation="http://mailmarkup.org/mime.xsd" />1980 <xs:include schemaLocation="http://mailmarkup.org/mime.xsd" />
3117 <xs:element name="mail">1981 <xs:element name="mail">
3118 <xs:complexType>1982 <xs:complexType>
3119 <xs:sequence>1983 <xs:sequence>
3120 <xs:element maxOccurs="unbounded" ref="session" />1984 <xs:element maxOccurs="unbounded" ref="session" />
3121 </xs:sequence>1985 </xs:sequence>
3122 <xs:attribute ref="mail-type" use="required" />1986 <xs:attribute ref="mail-type" use="required" />
3123 <xs:attribute ref="version" use="required" />1987 <xs:attribute fixed="http://mailmarkup.org/"
1988     name="targetNamespace" use="required" />
3124 </xs:complexType>1989 </xs:complexType>
3125 </xs:element>1990 </xs:element>
3126 <xs:attribute fixed="application/mail" name="mail-type" />
3127 <xs:attribute fixed="1.0" name="version" />
3128 <xs:element name="session">
3129 <xs:complexType>
3130 <xs:sequence>
3131 <xs:element minOccurs="0" maxOccurs="unbounded"
3132 ref="xs:import" />
3133 <xs:element minOccurs="0" maxOccurs="unbounded"
3134 ref="xs:include" />
3135
3136Cheney Standards Track [Page 56]1991 <xs:attribute fixed="application/mail" name="mail-type" />
31371992 <xs:element name="session">
3138Internet-Draft Mail Markup Language - Version 1.0 April 20091993 <xs:complexType>
31391994 <xs:sequence>
3140 <xs:element ref="address" />1995 <xs:element ref="address" />
3141 <xs:element minOccurs="0" ref="attachments" />1996 <xs:element minOccurs="0" ref="attachments" />
3142 <xs:element ref="subject" />1997 <xs:element ref="subject" />
3143 <xs:element minOccurs="0" ref="presentation" />1998 <xs:element minOccurs="0" ref="presentation" />
3144 <xs:choice>1999 <xs:choice>
3145 <xs:element ref="source" />2000 <xs:element ref="source" />
3146 <xs:element ref="plain-text" />2001 <xs:element ref="plain-text" />
3147 <xs:element ref="markup" />2002 <xs:element ref="markup" />
3148 </xs:choice>2003 </xs:choice>
3149 </xs:sequence>2004 </xs:sequence>
3150 <xs:attribute ref="time-stamp" use="required" />2005 <xs:attribute ref="time-stamp" use="required" />
3151 <xs:attribute default="en" ref="language" use="optional" />2006 <xs:attribute default="en" ref="language" use="optional" />
3152 </xs:complexType>2007 </xs:complexType>
3153 </xs:element&