oship-dev team mailing list archive
-
oship-dev team
-
Mailing list archive
-
Message #01312
Re: openEHR Refactoring
2010/8/5 Tim Cook <timothywayne.cook@xxxxxxxxx>
> Hi Diego and All,
>
> I took a look at your repackaging efforts and there is a problem.
>
> The reason I had bad imports was because I had old source code in the
> km/mlhim and km/openehr packages that depended on the old packaging.
These modules was generated by the adl2py code generator, correct ?
So, why they are necessary to the OSHIP, if they can be generated any time
you want ? They aren't used by any other module and they don't have tests.
I didn't catch how important is these files to the oship system. Could you
explain me ? I didn't catch their purpose .
>
But ...
>
> rm stands for Reference Model. There are many Reference Models. So to
> take your approach you should be using openehr.rm.xxxxxxxxxx so we can
> still have mlhim.rm.xxxxxx and sdmx-hd.rm.xxxxxxxx 13606.rm.xxxxxxx,
> etc,
>
This approach changes how I understand what is the OSHIP project. At the
moment, OSHIP project is only and just only the implementation of the
openEHR model. Until that I know, the purpose of all openEHR components is
mix all concepts from different models (hl7, ISO 18308, CEN) into a model
that communicate with all definitons described by each different
specification. My point is if separate them means that OSHIP approach is
leaved aside.
Could you explain me this too ?
>
> Each of these models have their own namespace with rm being one
> component of that top-level namespace.
>
But this don't indirect concludes that concept between these namespaces
won't be mixed together ?
> I have restructured your repackaging and created a new branch. It runs
> fine. I suggest that you merge it with the development branch.
>
> https://code.launchpad.net/~oship-dev/oship/repkg/+merge/31921
>
> I take your point, but there are some points that need be clear before this
merge be done.
> Cheers,
> Tim
>
>
>
> --
> ***************************************************************
> Timothy Cook, MSc
> Project Lead - Multi-Level Healthcare Information Modeling
> http://www.mlhim.org
>
> LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
> Skype ID == timothy.cook
> Academic.Edu Profile: http://uff.academia.edu/TimothyCook
>
> You may get my Public GPG key from popular keyservers or
> from this link http://timothywayne.cook.googlepages.com/home
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~oship-dev
> Post to : oship-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~oship-dev
> More help : https://help.launchpad.net/ListHelp
>
>
--
http://dmpinheiro.net
-----------------------------------
Diego Manhães Pinheiro
Follow ups
References