Sam Heard wrote: > Hi All > > One senses the different backgrounds of the players here - the more > operational the focus the more useful XML is but in the design and > modelling world it is of no use at all. I think almost everyone is > delighted with what can be done with XML these days - the more it is > used the more that is possible on the web. But ASCII was the same when > it came out and really OWL as RDF is not very easy to deal with even > with all the wonderful tools (because you have to have the model right). > > I have been working with Tom long enough to understand the issue when > you are formally describing the set of possible constraints that might > be necessary in any given model. The UML and XML serialisation come > later in this process. > > So we all need to accept that value of both approaches - if we are > serialising something formal that does the job and can reload and use > it then that is fine. I am pushing for the move to documentation via > XML archetypes and XSLT because I believe that the power of that > approach and its cross platform utility leaves everything else for > dead. But, I recognise that it is not suitable for use at design time > although it can serialise the UML (sometimes) > > You said you have an XSLT for the archetypes - would you like to share > it with the community. I think we might see things move quite quickly > if we get this out there. > > Cheers Sam > I would love to.
I will have to get clearance from Ravi, Richard & John but then yup...the sooner the better AFAICS. Adam > > > Adam Flinton wrote: >> >>> Other limitations on using XML - it's a no-show for enterprise scale >>> databases >>> or information processing. All that wasted space starts to count when you >>> have >>> to buy two ?20,000 high availability RAID disk arrays instead of one....and >>> plus >>> the bandwidth wastage when there are millions of messages rather than just >>> a >>> few. Yes, binary compression helps, but it just shifts disk and bandwidth >>> loss >>> to the CPU. There are many better ways to represent data for large-scale >>> deployments than XML (even the dADL syntax from ADL does 100% better in >>> space, >>> and represents all object-oriented constructs unambiguously). >>> >>> >> You have got to be kidding me on this one. >> >> Having done XML messaging in very large retail systems (major >> supermarket chains in the EU & US), mobile phone systems, home >> office/criminal justice system & now the CFH....you simply have got to >> be kidding. >> >> ummmmmm.......where to even start....oh yes how about... >> >> "XML is a very commonly used standard with thousands of tools in >> existence from routing engines, to processing engines to parsers to >> database layers ...." >> >> or maybe >> >> "XML is THE standard in enterprise level messaging systems with >> standards such as SOAP, EbXML, OAGI BODS etc.etc." >> >> or maybe : >> >> "XML integrates easily with existing web infrastructures by use of such >> mechanisms as AJAX, Rest JSON etc". >> >> >> Now wrt ADL..... >> >> Adam >> >> ********************************************************************** >> This message may contain confidential and privileged information. >> If you are not the intended recipient please accept our apologies. >> Please do not disclose, copy or distribute information in this e-mail >> or take any action in reliance on its contents: to do so is strictly >> prohibited and may be unlawful. Please inform us that this message has >> gone astray before deleting it. Thank you for your co-operation. >> >> NHSmail is used daily by over 100,000 staff in the NHS. Over a million >> messages are sent every day by the system. To find out why more and >> more NHS personnel are switching to this NHS Connecting for Health >> system please visit www.connectingforhealth.nhs.uk/nhsmail >> ********************************************************************** >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical at openehr.org >> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >> >> >> > > -- > Dr Sam Heard > Chief Executive Officer > Ocean Informatics > > Director, openEHR Foundation > Senior Visiting Research Fellow, University College London > Aus: +61 4 1783 8808 > UK: +44 77 9871 0980 > ------------------------------------------------------------------------ > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > ********************************************************************** This message may contain confidential and privileged information. If you are not the intended recipient please accept our apologies. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Please inform us that this message has gone astray before deleting it. Thank you for your co-operation. NHSmail is used daily by over 100,000 staff in the NHS. Over a million messages are sent every day by the system. To find out why more and more NHS personnel are switching to this NHS Connecting for Health system please visit www.connectingforhealth.nhs.uk/nhsmail **********************************************************************
