I'd hoped to respond to this yesterday, but alas Netscape decided it had other plans.
I think the notion of seperating the actual environment from individual policies makes good sense. Developers should look for the common ground that supports the widest majority of applications and which provides a common framework for adding currently undiscovered ideas. By taking a system-engineering approach to defining the required middleware API, application code could then be constructed in a way that allows applications to intercommunicate, but which allows application developers the flexability they need to chase niche markets. I think step one would be to identify use cases (UML-speak for user scenarios) that cover a wide range of intended applications and then work from there to standardize an API that provides the basic resources needed to support the use cases. Bill Jon Edwards wrote: > Hi Phillippe, > > As a company producing open-source software for healthcare, we'd be very > interested in this... especially if there's funding! ;-) > > Please add me to your mailing-list > > I'd be interested to hear how your "Lego-bricks" will talk to each other? > Will they all be written in the same language? Different languages but call > each other via XML-RPC/SOAP? Different languages but exchange data via XML? > > Cheers, Jon > > Jon Edwards > Pricom Ltd > www.pricom.co.uk
