idnits 2.17.1 draft-nelson-model-mail-ext-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 4 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** There is 1 instance of lines with control characters in the document. == There is 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 1996) is 10298 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 446 looks like a reference -- Missing reference section? '11' on line 501 looks like a reference -- Missing reference section? '14' on line 514 looks like a reference -- Missing reference section? '8' on line 488 looks like a reference -- Missing reference section? '9' on line 492 looks like a reference -- Missing reference section? '10' on line 496 looks like a reference -- Missing reference section? '2' on line 451 looks like a reference -- Missing reference section? '3' on line 460 looks like a reference -- Missing reference section? '4' on line 465 looks like a reference -- Missing reference section? '5' on line 469 looks like a reference -- Missing reference section? '6' on line 480 looks like a reference -- Missing reference section? '7' on line 483 looks like a reference -- Missing reference section? '12' on line 504 looks like a reference -- Missing reference section? '13' on line 510 looks like a reference -- Missing reference section? '2-7' on line 564 looks like a reference Summary: 10 errors (**), 0 flaws (~~), 2 warnings (==), 18 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group S. D. Nelson 2 Internet Draft Lawrence Livermore National Laboratory 3 Livermore, CA 94550, USA. 4 C. Parks 5 National Institute of Standards and Technology 6 Gaithersburg, MD 20899, USA. 7 Mitra 8 WorldMaker 9 1056 Noe, San Francisco, CA 94114 10 February 1996 11 Expires in six months 13 The Model Primary Content Type for 14 Multipurpose Internet Mail Extensions 15 17 Status of this Memo 19 This document specifies an Internet standards track protocol for 20 the Internet community, and requests discussion and suggestions 21 for improvements. Please refer to the current edition of the 22 "Internet Official Protocol Standards" (STD 1) for the 23 standardization state and status of this protocol. Distribution 24 of this memo is unlimited. 26 The original version of this draft benefitted from discussions 27 between the authors and their respective communities. 29 Draft documents are valid for a maximum of six months and may be 30 updated, replaced, or obsoleted by other documents at any time. 31 It is inappropriate to use draft documents as reference material 32 or to cite them other than as ``work in progress.'' 34 To learn the current status of any Internet-Draft, please check 35 the ``1id-abstracts.txt'' listing contained in the Internet-Drafts 36 Shadow Directories on ds.internic.net (US East Coast), 37 nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or 38 munnari.oz.au (Pacific Rim). 40 Introduction 42 The purpose of this Internet Draft is to propose an update to 43 Internet RFC 1521 to include a new primary content-type to be 44 known as "model". RFC 1521[1] describes mechanisms for specifying 45 and describing the format of Internet Message Bodies via 46 content-type/subtype pairs. We believe that "model" defines a 47 fundamental type of content with unique presentational, hardware, 48 and processing aspects. Various subtypes of this primary type are 49 immediately anticipated but will be covered under separate 50 documents. 52 Internet-draft Model Primary MIME Type February 1996 54 Table of Contents: 56 1. Overview 57 2. Definition 58 3. Consultation Mechanisms 59 4. Encoding and Transport 60 5. Security Considerations Section 61 6. Authors' Addresses 62 7. Expected subtypes 63 8. Appendix 64 9. Acknowledgements 66 1. Overview 68 This document will outline what a model is, show examples of models, 69 and discuss the benifits of grouping models together. This document 70 will not directly deal with the intended subtypes since those will be 71 covered by their seperate registrations. Some immediately expected 72 subtypes are listed in section 7. 74 This document is a discussion document for an agreed definition, 75 intended eventually to form a standard accepted extension to RFC 1521. 76 We are also targeting developers of input/output filters, viewer 77 software and hardware, those involved in MIME transport, and decoders. 79 2. Definition of a model 81 Each subtype in the model structure has unique features, just as 82 does each subtype in the other primary types. The important fact is 83 that these various subtypes can be converted between each other with 84 less loss of information then to that of other primary types. This 85 fact groups these subtypes together into the model primary type. All 86 of the expected subtypes have several features in common and that are 87 unique to this primary type: 89 1. have 3 or more dimensions which are bases of the system and 90 form an orthogonal coordinate system (any orthogonal system is 91 sufficient). 93 2. contains a structural relationship between model elements. 95 3. have calibration factors to physical units (force, momentum, 96 time, velocity, acceleration, size, etc.). Thus, an IGES file 97 will specify a building of non-arbitrary size, computational 98 meshes and VRML models will have real spatial/ temporal units. 99 This allows for differing elements to be combined 100 non-arbitrarily. 102 Internet-draft Model Primary MIME Type February 1996 104 4. Models can also be single descriptive objects or composed of a 105 collection of objects. These normally independent objects are 106 arranged in a master/slave scenario so that one object acts as 107 the reference which defines how the other objects interrelate 108 and behave. This allows for the creation of mathematical, 109 physical, economic, behaviorial, etc. models which typically are 110 composed of diferent elements. The key is in the description: 111 these types describe how something ``behaves''; contrasted to 112 typical data types which describe how something ``is''. 114 The inclusion of this "collective" system works similar to the 115 Email system's multipart/related type which defines the actions 116 of the individual parts. Further specification of the model/* 117 subtypes utilizing these properties is left to the subtype 118 authors. 120 With these assumptions: 122 a. the default dimensionality will be spatial and temporal (but 123 any are allowed). 125 b. it is presumed that models will contain underlying structure 126 which may or may not be immediately available to the 127 user. (fluid dynamics vector fields, electromagnetic 128 propagation, interrelated IGES dimensional specifiers, VRML 129 materials and operators, etc.) 131 c. it is assumed that basis set conversion between model domains 132 is lossless. The interpretation of the data may change but 133 the specification will not. i.e. convert the model of the 134 U.S.A. Gross Domestic Product into a VRML model and navigate 135 it to explore the variances and interrelationships. The model 136 has many dimensions but also ``passages'' and ``corridors'' 137 linking different parts of it. A similar situation is true 138 for meshes and CAD files. The key is identifying the basis set 139 conversion which makes sense. 141 d. models are grouped to assure LESS loss of information between 142 the model subtypes than to subtypes of other primary 143 types. (i.e. converting a chemical model into an image is 144 more lossy than concerting it into a VRML model). 146 Items c and d above define the grouping for model similar to the 147 way that ``images'' and ``videos'' are grouped together; to 148 assure less loss of information. Obviously converting from a GIF 149 image to a JPEG image looses less information than converting from 150 a GIF image to an AU audio file. 152 Internet-draft Model Primary MIME Type February 1996 154 3. Consultation Mechanisms. 156 Before proposing a subtype for the model/* primary type, it is 157 suggested that the subtype author examine the definition (above) 158 of what a model/* is and the listing (below) of what a model/* is 159 not. Additional consultations with the authors of the existing 160 model/* subtypes is also suggested. 162 Copies of Internet drafts and RFCs are available on: 164 ftp://ftp.isi.edu/in-notes/ 166 Similarly, the VRML discussion list has been archived as: 168 http://vrml.wired.com/arch/ 170 and discussions on the comp.mail.mime group may be of interest. 171 Discussion digests for the existing model/* subtypes may be 172 referenced in the respective documents. 174 The mesh community presently has numerous different mesh 175 geometries as part of different packages. Freely available 176 libraries need to be advertised more than they have been in the 177 past to spur the development of interoperable packages. It is 178 hoped that by following the example of the VRML community and 179 creating a freely available comprehensive library of input/output 180 functions for meshes[11] that this problem will be alleviated for 181 the mesh community. A freely available mesh viewer conforming to 182 these standards is available now for various platforms. 183 Consulations with the authors of the mesh system, 185 http://www-dsed.llnl.gov/documents/test/mesh.html 187 will be benificial. 189 The IGES community has a suite of tests and conformance utilities 190 to gauge the conformance to specifications and software authors 191 are encouraged to seek those out from NIST[14]. 193 4. Encoding and Transport 195 a. A parameter which makes sense for all subtypes of model is the 196 initial viewing condition, consisting of the view position (a 197 3D point), the view vector, and the up vector. This parameter 198 is optional. Some subtypes will contain one or more viewing 199 conditions as part of there internal data. If present, this 200 parameter over-rides any internal viewing condition. Note 201 that these parameters are not specific to visualizations on 202 computer screens but also the default fabrication orientation 203 on milling machines. 205 Internet-draft Model Primary MIME Type February 1996 207 b. Unrecognized subtypes of model should at a minimum be treated 208 as "application/octet-stream". Implementations may optionally 209 elect to pass subtypes of model that they do not specifically 210 recognize to a robust general-purpose model viewing 211 application, if such an application is available. 213 c. Different subtypes of model may be encoded as textual 214 representations or as binary data. Unless noted in the 215 subtype registration, subtypes of model should be assumed to 216 contain binary data, implying a content encoding of base64 for 217 email and binary transfer for ftp and http. 219 d. The formal syntax for the subtypes of the model primary type 220 should look like this: 222 MIME type name: model 223 MIME subtype name: xxxxxxxx 224 Required parameters: none 225 Optional parameters: dimensionality, static/dynamic, def. view 226 Encoding considerations: may be encoded 227 Security considerations: see section 5 below 228 Published specification: see Appendix B for references 229 Person and email address to contact for further information: 230 S. D. Nelson 232 5. Security Considerations Section 234 Note that the data files are ``read-only'' and do not contain file 235 system modifiers or batch/macro commands. The transported data is 236 not self-modifying but may contain interrelationships. The data 237 files may however contain a ``default view'' which is added by the 238 author at file creation time. This ``default view'' may 239 manipulate viewer variables, default look angle, lighting, 240 visualization options, etc. This visualization may also involve 241 the computation of variables or values for display based on the 242 given raw data. For motorized equipment, this may change the 243 position from the hardware's rest state to the object's starting 244 orientation. 246 The internal structure of the data files may direct agents to 247 access additional data from the network (i.e. inclusions); the 248 security limits of whom are not pre-supposed. Actions based on 249 these inclusions are left to the security definitions of the 250 inclusions. Further comments about the security considerations 251 for the subtypes will be contained in each subtype's registration. 253 Internet-draft Model Primary MIME Type February 1996 255 6. Authors' Addresses. 257 S. D. Nelson, Lawrence Livermore National Laboratory, 258 7000 East Ave., L-153, Livermore CA 94550, USA. 259 E-Mail: nelson18@llnl.gov 261 C. Parks, National Institute of Standards & Technology 262 Bldg 220, Room B-344, Gaithersburg, MD 20899, USA. 263 E-Mail: parks@eeel.nist.gov 265 Mitra, WorldMaker, 266 1056 Noe, San Francisco, CA 94114 267 E-Mail: mitra@earth.path.net 269 7. Expected subtypes 271 Table 1 lists some of the expected model sub-type names. Suggested 272 3 letter extensions are also provided for DOS compatibility but their 273 need is hopefully diminished by the use of more robust operating 274 systems on PC platforms. The ``silo'' extension is provided for 275 backwards compatibility. Mesh has an extensive list of hints since the 276 present variability is so great. In the future, the need for 277 these hints will diminish since the files are selfdescribing. 278 This document is not registering these subtypes. They will be 279 handled under separate documents. 281 Table 1. 283 Primary/sub-type Suggested extension(s) Reference 285 model/iges igs,iges [8] 286 model/vrml wrl [9] 287 model/mesh msh, mesh, silo [10] 289 It is expected that model/mesh will also make use of a number 290 of parameters which will help the end user determine the data 291 type without examinine the data. However, note that mesh files 292 are self-describing. 294 regular+static, unstructed+static, unstructured+dynamic, 295 conformal+static, conformal+dynamic, isoparametric+static, 296 isoparametric+dynamic 298 The sub-types listed above are some of the anticipated types that are 299 already in use. Notice that the IGES type is already registered 300 as "application/iges" and that RFC states that a more appropriate 301 type is desired. Note that the author of "application/iges" is 302 one of the authors of this "model" submission and application/iges 303 will be re-registered as model/iges at the appropriate time. 305 Internet-draft Model Primary MIME Type February 1996 307 The VRML type is gaining wide acceptance and has numerous parallel 308 development efforts for different platforms. These efforts are 309 fueled by the release of the QvLib library for reading VRML files; 310 without which the VRML effort would be less further along. This 311 has allowed for a consistent data type and has by defacto 312 established a set of standards. Further VRML efforts include 313 interfaces to other kinds of hardware (beyond just visual 314 displays) and it is proposed by those involved in the VRML effort 315 to encompass more of the five senses. Unlike other kinds of 316 "reality modeling" schemes, VRML is not proprietary to any one 317 vendor and should experience similar growth as do other open 318 standards. 320 The mesh type is an offshoot of existing computational meshing 321 efforts and, like VRML, builds on a freely available library set. 322 Also like VRML, there are other proprietary meshing systems but 323 there are converters which will convert from those closed systems 324 to the mesh type. Meshes in general have an association feature 325 so that the connectivity between nodes is maintained. It should be 326 noted that most modern meshes are derived from CAD solids files. 328 8. Appendices 330 8.1 Appendix A -- extraneous details about expected subtypes 332 VRML Data Types 334 The 3D modeling and CAD communities use a number of file 335 formats to represent 3D models, these formats are widely used 336 to exchange information, and full, or lossy, converters 337 between the formats exist both independently and integrated 338 into widely used applications. The VRML format is rapidly 339 becoming a standard for the display of 3D information on the 340 WWW. 342 Mesh Data Types 344 For many decades, finite element and finite difference time domain 345 codes have generated mesh structures which attempt to use the 346 physical geometry of the structures in connection with various 347 physics packages to generate real world simulations of events 348 including electromagnetic wave propagation, fluid dynamics, motor 349 design, etc. The resulting output data is then post processed to 350 examine the results in a variety of forms. This proposed mesh 351 subtype will include both geometry and scalar/vector/tensor 352 results data. An important point to note is that many modern 353 meshes are generated from solids constructed using CAD packages. 355 Internet-draft Model Primary MIME Type February 1996 357 Motivation for mesh grew out of discussions with other 358 communities about their design requirements. Many CAD or scene 359 descriptions are composed of a small number of complex objects 360 while computational meshes are composed of large numbers of 361 simple objects. A 1,000,000 element 3D mesh is small. A 362 100,000,000 element 3D structured mesh is large. Each object can 363 also have an arbitrary amount of associated data and the mesh 364 connectivity information is important in optimizing usage of the 365 mesh. Also, the mesh itself is usually uninteresting but 366 postprocessing packages may act on the underlying data or a 367 computational engine may process the data as input. 369 Meshes differ principally from other kinds of scenes in that 370 meshes are composed of a large number of simple objects which may 371 contain arbitrary non-spatial parameters, not all of whom need be 372 visible, and who have an implicit connectivity and neighbor list. 373 This latter point is the key feature of a mesh. It should be 374 noted that most meshes are generated from CAD files however. The 375 mesh type has association functions because the underlying 376 physics was used to calculate the interaction (if you crash a car 377 into a telephone pole, you get a crumpled car and a bent pole). 378 Most interesting computational meshes are 4D with additional 379 multidimensional results components. 381 IGES CAD Data Types 383 (The following text, reproduced for reference purposes only, is from 384 ``U.S. Product Data Association and IGES/PDES Organization Reference 385 Manual,'' June 1995; by permission.) 387 IGES, the Initial Graphics Exchange Specification, defines a 388 neutral data format that allows for the digital exchange of 389 information among computer-aided design (CAD) systems. 391 CAD systems are in use today in increasing numbers for 392 applications in all phases of the design, analysis, and 393 manufacture and testing of products. Since the designer may use 394 one supplier's system while the contractor and subcontractor may 395 use other systems, there is a need to be able to exchange data 396 digitally among all CAD systems. 398 The databases of CAD systems from different vendors often 399 represent the same CAD constructs differently. A circular arc on 400 one system may be defined by a center point, its starting point 401 and end point, while on another it is defined by its center, its 402 diameter starting and ending angle. IGES enables the exchange of 403 such data by providing, in the public domain, a neutral definition 404 and format for the exchange of such data. 406 Internet-draft Model Primary MIME Type February 1996 408 Using IGES, the user can exchange product data models in the form 409 of wireframe, surface, or solid representations as well as surface 410 representations. Translators convert a vendor's proprietary 411 internal database format into the neutral IGES format and from the 412 IGES format into another vendor's internal database. The 413 translators, called pre- and post-processors, are usually 414 available from vendors as part of their product lines. 416 Applications supported by IGES include traditional engineering 417 drawings as well as models for analysis and/or various 418 manufacturing functions. In addition to the general specification, 419 IGES also includes application protocols in which the standard is 420 interpreted to meet discipline specific requirements. 422 IGES technology assumes that a person is available on the 423 receiving end to interpret the meaning of the product model 424 data. For instance, a person is needed to determine how many holes 425 are in the part because the hole itself is not defined. It is 426 represented in IGES by its component geometry and therefore, is 427 indistinguishable from the circular edges of a rod. 429 The IGES format has been registered with the Internet Assigned 430 Numbers Authority (IANA) as a Multipurpose Internet Mail Extension 431 (MIME) type "application/iges". The use of the message 432 type/subtype in Internet messages facilitates the uniform 433 recognition of an IGES file for routing to a viewer or translator. 435 Version 1.0 of the specification was adopted as an American 436 National Standards (ANS Y14.26M-1981) in November of 437 1981. Versions 3.0 and 4.0 of the specification have subsequently 438 been approved by ANSI. The current version of IGES 5.2 was 439 approved by ANSI under the new guidelines of the U.S. Product Data 440 Association. Under these guidelines, the IGES/PDES Organization 441 (IPO) became the accredited standards body for product data 442 exchange standards. This latest standard is USPRO/IPO-100-1993. 444 8.2 Appendix B -- References and Citations 446 [1] N. Borenstein, and N. Freed, "MIME (Multipurpose Internet Mail 447 Extensions) Part One: Mechanisms for Specifying and Describing the 448 Format of Internet Message Bodies", RFC 1521, Bellcore, Innosoft, 449 September 1993. 451 [2] Fitzgerald P., "Molecules-R-Us Interface to the Brookhaven 452 Data Base", Computational Molecular Biology Section, National 453 Institutes of Health, USA; see http://www.nih.gov/htbin/pdb for 454 further details; Peitsch M.C, Wells T.N.C., Stampf D.R., Sussman 455 S. J., "The Swiss-3D Image Collection And PDP-Browser On The 456 Worldwide Web", Trends In Biochemical Sciences, 1995, 20, 82. 458 Internet-draft Model Primary MIME Type February 1996 460 [3] "Proceedings of the First Electronic Computational Chemistry 461 Conference", Eds. Bachrach, S. M., Boyd D. B., Gray S. K, Hase W., 462 Rzepa H.S, ARInternet: Landover, Nov. 7- Dec. 2, 1994, in press; 463 Bachrach S. M, J. Chem. Inf. Comp. Sci., 1995, in press. 465 [4] Richardson D.C., and Richardson J.S., Protein Science, 1992, 466 1, 3; D. C. Richardson D. C., and Richardson J.S., Trends in 467 Biochem. Sci.,1994, 19, 135. 469 [5] Rzepa H. S., Whitaker B. J., and Winter M. J., "Chemical 470 Applications of the World-Wide-Web", J. Chem. Soc., Chem. Commun., 471 1994, 1907; Casher O., Chandramohan G., Hargreaves M., Murray-Rust 472 P., Sayle R., Rzepa H.S., and Whitaker B. J., "Hyperactive 473 Molecules and the World-Wide-Web Information System", 474 J. Chem. Soc., Perkin Trans 2, 1995, 7; Baggott J., "Biochemistry 475 On The Web", Chemical & Engineering News, 1995, 73, 36; Schwartz 476 A.T, Bunce D.M, Silberman R.G, Stanitski C.L, Stratton W.J, Zipp 477 A.P, "Chemistry In Context - Weaving The Web", Journal Of Chemical 478 Education, 1994, 71, 1041. 480 [6] Rzepa H.S., "WWW94 Chemistry Workshop", Computer Networks and 481 ISDN Systems, 1994, 27, 317 and 328. 483 [7] S.D. Nelson, "Email MIME test page", Lawrence Livermore 484 National Laboratory, 1994. See 485 http://www-dsed.llnl.gov/documents/WWWtest.html and 486 http://www-dsed.llnl.gov/documents/tests/email.html 488 [8] C. Parks, "Registration of new Media Type application/iges", 489 ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/ 490 application/iges, 1995. 492 [9] G. Bell, A. Parisi, M. Pesce, "The Virtual Reality Modeling 493 Language", 494 http://sdsc.edu/SDSC/Partners/vrml/Archives/vrml10-3.html, 1995. 496 [10] S.D. Nelson, "Registration of new Media Type model/mesh", 497 (will be) 498 ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/model/ 499 mesh, 1995. 501 [11] "SILO User's Guide", Lawrence Livermore National Laboratory, 502 University of California, UCRL-MA-118751, March 7, 1995, 504 [12] E. Brugger, "Mesh-TV: a graphical analysis tool", Lawrence 505 Livermore National Laboratory, University of California, 506 UCRL-TB-115079-8, http://www.llnl.gov/liv_comp/meshtv/mesh.html 508 Internet-draft Model Primary MIME Type February 1996 510 [13] S. Brown, "Portable Application Code Toolkit (PACT)", the 511 printed documentation is accessible from the PACT Home Page 512 http://www.llnl.gov/def_sci/pact/pact_homepage.html 514 [14] L. Rosenthal, ``Initial Graphics Exchange Specification 515 (IGES) Test Service'', 516 http://speckle.ncsl.nist.gov/~jacki/igests.htm 518 8.3 Appendix C -- hardware 520 Numerous kinds of hardware already exist which can process some 521 of the expected model data types and are listed here for illustration 522 purposes only: 524 stereo glasses, 3D lithography machines, automated manufacturing 525 systems, data gloves (with feedback), milling machines, 526 aromascopes, treadmills. 528 8.4 Appendix D -- Examples 530 This section contains a collection of various pointers to 531 examples of what the model type encompasses: 533 Example mesh model objects can be found on this mesh page: 534 http://www-dsed.llnl.gov/documents/tests/mesh.html 536 Various IGES compliant test objects: 537 http://www.eeel.nist.gov/iges/specfigures/index.html 539 VRML Test Suite: 540 http://www.chaco.com/vrml/test/ 542 An image of a model of a shipping cage crashing into the ground: 543 http://www.llnl.gov/liv_comp/meiko/apps/dyna3d/cagefig2.gif 545 An image of a 100,000,000 zone mesh: 546 http://www.llnl.gov/liv_comp/meiko/apps/hardin/PMESH.gif 548 A video of a seismic wave propagation through a computational mesh: 549 http://www.llnl.gov/liv_comp/meiko/apps/larsen/movie.mpg 551 Internet-draft Model Primary MIME Type February 1996 553 9. Acknowledgements 555 Thanks go to Henry Rzepa (h.rzepa@ic.ac.uk), Peter Murray-Rust 556 (pmr1716@ggr.co.uk), Benjamin Whitaker 557 (B.J.Whitaker@chemistry.leeds.ac.uk), Bill Ross 558 (ross@cgl.ucsf.EDU), and others in the chemical community on which 559 the initial draft of this document is based. That document 560 updated IETF Internet Draft, draft-rzepa-chemical-mime-type-01.txt 561 in which the initial chemical submission was made, incorporated 562 suggestions received during the subsequent discussion period, and 563 indicated scientific support for and uptake of a higher level 564 document incorporating physical sciences[2-7]. This Model 565 submission benefited greatly from the previous groundwork laid, and 566 the continued interest by, those communities. 568 The authors would additionally like to thank Keith Moore 569 (moore@cs.utk.edu), lilley (lilley@afs.mcc.ac.uk), Wilson Ross 570 (ross@cgl.ucsf.EDU), hansen (hansen@pegasus.att.com), Alfred 571 Gilman (asg@severn.wash.inmet.com), and Jan Hardenbergh 572 (jch@nell.oki.com) without which this document would not have been 573 possible. Additional thanks go to Mark Crispin 574 (MRC@CAC.Washington.EDU) for his comments on the previous version and 575 Cynthia Clark (cclark@CNRI.Reston.VA.US) for editing the submitted 576 versions.