Since DTDs do not follow established software engineering standards, you
would be much better off with XML Schema. The combination of XML schema and
XForms should be sufficient for handling the data and user interaction. Both
SVG and XSL can be used to present the data.
I will soon have two papers published that describe the use of DICOM
data-types in XML. For those who are interested, I will send out preprints
in PDF.
Bob Leif
-----Original Message-----
From: Sanjaya Joshi [mailto:sanjay@...]
Sent: Monday, February 24, 2003 3:29 PM
To: lecis-post@yahoogroups.com
Subject: [lecis-post] FW: ALA and XML for instruments (Structured Reporting
usign objects similar XML DOM)
Below is a link interesting paper on Structured Reporting and Event
Streams similar to the XML Document Object Model...
http://www.dclunie.com/papers/spie_mi_2001_SR_manuscript.pdf
The SR is part of the DICOM standard...
Also a book:
http://www.pixelmed.com/srbook.html
We have also been thinking of embedding conditional flow and conditional
programming into the DTD directly... This is good in an HTS scenario
(some of this grammar is already within the XSL DTD especailly for the
FO -- Formatting Objects -- area).
Another area is Aspect Oriented programming similar to Event Streams...
(More on that soon).
Another standardization area for imaging (that is gaining a big
foothold) is JPEG2000 (I think the FDA is OK with a factor of 10 or 12
for lossless compression.
Again would be good to combine the control paradigm with the data model
(process).
Sanjay
-----Original Message-----
From: James Gill [mailto:james.gill@...]
Sent: Sunday, February 23, 2003 8:51 AM
To: Gary W. Kramer; tstaab@...; Mark F Russo;
roger.mcintosh@...; bs-sc@...;
info@...
Subject: Re: ALA and XML for instruments
All,
I certainly had no intentions to dilute current efforts nor necessarily
start a new one. Ok I'll admit the mail sounded that way - but my
intention was to offer the suggestion that ALA might have a role to
play, and to start the discussion that if ALA does have a role - what
would that role be? Perhaps just to make sure the ALA's efforts to
support the various efforts are continued.
I think one important question in front of us now is - Since we have a
major
vendor (certainly in the HTS area) using XML, and even better towards
releasing it into the public domain, how can this be leveraged to insure
better standardization? I suspect there are also numerous other in house
development efforts on going at various vendors and large industrial
sites as well. How can we make sure that these in house developers
(especially the vendors) want to use the standards??
I should also point out that in the HTS area - I believe that standards
have been much harder to come by than in the Spectroscopy and
Chromatography areas. I believe that the HTS area simply has not
developed a "standardization" mentality
- So please forgive my ignorance in this area and accept my suggestions
as opportunities to educate me.
Suggestions? Is it as Torsten and Gary say - the vehicles are in place,
folks just need to start using them? Does ALA have a role?
Jay
"Gary W. Kramer" wrote:
> Jay,
>
> There is currently an effort to develop XML data representations for
> result data from spectroscopy and chromatography instruments ongoing
> in ASTM E13. This has been in the works for about a year and a half,
> and many instrument vendors and LIMS folks are participating. We're
> having a meeting at Pittcon, see below for the info. We have
> preliminary indications that the IUPAC/JCAMP folks will join the ASTM
> effort so that we can develop a single standard, not multiple
> approaches like we had with the ANDI and JCAMP standards.
>
> I completely agree with you that we need to get XML standards in place
> for instrument data, but I would very much not like to see competing
> efforts evolve to do try to do this. The ASTM effort and approach is
> not yet set in concrete, so there is plenty of opportunity for folks
> who want to see such standards to get involved and be a part of the
> solution. Speaking for the ASTM XML Working Group, we invite all
> interested parties to work with us to develop standards that will
> benefit all of us.
>
> Cheers,
> Gary
>
> From: "Abramo, Kimberly" <KHAbramo@...>
> To: "Abramo, Kimberly" <KHAbramo@...>,
> "'ty_abshear@...'"
> <ty_abshear@...>,
> "Alt, Timothy" <TMAlt@...>,
> "'aykut.arslan@...'" <aykut.arslan@...>,
> "'mark.f.bean@...'" <mark.f.bean@...>,
> "'stephen.best@...'" <stephen.best@...>,
> "'blair@...'" <blair@...>,
> "'michael_boruta@...'" <michael_boruta@...>,
> "'tony_brand@...'" <tony_brand@...>,
> "'polyspec@...'" <polyspec@...>,
> "'tony.davies@...'"
<tony.davies@...>,
> "'dermin.fan@...'" <dermin.fan@...>,
> "'paul.derose@...'" <paul.derose@...>,
> "'cdollar@...'" <cdollar@...>,
> "'james.duckworth@...'"
> <james.duckworth@...>,
> "'scot.ellis@...'"
> <scot.ellis@...>,
> "'jean-louis.excoffier@...'"
> <jean-louis.excoffier@...>,
> "'craig.fellows@...'"
> <craig.fellows@...>,
> "'thorsten.froehlich@...'"
> <thorsten.froehlich@...>,
> "Fugere, John \"Barry\""
> <jbfugere@...>,
> "'egavin@...'" <egavin@...>,
> "'mark_harnois@...'" <mark_harnois@...>,
> "'dheld@...'" <dheld@...>,
> "'markus.hemmer@...'"
<markus.hemmer@...>,
> "'sherry.hemmingsen@...'"
<sherry.hemmingsen@...>,
> "'hooverhl@...'" <hooverhl@...>,
> "'hughespf@...'"
> <hughespf@...>,
> "'tony.johnson@...'"
> <tony.johnson@...>,
> "'simon.kaalman@...'"
> <simon.kaalman@...>,
> "'pkilz@...'"
> <pkilz@...>,
> "'gary.kramer@...'" <gary.kramer@...>,
> "'don_kuehl@...'" <don_kuehl@...>,
> "'rjlanc@...'" <rjlanc@...>,
> "'rlarsensdt@...'"
> <rlarsensdt@...>,
> "'dlevy@...'" <dlevy@...>,
> "'kenlewis@...'" <kenlewis@...>,
> "'mil55244@...'"
> <mil55244@...>,
> "'christopher.lynch@...'"
> <christopher.lynch@...>,
> "'gary.mallard@...'"
> <gary.mallard@...>,
> "'michael@...'" <michael@...>,
> "'rmcdjcamp@...'" <rmcdjcamp@...>,
> "'r_d_mcdowall@...'" <r_d_mcdowall@...>,
> "'dave.michelsen@...'" <dave.michelsen@...>,
> "'todd_miller@...'" <todd_miller@...>,
> "'bryan_miller@...'" <bryan_miller@...>,
> "'moored@...'" <moored@...>,
> "'pm286@...'"
> <pm286@...>,
> "'totoole@...'" <totoole@...>,
> "'martin.peschke@...'" <martin.peschke@...>,
> "'jay_powell@...'" <jay_powell@...>,
> "Richard, Shannon" <SMRichard@...>,
> "'brian_rohrback@...'" <brian_rohrback@...>,
> "'john.rumble@...'" <john.rumble@...>,
> "'thomas.sauter@...'" <thomas.sauter@...>,
> "'marie_scandone@...'" <marie_scandone@...>,
> "'schaefer@...'"
> <schaefer@...>,
> "'thomas_r_sharp@...'"
<thomas_r_sharp@...>,
> "'terry.sheehan@...'" <terry.sheehan@...>,
> "'ssimpson@...'" <ssimpson@...>,
> "'steve.stein@...'"
> <steve.stein@...>,
> "'bill.town@...'"
> <bill.town@...>,
> "'john.travis@...'" <john.travis@...>,
> "'tom.tuzzeo@...'" <tom.tuzzeo@...>,
> "'david.varley@...'" <david.varley@...>,
> "'craig.walla@...'" <craig.walla@...>,
> "'thomas.weber@...'"
<thomas.weber@...>,
> "'tony@...'" <tony@...>,
> "'debbie_zink@...'"
> <debbie_zink@...>
> Cc: "'Paul.Fjeldsted@...'"
<Paul.Fjeldsted@...>,
> "Wishnies, Steven" <SMWishnies@...>,
> "Mutin, Alexander"
> <almutin@...>,
> "Nishimura, Masayuki" <MANishimura@...>,
> "'frank.tontala@...'" <frank.tontala@...>,
> "'d_martinsen@...'" <d_martinsen@...>,
> "'peter.linstrom@...'" <peter.linstrom@...>,
> "'aykut.arslan@...'" <aykut.arslan@...>,
> "'anlidao.nguyen@...'" <anlidao.nguyen@...>,
> "'rmcdjcamp@...'" <rmcdjcamp@...>,
> "'scubbedge@...'"
> <scubbedge@...>,
> "'steve@...'" <steve@...>,
> "'steve.leich@...'" <steve.leich@...>,
> "'friedrich.brunzema@...'" <friedrich.brunzema@...>,
> "'dave.blaha@...'" <dave.blaha@...>,
> "'craig.walla@...'" <craig.walla@...>,
> "'ute_bober@...'" <ute_bober@...>,
> "'bill.town@...'" <bill.town@...>,
> "'sgadgil@...'" <sgadgil@...>,
> "'jerrym@...'" <jerrym@...>,
> "'clacraver@...'"
> <clacraver@...>,
> "'claracraver@...'"
> <claracraver@...>,
> "'jay_powell@...'"
> <jay_powell@...>,
> "'JULIAN_RANDALL_K@...'"
> <JULIAN_RANDALL_K@...>,
> "'Friedrich.Brunzema@...'"
> <Friedrich.Brunzema@...>
> Subject: RE: PITTCON SpectroML/ GAML/XML ASTM meeting
> Date: Fri, 21 Feb 2003 13:02:35 -0500
> MIME-Version: 1.0
> X-Mailer: Internet Mail Service (5.5.2653.19)
> Content-Type: text/plain;
> charset="iso-8859-1"
>
> I apologize for the delay in sending this message. There has been
much
> confusion as to when the ASTM meetings where going to be held. The
> schedule has now been finalized and the SpectroML/GAML/XML meeting
> will take place on Tuesday March 11th at 5:30PM. I realize that this
> is late in the afternoon, but since most of the committee participants
> are vendors, it works out better that way. We will be reviewing our
> progress in several areas. Additionally, we hope to have attendance
> from representatives from IUPAC. I hope that we will be able to share
> the vision and further develop plans to get the schemas finalized.
> Please let me know if you have any further questions. I look forward
> to seeing many of you at Pittcon.
>
> > Thanks-
> > Kimberly Harris Abramo
> > Product Manager - Spectroscopy
> > Shimadzu Scientific Instruments
> > 1-800-477-1227 ext 1912
> > (Fax) 410-381-1222
> >
>
> > Guys,
> > There was a lot of talk at LA03 about xml and standards for
> > instrument data. Roger has been working to get his format into the
> > public domain, and I had a number of discussions with folks at the
> > meeting..
> >
> > What would folks think about having the ALA sponsor a group to
> > co-ordinate the various efforts and ultimately to recommend a
> > specification which would be supported by the ALA, published in JALA
> > etc. I think the ALA represents a unique opportunity in that there
> > is representation from the vendors, industry, consultants, academics
> > and government. In fact, all of those constituencies are
> > represented on this mail. In addition there has already significant
> > progress that has been made by the folks on this mail towards a
> > standard.
> >
> > I would see the next steps being
> >
> > 1) Gain agreement from you all that the ALA is the right place to
> > propose such a standard and they you would want to participate
> > 2) Propose the concept to the Board (which of course will happily
> > accept)
> > 3) Determine membership on the committee
> >
> > Finally whether or not we pursue this approach, I'm hopeful that all
> > of you keep talking. From a personal viewpoint, I'm tired of
> > writing instrument drivers.
> >
> > Jay
> >
To view archived messages, go to:
http://groups.yahoo.com/group/lecis-post/messages
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/