Lists Home |
Date Index |
Bryan you are somewhat right, yes I could transfer the presentation logic to
the programming language, since
for my work it is complex to be implemented. But I want the behaviour of the
instruments to be independently
Suppose there is a scenario:
I have a instrument panel in which there are a number of instruments. The
behaviour of these instruments is interdependent in the panel and also some
of the instruments are affected or affect instruments in other panels. I
want not to keep this behaviour coupled with the language. I want that
things are changeable by just changing the XML file.
Any help, any DTD that corelates to this.
----- Original Message -----
From: "Thomas B. Passin" <email@example.com>
Sent: Monday, January 13, 2003 7:43 PM
Subject: Re: [xml-dev] Instrument DTD
> > I don't think you'll find anything general. Unless it was at the same
> > time practically useless. For example when you say you want
> > representation of instrument input/output I suppose the best you could
> > hope for is some markup representing where and how you are supposed to
> > get a hold of said input/output.
> This bit sounds much like ACME, a software architecture description
> language. ACME itself is not XML, but an XML version is supposed to be in
> the works, or you could turn it into XML yourself since it is a text
> Tom P
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.435 / Virus Database: 244 - Release Date: 12/30/02