Thanks Pablo, I'm going to be updating the service today, and it is not a production service, but if you have any issues do let me know. It would be interesting to see if this can support a gui generation scenario. Please let us know how it goes!
Kind regards Seref On Tue, Nov 15, 2011 at 3:19 PM, pablo pazos <pazospablo at hotmail.com> wrote: > Thank you Seref impressive work! > > I'll try the JSON services to do some javascript gui generation. > > -- > Kind regards, > Ing. Pablo Pazos Guti?rrez > LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez > Blog: http://informatica-medica.blogspot.com/ > Twitter: http://twitter.com/ppazos <http://twitter.com/ppazos> > > ------------------------------ > Date: Tue, 15 Nov 2011 09:45:18 +0000 > Subject: Bosphorus web services beta announcement > From: serefarikan at kurumsalteknoloji.com > To: openehr-technical at openehr.org > > > Dear members of the openEHR community, > > Having reached a point where project Bosphorus has reached a functional > state, we have deployed and experimental web service under Opereffa's > current server. > > The web service exposes the archetype parser functionality of Thomas > Beale's Eiffel code base with XML and JSON output. There is a simple web > application at http://opereffa.chime.ucl.ac.uk/bosphorus/ which uses this > web service to display XML and JSON output. > > The web service is as simple as possible to use: calling > http://opereffa.chime.ucl.ac.uk/bosphorus/resteasy/openehr/getarchetypeslistreturns > an XML list of the archetypes in repository, and calling > http://opereffa.chime.ucl.ac.uk/bosphorus/resteasy/openehr/getarchetypewith > the archetype name as the parameter such as: > http://opereffa.chime.ucl.ac.uk/bosphorus/resteasy/openehr/getarchetype?archetypeName=openEHR-EHR-CLUSTER.case_identification.v1returns > the XML output. Simply changing the URLS to > http://opereffa.chime.ucl.ac.uk/bosphorus/resteasy/openehr/getarchetypeslistjsonand > http://opereffa.chime.ucl.ac.uk/bosphorus/resteasy/openehr/getarchetypejsonallows > access to JSON output. > > There are known issues in the XML output, which we are fixing at the > moment, but we felt that the current state of the code is capable enough to > share with the community, to demonstrate the idea of turning key openEHR > infrastructure functionality into web services. Thanks to functionality of > the Eiffel reference implementation, this web service handles the > processing of ADL 1.5 specific features and its XML output is valid > according to published XML schemas (version 1.0.1). Please note that the > XML or JSON output is only data, therefore its content must be placed into > an AOM implementation to become a complete parser output, and we look > forward to hearing from implementers, especially in the Java space to > collaborate on this. > > In the near future, we are going to be extending the set of services, and > we would be glad to hear about your ideas for new web services in the > tooling space. > > The packaging and release of code will follow soon, but it will take time > since Bosphorus has a fairly complicated development setup, requiring Java, > C/C++ and Eiffel development setups to be configured jointly. The > reference deployment of the web service is therefore the most practical way > of experimenting with functionality. There are issues related to > serialization of various AOM items, and it you notice errors in the XML > output, please let us know so that we can fix them. > > We would like to thank Thomas Beale of Ocean Informatics for providing > access to his Eiffel source code and his contributions to this work, which > enables us to share our work with the community. > > Kind regards > > Seref Arikan & Professor David Ingram, > UCL, CHIME > _______________________________________________ openEHR-technical mailing > list openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20111115/ac89da83/attachment.html>
