• From: Timothy Cook <timothywayne.cook@g...>
• To: "Costello, Roger L." <costello@m...>
• Date: Tue, 25 Sep 2012 10:59:04 -0300

Hi All,

On Tue, Sep 25, 2012 at 9:40 AM, Costello, Roger L. <costello@m...> wrote:
> Hi Folks,
>
> Should all data be specified the same way?
>

With the best quality guarantee possible; yes, I think so.  But in
some cases there are costs trade-offs taht will be made.

> Should data that, if misunderstood will result in the loss of human life, be specified in the same way as data about my recent vacation?
>

Not really.  Though the level of semantic detail may be different.
The approach should be the same.

> If not, then in what ways should they be specified differently?
>

Two equally important but very different scenarios:
Air traffic control information; relatively short term live
persistence (though long term archiving is important) probably only
needs a datetime stamp and geo-location tags to be semantically
relevant.

Medical device output and decision support needs multiple links to
controlled vocabularies and ontologies to cover the various semantics
along with the persistent version numbers and content of those
references.  Data may need to be live for weeks, months, etc. and
certainly archiving should be held for more than a century.

In both cases, lives are at stake.  I do not think that there is one
single approach across all domains.

My 2 cents,
Tim

-- 
============================================
Timothy Cook, MSc           +55 21 94711995
MLHIM http://www.mlhim.org
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
Skype ID == timothy.cook
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

• References:
  • What techniques do you employ to ensure that your data is preciselyand unambiguously specified?
    • From: "Costello, Roger L." <costello@m...>
  • RE: What techniques do you employ to ensure that your data isprecisely and unambiguously specified?
    • From: "Costello, Roger L." <costello@m...>