There is a philosophical difference between XML and HTML - the first is
to represent / store information with no thought to how it is displayed.
HTML involves content and display, but the emphasis is on
presentation. Constructs involved in presentation change more rapidly
than the constructs
Good thought.
And welcome back, Bhaskar :-)
Kevin
--- K.S. Bhaskar [EMAIL PROTECTED] wrote:
There is a philosophical difference between XML and
HTML - the first is
to represent / store information with no thought to
how it is displayed.
HTML involves content and display, but the
13, 2005 3:51 PM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] Announcing XML
exporter (Beta testers
wanted.)
One of my goals has been to be able to dump a chart
to
a .html format, viewable in a web browser.
This should be straight-forward for progress notes
I am a XML newbie, so bear with me.
Are you saying to use my XML exporter to get the data
out of VistA, then use a separate program to assemble
the information into a final CCR?
And what is XSLT?
Thanks
Kevin
--- Gregory Woodhouse
[EMAIL PROTECTED] wrote:
I know of no implementation of XSLT
Absolutely. Modularity if powerful in many ways.
Kevin
--- Gregory Woodhouse
[EMAIL PROTECTED] wrote:
Dare I be so audacious as to suggest that this is a
good example of
dividing a task into subtasks that don't need to
know about the
larger context? The XML exporter could have been
XSLT is a kind of mini-language that allows you to transform (hence
the 'T') the structure of XML documents. It was originally intended
as a stylesheet language (hence the 'S') that could be used to
transform XML to HTML, a special formatting markup intended primarily
for print (XSL
Incidentally, XSLT and XSL-FO were initially part of the same
specification. I think one of the main reasons XSLT was split off
into a separate specification is that people quickly came to realize
how useful it would be for applications having nothing to do with
style or formatting. It has
@lists.sourceforge.net
Subject: RE: [Hardhats-members] Announcing XML exporter (Beta testers
wanted.)
That's a good idea, but off track from what I want.
When I dump the file to html, I want it to be able to
go to a disk that a patient could take with them
somewhere. Then someone could view the record
]
On Behalf Of Kevin
Toppenberg
Sent: Wednesday, July 13, 2005 3:51 PM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] Announcing XML
exporter (Beta testers
wanted.)
One of my goals has been to be able to dump a
chart
to
a .html format, viewable
Well, I am finally done with my XML exporter.
Features:
--Separate modules for usr interface (setting up
export request) and actual export, to allow for future
modular use.
--Export 1 or more files at a time
--Works with Sort Templates to allow a user to search
for a complex set of desired output
One of my goals has been to be able to dump a chart to
a .html format, viewable in a web browser.
This should be straight-forward for progress notes
(all that I am concerned with at this point.) But if
one gets into all the other info that can be stored
(i.e. labs etc etc.) then I give up.
Well then, Greg will just have to hurry up and finish Triton! ;-)
On Wednesday 13 July 2005 03:50 pm, Kevin Toppenberg wrote:
One of my goals has been to be able to dump a chart to
a .html format, viewable in a web browser.
This should be straight-forward for progress notes
(all that I am
13, 2005 3:51 PM
To: hardhats-members@lists.sourceforge.net
Subject: Re: [Hardhats-members] Announcing XML exporter (Beta testers
wanted.)
One of my goals has been to be able to dump a chart to
a .html format, viewable in a web browser.
This should be straight-forward for progress notes
(all
I know of no implementation of XSLT in MUMPS, but there are open
source tools like Xalan. Instead of trying to export data directly to
CCR, why not consider exporting to SOME format (so long as it's XML,
of course) using as many separate exports as you need, and then write
an XSLT
Dare I be so audacious as to suggest that this is a good example of
dividing a task into subtasks that don't need to know about the
larger context? The XML exporter could have been (indeed, was)
designed without regard to any larger problem such as generating a
CCR document from Vista.
15 matches
Mail list logo
