More Detail |
||||||
Terms and Conditions of use |
The code from which the present applet was derived was written by Guillaume Cottenceau at Imperial College and that code is
|
|||||
|
|
||||||
A quick tour of the ISO format |
An introduction to the format is available in the scientific literature:
What the applet's format checker doesThe checking procedures in the applet are very simple, and concentrate on the "invariant" aspects of the format. Incoming information is divided into separate lines of (text) data, and each line's content examined. The first check is for the word "VAMAS" (no other part of the "format identifier" (other than "new line") is checked): successful location of the format identifier line signals the start of the SDTF proper and its header information. Everything before this is ignored. How to "construct" an ISO spectrum.If it is desired to "fabricate" a data file which can be displayed by the applet - for example for test purposes, or if a data system which writes valid ISO-14976 files is not available, it is a simple matter to copy a dummy ISO-14976 header (for example, from the PET spectrum here) and append a series of ordinate values to that, changing the x-start, x-increment, and no. of x values lines appropriately (lines 49, 50, and 62 in this example). No formal "end of experiment" terminator is required, as mentioned above. |
|||||
|
|
||||||
For system administrators |
Applet invocation syntax.Broadly "HTML 4.0" should be followed, avoiding the "proprietary" tags, thus in general only the following tags and attributes should be used: Applet security.The applet is "unsigned" and so must be regarded formally as "insecure"; (the original JCAMP applet implemented Netscape security signatures) Spectrum MIME type.The ".vms" file extension is used for the spectra and is in process of submission through the IETF as a "Chemical MIME" type. The present status is "experimental" (i.e. the type/sub-type) "chemical/x-vamas-iso14976" should be set. Since the format is solely text based, however, http systems (and browsers communicating with them) will in general react correctly if configured to serve (or read) unknown MIME types as "text/plain". In most cases this will be the default action. |
|||||
|
||||||
This an Acolyte design.