[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
=20
kramerGary Kramer "Analytical Information Markup Language (AnIML) for
Spectroscopy and Chromatography Data"=20
The Analytical Information Markup Language (ANIML) is being developed =
by
ASTM subcommittee E13.15 on Analytical Data Management as a "web-aware"
mechanism for instrument-to-instrument, instrument-to-application, and
application-to-application data interchange and archiving. AnIML is =
based in
part on NIST's SpectroML markup language for uv-vis spectroscopy data =
and
ThermoElectron's Generalized Analytical Markup Language (GAML) and =
borrows
heavily from older interchange standards such as IUPAC=B9s JCAMP-DX and =
ASTM=B9s
ANDI, from existing data dictionaries, and from other relevant markup
language efforts. AnIML is comprised of two major parts. The AnIML =
Core,
whose structure is described by an XML (Extensible Markup Language) =
schema,
provides means to organize and represent arbitrary analytical data. =
AnIML
Technique Layers formally define the structure of data and metadata for
specific analytical techniques and take the form of XML instance =
documents.
A Technique Schema provides the meta-representation for the Technique
Layers, which are extensible to permit vendor, enterprise, and/or user
extensions to the data representation. Utilizing extension data will =
require
custom software; however, its presence in an AnIML file should not =
break
generic software applications. A software tool(the AnIML Validator) has =
been
created to check such instance documents for completeness, for proper
syntax, and, in a limited way, for semantic content. Another software =
tool
(the AnIML Technique Creator) allows analytical domain experts lacking =
XML
expertise to create Technique Layer instance documents. Adherence to =
the
AnIML standard permits the creation of generic data viewers that can
function inside XML-aware programs, such as Microsoft's Internet =
Explorer
(versions > 6.0). With such a viewer, a user should be able to look at
result data from any analytical technique in AnIML format. However,
manipulating such data will require an advanced viewer or custom =
software
More research to come.
=20
_____ =20
""I do not feel obliged to believe that the same God who has endowed us =
with
sense, reason, and intellect has intended us to forgo their use." -- =
Galileo
Galilei=20
_____ =20
Toby Considine
Facilities Technology Office
University of North Carolina
Chapel Hill, NC
=20
Email: Toby.Considine@fac.unc.edu <mailto:Toby.Considine@fac.unc.edu>=20
Phone: (919)962-9073=20
=20
------_=_NextPart_001_01C4F44D.825B57E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40";>
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"PlaceType"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"PlaceName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Verdana;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:11.0pt;
font-family:Verdana'>I spent a bunch of time today tracking down =
UnitsML. No
one knows nothing about it. I even tried all my old LBL contacts =
-
no one can remember anything. The last known member of the team =
now works
from home and was unreachable. The UnitsML trail vanishes with a =
single PowerPoint
in January 2003.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:11.0pt;
font-family:Verdana'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:11.0pt;
font-family:Verdana'>I may have found Son of =
UnitsML.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:11.0pt;
font-family:Verdana'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:11.0pt;
font-family:Verdana'>The AniML standard (Analytical Information Markup =
Language)
is still in active development by NIST. It seems to occupy the =
same space
and be focused on analytical equipment that includes Data =
Loggers. NIST
is actively funding two full-time personnel. AniML is a ASTM =
standard.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:11.0pt;
font-family:Verdana'>http://animl.sourceforge.net/<o:p></o:p></span></fo=
nt></p>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:11.0pt;
font-family:Verdana'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:11.0pt;
font-family:Verdana'>From a November 2004 conference:<o:p></o:p></span><=
/font></p>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:11.0pt;
font-family:Verdana'><o:p> </o:p></span></font></p>
<p><a name=3Dkramer></a><b><font size=3D3 face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;font-weight:bold'>Gary Kramer =
</span></font></b>"Analytical
Information Markup Language (AnIML) for Spectroscopy and Chromatography
Data" <o:p></o:p></p>
<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>The
Analytical Information Markup Language (ANIML) is being developed by =
ASTM
subcommittee E13.15 on Analytical Data Management as a =
"web-aware"
mechanism for instrument-to-instrument, instrument-to-application, and
application-to-application data interchange and archiving. AnIML is =
based in
part on NIST's SpectroML markup language for uv-vis spectroscopy data =
and
ThermoElectron's Generalized Analytical Markup Language (GAML) and =
borrows
heavily from older interchange standards such as IUPAC¹s JCAMP-DX =
and
ASTM¹s ANDI, from existing data dictionaries, and from other =
relevant
markup language efforts. AnIML is comprised of two major parts. The =
AnIML Core,
whose structure is described by an XML (Extensible Markup Language) =
schema,
provides means to organize and represent arbitrary analytical data. =
AnIML
Technique Layers formally define the structure of data and metadata for
specific analytical techniques and take the form of XML instance =
documents. A
Technique Schema provides the meta-representation for the Technique =
Layers,
which are extensible to permit vendor, enterprise, and/or user =
extensions to
the data representation. Utilizing extension data will require custom =
software;
however, its presence in an AnIML file should not break generic =
software
applications. A software tool(the AnIML Validator) has been created to =
check
such instance documents for completeness, for proper syntax, and, in a =
limited
way, for semantic content. Another software tool (the AnIML Technique =
Creator)
allows analytical domain experts lacking XML expertise to create =
Technique
Layer instance documents. Adherence to the AnIML standard permits the =
creation
of generic data viewers that can function inside XML-aware programs, =
such as
Microsoft's Internet Explorer (versions > 6.0). With such a viewer, =
a user
should be able to look at result data from any analytical technique in =
AnIML
format. However, manipulating such data will require an advanced viewer =
or
custom software<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:11.0pt;
font-family:Verdana'>More research to =
come.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:11.0pt;
font-family:Verdana'><o:p> </o:p></span></font></p>
<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D2
face=3D"Times New Roman"><span style=3D'font-size:10.0pt'>
<hr size=3D2 width=3D"100%" align=3Dcenter>
</span></font></div>
<p class=3DMsoNormal><font size=3D3 face=3DVerdana><span =
style=3D'font-size:12.0pt;
font-family:Verdana'>""I do not feel obliged to believe that =
the same
God who has endowed us with sense, reason, and intellect has intended =
us to
forgo their use." -- Galileo Galilei =
</span></font><o:p></o:p></p>
<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D2
face=3D"Times New Roman"><span style=3D'font-size:10.0pt'>
<hr size=3D2 width=3D"100%" align=3Dcenter>
</span></font></div>
<table class=3DMsoNormalTable border=3D0 cellpadding=3D0>
<tr>
<td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
<p class=3DMsoNormal><st1:PlaceName w:st=3D"on"><font size=3D3 =
face=3DVerdana><span
=
style=3D'font-size:12.0pt;font-family:Verdana'>Toby</span></font></st1:P=
laceName><font
face=3DVerdana><span style=3D'font-family:Verdana'> <st1:PlaceName =
w:st=3D"on">Considine</st1:PlaceName><br>
<st1:PlaceName w:st=3D"on">Facilities</st1:PlaceName> <st1:PlaceName =
w:st=3D"on">Technology</st1:PlaceName>
<st1:PlaceName w:st=3D"on">Office</st1:PlaceName><br>
<st1:PlaceType w:st=3D"on">University</st1:PlaceType> of <st1:State =
w:st=3D"on">North
Carolina</st1:State><br>
<st1:place w:st=3D"on"><st1:City w:st=3D"on">Chapel Hill</st1:City>, =
<st1:State
w:st=3D"on">NC</st1:State></st1:place></span></font><o:p></o:p></p>
</td>
<td style=3D'padding:.75pt .75pt .75pt .75pt'>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'> <o:p></o:p></span></font></p>
</td>
<td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'>
<p class=3DMsoNormal><font size=3D3 face=3DVerdana><span =
style=3D'font-size:12.0pt;
font-family:Verdana'>Email: <a =
href=3D"mailto:Toby.Considine@fac.unc.edu";>Toby.Considine@fac.unc.edu</a=
><br>
Phone: (919)962-9073 </span></font><o:p></o:p></p>
</td>
</tr>
</table>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
------_=_NextPart_001_01C4F44D.825B57E0--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]