The notion of moving the standard forward was part of the dialog at the
April VCM and it was my understanding that the MDC would be reactivated
via a host organization and a communication process defined by which
reviewing the "Millenium Standard" that existed in Sept 1999 would occur
and then receive new proposals. The VistA architecture exists with a
technical platform that includes the M(UMPS) data management environemnt.
If the world is to believe that this information architecture should be
taken seriously, then there must be a visible organizations that maintains
the common conventions about how this M data management environment will
adapt to the march of technology so that the M environment as a host for
VistA clearly has a means to evolve to accommodate the the progressively
evolving conceptual content of biomedical science and resource management.
Other ICT component technologies have a means for this evolution and
adaptation that are needed to respond to the capabilities demanded by the
the target users. "Adapt of Fall into the Abyss!" is the rule of nature.
Now lets hear how the M community is going to do this and how the
Suppliers of M implementations will be brought into the dialog with the
potential acquieres in the health (and other) professional discilpines of
the Acquirer sector. MTA and MDC did this up till five years ago so we
know it can be done. If the VistA Community is going to reach the rest of
the world it needs to tell them how it will deal with this problem and
then get on with it. The technical interface with other technologies by
the M environment is needed to complete the story of how the VistA
resource can be used by the healthcare community and it is needed
expeditiously. Gregs's statement that it is feasible and the effort to
work on it is rewarding should be enough since it has been said by many.
Now lets hear how we will do it, when we will do it and where the action
will take place. There are many other dependenat activities that will
augment the effort on the technical infrastructure and they cant wait
around with little specific information.
On Tue, 23 Aug 2005, Greg Woodhouse wrote:
I actually didn't know that MUMPS_V1 was (now) open source. Originally,
I was looking for a version of MUMPS that I could run under Windows
but, as I recall, the developer was adamant that it not be ported to
Windows, so it was of no real use to me. Since then, I've decided to
use OS X as my primary operating system, so that may not be an issue.
But as I said before, ther are other things I'm interested in doing
right now. My opinion is that MUMPS is an underappreciated language,
and I believe that it is in the long term best interest of the MUMPS
community to move the language forward. I also believe it is feasible
to do so, but the community seems almost ideologically opposed to this
course. The argument is framed as one of "practicality" or of "saving
VistA", but I don't think marrying ourselves to the existing code base
without providing a way forward is saving VistA. At best, it's getting
a product out the door.
--- Jim Self <[EMAIL PROTECTED]> wrote:
Greg Woodhouse wrote:
--- Jim Self <[EMAIL PROTECTED]> wrote:
Greg Woodhouse wrote:
Off hand, I don't know, but members of this list do seem to have
a
tendency to "plug" GT.M (presumably because it is open source).
Personally, I think we'd all benefit from a little more vendor
neutrality.
I am not a vendor and neither is GT.M.
No, but Fidelity is.
If you know my history, then you should know that I advocate Free
MUMPS, not vendors. You
do not buy a license for GT.M/Linux from a vendor. You download it
from Sourceforge or get
it from a friend.
Open source may be a
good thing (and I think it is), but is it being touted because it's
the
"right" way to do things or because it's the cheapest?
I don't know of any serious advocate of Open Source or Free software
who doesn't primarily
believe that it is the right way (and perhaps ultimately the only
way) to develop and
promote open standards for computing and the knowledge that we need
(widespread and deep)
to develop and maintain secure and reliable computing and
communications systems in the
long term.
At the moment, GT.M is the only Free (Open Source) MUMPS
implementation that has been
taken seriously enough by VistA developers to make VistA work on
it.
Perhaps so. But reason may only be that it has become something of a
juggernaut -- people put their efforts into GT.M because that is
where
other people are putting their efforts,
MUMPS_V1 was freely available for a good while before GT.M was
released for Linux, but
unfortunately, MUMPS_V1 was only free, not Free (Open Source) until
some time after
attention had shifted to GT.M. Before that I worked with it and
tested it repeatedly for
conformance to the MUMPS standards and talked it up on this list and
elsewhere as a
serious effort at implementing standard MUMPS that was worthy of
serious attention. It
still is.
---------------------------------------
Jim Self
Systems Architect, Lead Developer
VMTH Computer Services, UC Davis
(http://www.vmth.ucdavis.edu/us/jaself)
===
Gregory Woodhouse <[EMAIL PROTECTED]>
"Design quality doesn't ensure success, but design failure can ensure failure."
--Kent Beck
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
