mlhim-owners team mailing list archive
-
mlhim-owners team
-
Mailing list archive
-
Message #00269
Re: Draft 2.2.0 Specs.
Hi Roger,
Thanks again for your participation and comments.
I too do not like the order of the way the classes are listed.
I REALLY need to complete the work on the CDD re-validation with the specs.
It would be awesome for the project if you would make your suggested
changes and commit them.
I do not believe that it is good for only one person to be the developer.
bzr branch lp:mlhim-specs
Please feel free to make your changes.
Cheers,
Tim
On Thu, Jun 9, 2011 at 6:52 PM, Roger Erens <roger.erens@xxxxxxxxx> wrote:
> Hi Tim,
>
> good work! Some quick suggestions:
> 1) left-aligning the text instead of justifying makes the pages look a
> little restless in my opinion
> 2) since it's a reference manual, I would choose to list the classes
> in the packages in alphabetical order
> 3) the analogy between Lego and MLHIM approach: I would compare the
> Reference Model with (info in) the catalog of all the Lego-bricks used
> in a Lego-product line (e.g. Star Wars) (so not a catalog of *all*
> Lego-bricks ever produced). Then the actual Lego-bricks from this
> product line (cf Healthcare domain) are instantiations of the info in
> the catalog. The bricks are analogous to the actual data-items, that
> have to be bound to the toy-model (archetype). At least, this is how I
> would improve the analogy in the openEHR docs, where I long time
> believed the actual data-items were instantiations of
> archetype-classes ,where those archetype-classes were created at
> design-time instead of run-time.
>
> Cheers,
>
> Roger
>
> On Thu, Jun 9, 2011 at 20:33, Timothy Cook <timothywayne.cook@xxxxxxxxx> wrote:
>> Hi All,
>>
>>
>> I have uploaded a PDF of the draft 2.2.0 specs to
>> http://www.mlhim.org/mlhim-2.0/mlhim-ref-man-2.0.x-enUS.pdf/view
>>
>> I would appreciate it if some of you would read through it quickly and
>> see if you find any glaring errors or subtle bugs.
>>
>> It is only 74 pages at this point so not too tough to scan.
>>
>> Thanks,
>> 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/~mlhim-owners
>> Post to : mlhim-owners@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~mlhim-owners
>> More help : https://help.launchpad.net/ListHelp
>>
>
--
================
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
Follow ups
References