[Obi-instrument-branch] identifies<->identified_by
frank gibson
We need to be able to link artifact_objects to information about that
object. For example, product information - batch number, lot number,
catalogue number, devices - model number serial number etc.
In order to do this the identifies<->identified_by relation has been
proposed which is a relation between an artifact object and an
information entity which aims to establish identity of the artifact
object.
Comments?
Frank
--
Frank Gibson, PhD
http://peanutbutter.wordpress.com/
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Obi-instrument-branch mailing list
Obi-instru...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/obi-instrument-branch
Alan Ruttenberg
What do lot numbers and batch numbers identify.
I have raised issue with what identification is, so for the moment my
preference is to use the is_about and inheres to to relate these
information entities to their bearers.
The relation would, in any case, be in scope for IAO, rather than OBI.
Regards,
Alan
frank gibson
<alanrut...@gmail.com> wrote:
> Definition?
> What do lot numbers and batch numbers identify.
A lot number is probably synonymous with a serial number. A batch
number identifies a particular "batch" e.g the culture medium made on
Tuesday, as opposed to the culture medium made on Wedensday
> I have raised issue with what identification is, so for the moment my
> preference is to use the is_about and inheres to to relate these
> information entities to their bearers.
Can you give an example how you inheres_in is_about would work?
> The relation would, in any case, be in scope for IAO, rather than OBI.
Thats probably irrelevant, it links materials with information
Frank
>
> Regards,
> Alan
>
>
> On Wed, Nov 26, 2008 at 5:07 AM, frank gibson <Frank....@ncl.ac.uk> wrote:
Alan Ruttenberg
> On Wed, Nov 26, 2008 at 5:33 PM, Alan Ruttenberg
> <alanrut...@gmail.com> wrote:
>> Definition?
>> What do lot numbers and batch numbers identify.
>
> A lot number is probably synonymous with a serial number. A batch
> number identifies a particular "batch" e.g the culture medium made on
> Tuesday, as opposed to the culture medium made on Wedensday
>
>> I have raised issue with what identification is, so for the moment my
>> preference is to use the is_about and inheres to to relate these
>> information entities to their bearers.
>
> Can you give an example how you inheres_in is_about would work?
inheres_in relates the serial number to the bearer of the serial
number, i.e. if there is a metal tag on the instrument with the serial
number that is the bearer.
is_about collects what the serial number is about. For batch, for
instance, we would say it is about the entity as well as the process
of manufacturing.
>
>
>> The relation would, in any case, be in scope for IAO, rather than OBI.
>
> Thats probably irrelevant, it links materials with information
Don't understand what you mean.
-Alan
frank gibson
<alanrut...@gmail.com> wrote:
> On Wed, Nov 26, 2008 at 11:39 AM, frank gibson <Frank....@ncl.ac.uk> wrote:
>> On Wed, Nov 26, 2008 at 5:33 PM, Alan Ruttenberg
>> <alanrut...@gmail.com> wrote:
>>> Definition?
>>> What do lot numbers and batch numbers identify.
>>
>> A lot number is probably synonymous with a serial number. A batch
>> number identifies a particular "batch" e.g the culture medium made on
>> Tuesday, as opposed to the culture medium made on Wedensday
>>
>>> I have raised issue with what identification is, so for the moment my
>>> preference is to use the is_about and inheres to to relate these
>>> information entities to their bearers.
>>
>> Can you give an example how you inheres_in is_about would work?
>
> number, i.e. if there is a metal tag on the instrument with the serial
> number that is the bearer.
>
> is_about collects what the serial number is about. For batch, for
> instance, we would say it is about the entity as well as the process
> of manufacturing.
so that:
culture_medium bears some (batch_number and (is_about some
manufacturing process))
How do I say, the batch number is XXXYYY0000111, a particular instance
of batch number?
>>
>>
>>> The relation would, in any case, be in scope for IAO, rather than OBI.
>>
>> Thats probably irrelevant, it links materials with information
>
> Don't understand what you mean.
as in, it does not really matter, there are equal cases for both, and
I don't care
Frank
>
> -Alan
Alan Ruttenberg
> On Wed, Nov 26, 2008 at 5:42 PM, Alan Ruttenberg
> <alanrut...@gmail.com> wrote:
>> On Wed, Nov 26, 2008 at 11:39 AM, frank gibson <Frank....@ncl.ac.uk> wrote:
>>> On Wed, Nov 26, 2008 at 5:33 PM, Alan Ruttenberg
>>> <alanrut...@gmail.com> wrote:
>>>> Definition?
>>>> What do lot numbers and batch numbers identify.
>>>
>>> A lot number is probably synonymous with a serial number. A batch
>>> number identifies a particular "batch" e.g the culture medium made on
>>> Tuesday, as opposed to the culture medium made on Wedensday
>>>
>>>> I have raised issue with what identification is, so for the moment my
>>>> preference is to use the is_about and inheres to to relate these
>>>> information entities to their bearers.
>>>
>>> Can you give an example how you inheres_in is_about would work?
>>
>> inheres_in relates the serial number to the bearer of the serial
>> number, i.e. if there is a metal tag on the instrument with the serial
>> number that is the bearer.
>>
>> is_about collects what the serial number is about. For batch, for
>> instance, we would say it is about the entity as well as the process
>> of manufacturing.
>
> so that:
>
> culture_medium bears some (batch_number and (is_about some
> manufacturing process))
The bearer isn't the culture unless it is written on it.
This is a bit tricky and needs to be worked out more carefully.
There is a protocol application. The medium is part of the specified output.
The batch number is about the protocol application, and about the output.
Typically, the containers that the media are shipped in and the plates
are bar coded and the bar code encodes the batch number. There may be
other bearers, such as an information system.
Obviously we don't want to say all this explicitly every time we have
a batch number. But we need to get the details straightened out, along
the lines of the instrument settings example I sent out for review.
-Alan
frank gibson
<alanrut...@gmail.com> wrote:
> On Wed, Nov 26, 2008 at 11:54 AM, frank gibson <Frank....@ncl.ac.uk> wrote:
>> On Wed, Nov 26, 2008 at 5:42 PM, Alan Ruttenberg
>> <alanrut...@gmail.com> wrote:
>>> On Wed, Nov 26, 2008 at 11:39 AM, frank gibson <Frank....@ncl.ac.uk> wrote:
>>>> On Wed, Nov 26, 2008 at 5:33 PM, Alan Ruttenberg
>>>> <alanrut...@gmail.com> wrote:
>>>>> Definition?
>>>>> What do lot numbers and batch numbers identify.
>>>>
>>>> A lot number is probably synonymous with a serial number. A batch
>>>> number identifies a particular "batch" e.g the culture medium made on
>>>> Tuesday, as opposed to the culture medium made on Wedensday
>>>>
>>>>> I have raised issue with what identification is, so for the moment my
>>>>> preference is to use the is_about and inheres to to relate these
>>>>> information entities to their bearers.
>>>>
>>>> Can you give an example how you inheres_in is_about would work?
>>>
>>> inheres_in relates the serial number to the bearer of the serial
>>> number, i.e. if there is a metal tag on the instrument with the serial
>>> number that is the bearer.
>>>
>>> is_about collects what the serial number is about. For batch, for
>>> instance, we would say it is about the entity as well as the process
>>> of manufacturing.
>>
>> so that:
>>
>> culture_medium bears some (batch_number and (is_about some
>> manufacturing process))
>
yeah, this is a problem. I need to say the 10ml of culture medium feed
to my cells on Tuesday is from batch 10 and the 10mls fed to my cells
on Friday was from batch 11. The identifies relation would seem more
suitable here than inheres_in
>
> This is a bit tricky and needs to be worked out more carefully.
> There is a protocol application. The medium is part of the specified output.
> The batch number is about the protocol application, and about the output.
> Typically, the containers that the media are shipped in and the plates
> are bar coded and the bar code encodes the batch number. There may be
> other bearers, such as an information system.
All is correct, but are you saying that if you take 10mls out of the
jar, you can no longer say it has a batch number?
>
> Obviously we don't want to say all this explicitly every time we have
> a batch number.
This I agree with
But we need to get the details straightened out, along
> the lines of the instrument settings example I sent out for review.
Several examples would help, yes
Frank
>
> -Alan
Alan Ruttenberg
No. I'm saying the information artifact that is the batch number still
exists and is still about the medium or its parts.
I'm thinking the simplest thing to do is have an instance of batch
number (gdp) that is about the process and the medium (and parts
thereof). We need not specify what the batch number inheres in unless
we know it.(open world and all that).
If you want to find out about the batch number of something you would
query for batch numbers about it and then look for the process it is
also about.
-Alan
frank gibson
Yes, thats fine,
>
> I'm thinking the simplest thing to do is have an instance of batch
> number (gdp) that is about the process and the medium (and parts
> thereof). We need not specify what the batch number inheres in unless
> we know it.(open world and all that).
Well I need to say the 10mls of culture medium I fed my cells has a
batch number. This is the statement I need to make. How do I do it?
>
> If you want to find out about the batch number of something you would
> query for batch numbers about it and then look for the process it is
> also about.
Mostly the query is "What is the batch number of this product", rather
"than what does the batch number mean"?
Frank
> --~--~---------~--~----~------------~-------~--~----~
> informatio...@googlegroups.com
> To change settings, visit
> http://groups.google.com/group/information-ontology
> -~----------~----~----~----~------~----~------~--~---
Alan Ruttenberg
relation has_label to be added to IAO (not sure what the name should be)
in OBI:
Class Batch number subclass of information content entity
is_about some protocol application
is_about some material entity
has_label exactly 1
Instance <10 mls of culture medium> type: whatever
Instance b1 : batch number
b1 is_about <10 mls of culture medium>
b1 has_label < the batch number >
if you know something about the process then
b1 is_about process and <whatever you know about the process>
>
>>
>> If you want to find out about the batch number of something you would
>> query for batch numbers about it and then look for the process it is
>> also about.
>
> Mostly the query is "What is the batch number of this product", rather
> "than what does the batch number mean"?
pseudo sparql to retrieve the batch number for your 10ml.
select ?bnumber
where
?batch-number-instance :a <Batch number>.
?batch-number-instance is_about <10 mls of culture medium>.
?batch-number-instance has_label ?bnumber.
(I've used <> where one would use identifiers )
-Alan
frank gibson
>
> relation has_label to be added to IAO (not sure what the name should be)
Well, unless you are referring to the physical_material, the has_label
is just a synonym for is_identified_by? As the purpose of having a
label is to identify - In the first instance to distinguish between
individuals of the same class - and possibly, but not exclusively to
distinguish between individuals of other classes.
I am not clear in what you actually mean when you say has_label. Could
you write some sort of a quick definition, and domain and range?
Frank
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
frank gibson
Just preparing for the relations call scheduled for later today.
Cheers
Frank
On Tue, Dec 9, 2008 at 11:59 AM, frank gibson <Frank....@ncl.ac.uk> wrote:
> [snip]
>>
>> relation has_label to be added to IAO (not sure what the name should be)
>
> Well, unless you are referring to the physical_material, the has_label
> is just a synonym for is_identified_by? As the purpose of having a
> label is to identify - In the first instance to distinguish between
> individuals of the same class - and possibly, but not exclusively to
> distinguish between individuals of other classes.
>
> I am not clear in what you actually mean when you say has_label. Could
> you write some sort of a quick definition, and domain and range?
>
> Frank
>
>
>>
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
> The future of the web can't happen without you. Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> Obi-relations mailing list
> Obi-re...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/obi-relations
>
--
Frank Gibson, PhD
http://peanutbutter.wordpress.com/
------------------------------------------------------------------------------