mlhim-owners team mailing list archive

[Roger Erens <roger.erens@xxxxxxxxx>]

Hi Tim,

Good idea to have an executive summary explaining the project, but
<rant>
funny that you discuss interoperability on a TiddlyWiki page that
violates the UI behaviour with its missing Back/Forward Button
behaviour. I instantly disliked it after having clicked a link. Hence,
I would suggest to replace that page with just a single external link
pointing to the MLHIM site.</rant>

Some points:
,programs (HIV, TB,
should be
, and programs (HIV, TB,
possibly also explaining the abbreviations HIV and TB (or linking them
to wikipedia entries)

to overcome semantic interoperability
should be
to overcome LACK OF semantic interoperability

components that express domain knowledge in artifacts known as Concept
Constraint Definitions (CCDs).
could be
artifacts that express domain knowledge, known as Concept Constraint
Definitions (CCDs).
or
components that express domain knowledge, known as Concept Constraint
Definitions (CCDs).
?

have asked the question; Why?
should be
have asked the question: "Why?"

The section almost in the end, but in which you want to propose
something first (?), about trust, is confusing.
The next is somewhat less confusing.
Maybe another criticism on the lack-of-governance that you/all of us
might think about how to counter: when an implementer chooses an
'approved CCD' he not only gets trust in that CCD, but it also SAVES
him/her TIME, hence effort/money. He needs less time to test whether
to use CCD 1 or CCD 2 which may look very much the same. It will take
a long time before one of the alternatives turns out to be the best,
or most popular one.

An executive summary should not contain an example, I think.
Although you may think it's a brief introduction, maybe newbies may
not think so. An executive summary should fit on one A4/US Letter
page; this document is more like a manifesto. Also, you're targeting
developers, not executives?

Maybe you should start out creating a mind map with a few
(marketing-ish) people to flesh out the essential message you want to
convey, and postpone the rest of the really interesting (I mean that,
seriously!) subjects to another document.

Sorry if this sounded all too blunt, but hey, I'm Dutch :-/ (meaning: direct)
I really appreciate your effort.

Roger

On Fri, Feb 11, 2011 at 16:09, Tim Cook <timothywayne.cook@xxxxxxxxx> wrote:
> Hi All,
>
> In case you need to explain to someone what MLHIM is (and is not) I have
> put an Executive Summary type of document on the WHO Health Metrics
> Network wiki for others to see in the context of interoperability.
>
>  http://tinyurl.com/4rukbsx
>
> Any questions or comments, corrections please let me know.
>
> 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/~mlhim-owners
> Post to     : mlhim-owners@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mlhim-owners
> More help   : https://help.launchpad.net/ListHelp
>
>