>General comment, I=20
>think that we need more examples of terms.
Apologies to Trish, but I found the synonyms helpful, only as I thought
that some of the synonyms of instrument didn't belong together
Perhaps a subterm under object "Equipment?" with several children
(listed here as synonyms)
[Tool/utensil/implement]: equipment which typically provides a
mechanical advantage in accomplishing a physical task, (e.g., hammer,
mortar, pestle, crowbar)
microtitre plate, test tube, pipette tip, cage, flask
[Instrument/device/machine/apparatus]: mechanical/electronic equipment
(e.g., Cytometer, Sequencer, PCR amplifier, Microarray Scanner,
Hybridization oven, autoclave, Mass Spec)
I expect users of OBI probably won't be recording too many details about
the tools or labware used in an experiment, but rather the details about
the instrumentation. Certainly all the terms I have seen posted on the
wiki seem to fall into the third category.=20
From: Trish Whetzel [mailto:whetzel@...
Sent: Tuesday, March 13, 2007 12:28 PM
To: Ryan Brinkman
Cc: Daniel Schober; obi-instrument-branch@...; frank
gibson; Luisa Montecchi; William Bug; Liju Fan; Philippe Rocca-Serra;
Subject: RE: [Obi-instrument-branch] Re-define Instrument term
There seems to be two avenues to follow, one is to make the=20
definition of 'instrument' more broad to include all of these physical,=20
manufactured types of objects,e.g. cage, microtiter plate, mass spec,
or two to propose new class(es) to account for cage, microtiter plate
state in the definition of instrument and these new class(es)=20
what the difference is (whatever that may be). If we are able to change=20
the lexical label for instrument to be something more general that too=20
may help, but I'm not sure if/when we are allowed to do that.
Although there were only 3 of us on the call, I thought that the action=20
item was to define 'instrument' more broadly to be able to further=20
subclass to include objects like cage, microtiter plate, mass spec etc.=20
Either way is fine with me, I think that if we create new classes for=20
objects like cage etc we will eventually see that these could have a=20
common parent, i.e. direct subclass from bfo:object that these new=20
classes can be children of.
**Can we agree which method we want to follow - define instrument more=20
broadly to include all these things or eventually propose to add a new=20
class for other types of physical objects and define instrument to=20
include, well what are the type it should include? General comment, I=20
think that we need more examples of terms.
As for 'tool', I think that Daniel proposed this as a synonym for=20
instrument but I understand here it is being proposed as a term itself,=20
following the second approach listed above. This mixes what the term and
it's encompassing definition should be with what are appropriate
for a term and is one reason that I wanted to not worry about synonyms=20
since it brings up these additional issues, trying to sort out what a=20
lexical label means without yet having an agreed on definition for the=20
term itself with the given label.
> Should the definition of instrument include the idea that is something
> mechanical or electronic? A mortars and pestles provide an advantage
> accomplishing the grinding up of cells (a physical step in a
> but I don't think this is something we would include under this
> Non-mechanical or electronic objects may be better served by being
> placed under a "tool/utensil/implements" class, likely disjoint from
> instruments. For example, I would propose that crowbars (mentioned in
> the call), and Trish's cage example are tools, not instruments. I
> of instruments as things that are (usually) plugged into an outlet, at
> least the modern equivalents (e.g., electronic scales).
> -----Original Message-----
> From: Trish Whetzel [mailto:whetzel@...]
> Sent: Tuesday, March 13, 2007 8:02 AM
> To: Daniel Schober
> Cc: obi-instrument-branch@...; frank gibson; Luisa
> Montecchi; William Bug; Ryan Brinkman; Liju Fan; Philippe Rocca-Serra;
> Susanna Sansone
> Subject: Re: [Obi-instrument-branch] Re-define Instrument term
> Quick question, would 'cage' (the cage that a mouse is kept in) fit as
> subclass of instrument using the definition: An instrument is an
> which provides an advantage in accomplishing a physical and/or
> step in a process. I'm not sure what is meant as a physical step and
> does the instrument need to provide an _advantage_ in accomplishing a
> step the process? The definition sounds like it might be a little too
> function related.
> As for synonyms, I wouldn't worry about those too much at this point
> that we can stay focused on finding an acceptable general definition
> OBI instrument.
> Of the terms from the attached doc, I prefer the definition of
> Manufactured Object (a physical object made by human beings) as that
> a broad definition that we can create further subclasses based on the
> types of physical objects that are proposed by the communities.
>> To summarize, I would propose the following branch top level classes
> for OBI:
>> * preferred_term: instrument
>> * synonym: device, tool, machine, utensil, equipment, hardware,
>> apparatus (WHERE: apparatus and machine indicate a somewhat
>> higher complexity, whereas tools implies a more primitive or
>> less complex nature of the object).
>> * definition(device-derived): An instrument is an object which
>> provides an advantage in accomplishing a physical and/or
>> analytical step in a process.
>> * definition_source: OBI.
>> then a subclass
>> * preferred_term: analytical_instrument
>> * definition(OBI-derived): An analytical instrument is an
>> instrument that is used to collect data and thereby provides
>> an advantage in accomplishing a physical and/or analytical
>> step in an analytical process.
>> * definition_source: OBI.
>> For a first orientation and (bad)definitions, I have scanned UMLS
>> Methathesaurus and Semantic Network for instrument related terms.
>> Find the results as txt file attached. It is just an overview what
> exists out
>> there terminologically....
>> Maybe people can also have a look at the last call noted posted on
>> before the next call on Friday.
>> Best regards,
>> Daniel Schober.