Very good, Thomas, I appreciate your help. I have some good starting thoughts and will write them tomorrow in the wiki.
Bert Op 6 sep. 2016 23:04 schreef "Thomas Beale" <[email protected]>: I will actually have some time to start to look at this in the next few weeks - i.e. to facilitate / coordinate some work, and possibly do some. I would propose to proceed as follows: - gather current unmet requirements - examine current state of AQL spec to clarify what it alredy says, what it lacks - propose changes to AQL The question of adding e.g. an Antlr grammar for the IHTSDO constraint expression syntax to AQL is almost trivial; the real question to me is: what is the querying + terminology interaction model we are trying to achieve. So some example queries (pseudo-code is fine) would help. If Bert and others who want more progress can *at least post some ideas at the requirements level *- clear and succinct as possible please - it will help a lot. Here is a wiki page for gathering this information <https://openehr.atlassian.net/wiki/display/spec/Terminology+Querying+for+AQL>. As usual, contributors should feel free to change it as required. - thomas On 06/09/2016 13:05, Bert Verhees wrote: Op 6-9-2016 om 19:01 schreef Erik Sundvall: Many of us think that a better integration of the openEHR and the Snomed CT modelling efforts would be great. But there are not enough resources (e.g. dedicated time of people with the right knowledge) being put into doing this, since this is hard (but interesting) work usually requiring somebody to pay people... Hi Erik, I do not want to undermine the value of your statement, contrary, I think it is very good when some organization or country builds the thing, the money involved is a piece of cake for such an entity. Let the people with good connections start working on getting this arranged!!!! The sooner the better!!! ----------------------------------------------------------------------------------- But on the other hand, we should sit down and wait until something will happen. First, I think, we need a list of requirements. We could start with that. We need that anyway, even if someone succeeds in getting a big company or government to finance the project. In my opinion, the most difficult work is the definition, following the (to be defined) requirements, how is this project going to look like? Someone with experience in modeling modeling-languages and query-languages, someone who is clever in thinking about syntaxes and structures. The implementing itself is easier, it is just programming. With help of ANTLR and a good definition, this will not be too hard. Like there are written ADL-parsers/AQL-parsers as open source. When there is a prototype ready, others can improve it, or inspired by a lousy prototype, start a new better one. That is how open source usually works, and it can create big things. We know that. I can help, I have knowledge of AQL, ADL, and SCT (expression constraints), enough of all three to add sensible ideas. But I cannot do it on my own. I do not feel too confident. There is also a risk of failure when doing this alone. So, to set up the requirements, how can we cooperate on that? Do you have an idea? Maybe a wiki? Someone needs to take the lead. Say how things are to be done, facilitates, etc. Maybe it is too much to ask for someone to take the lead. Let first inventory who wants to help. It will cost maybe a few hours in this initial phase. ---------------------------------------------------------------------- So, who wants to help with this sub-project: - having ideas about features - set up requirements - set up some global architecture ideas. ---------------------------------------------------------------------- Bert _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr- technical_lists.openehr.org -- *Thomas Beale* Management Board, Specifications Program Lead, openEHR Foundation <http://www.openehr.org> Chartered IT Professional Fellow, BCS, British Computer Society <http://www.bcs.org/category/6044> Health IT blog <http://wolandscat.net/> Culture blog <http://wolandsothercat.net/> _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr- technical_lists.openehr.org
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
