Re: [Obi-instrument-branch] organizations

0 views
Skip to first unread message

frank gibson

unread,
Dec 9, 2008, 4:53:20 AM12/9/08
to Melanie Courtot, OBI Relations Mailing List, obi-instru...@lists.sourceforge.net
On Mon, Dec 8, 2008 at 7:23 PM, Melanie Courtot <mcou...@gmail.com> wrote:
> Dear instrumenters,
>
> The biomaterial branch added an example of organization, Affymetrix,
> as an instance of the organization class.
> This is a template which goal is to show how to proceed with those,
> instances in general will be stored in a separate file.
>
> The relation has_manufacturer/vendor/supplier has been added to the
> agenda for the relation call tomorrow: there is currently a relation
> is_manufactured_by, do we need its inverse relation
> (is_manufacturer_of), and do we want to change its label to something
> more generic (maybe has_supplier/provider as suggested by Frank at http://sourceforge.net/tracker/index.php?func=detail&aid=2310029&group_id=177891&atid=886178)
> and then use roles to differentiate between vendor/manufacturer


Just to clarify, we need the relation is_manufacturer_of, creating the
inverse of this would be appropriate. The relation is_supplier_of
would be in addition to the manufacture_of relation, not in replace
of. However, manufactures can also be suppliers e.g

gel tank
Sigma is_manufacturer_of gel_tank
Sigma is_supplier_of gel_tank

FIlter paper
paper_products is_manufacturer_of filter paper
fisher_scientific is_supplier_of filter paper

Frank


>
> I moved that item to first on the list for discussion on the relation
> call (it has its advantages to write down the agenda ;) ) as we are
> ready to move on on this and it would help us progress on our mini use
> case (a flow cytometer has manufacturer BD). We will then be able to
> attack the parameter issue.
>
> Thanks,
> Melanie
>
> ---
> Mélanie Courtot
> TFL- BCCRC
> 675 West 10th Avenue
> Vancouver, BC
> V5Z 1L3, Canada
>
>
>
>
>
> ------------------------------------------------------------------------------
> 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-instrument-branch mailing list
> Obi-instru...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/obi-instrument-branch
>

--
Frank Gibson, PhD
http://peanutbutter.wordpress.com/

------------------------------------------------------------------------------
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-instrument-branch mailing list
Obi-instru...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/obi-instrument-branch

Daniel Schober

unread,
Dec 9, 2008, 5:51:08 AM12/9/08
to frank gibson, OBI Relations Mailing List, obi-instru...@lists.sourceforge.net
Hi instrumenteers.

1. I think implementing a few example instances for the Oonomasticon exteriment is a good idea.

2. Yes, I would think all of these are needed and for the moment they are siblings, because 'is vendor of' is not always a subrelation of 'is supplier of'. I would suggest the following relation pairs:
is supplier of     -     has supplier
is vendor of     -     has vendor   ('is sold by' is not inharmony to the naming conventions)
is manufacturer of     -     has manufacturer

I would stick with the 'is manufacturer of'-'has manfacturer' pair and substitute/remove 'is manufactured by'. The reason of this is that it seem that the is_x_of - has_x naming convention allows to avoid lexical heterogenity. In our example above, the alternative convention is_x_of - is_xed_by  will lead to the lexical heterogenous pair
is vendor of     -     is vended by  or 'is sold by'

3. Is the domain of these a role , e.g. vendor role or the instance of organisation ?

Cheers, Daniel.
-- 
__________________________________________________________________________________________

Dr. Daniel Schober

NET Project - Ontologist

The European Bioinformatics Institute   email:  sch...@ebi.ac.uk
EMBL Outstation - Hinxton               direct: +44 (0)1223 494410
Wellcome Trust Genome Campus            fax: +44 (0)1223 494 468
Cambridge CB10 1SD, UK                 	Room: A3-141 (extension building)

Project page: www.ebi.ac.uk/net-project

Personal page:    http://www.ebi.ac.uk/Information/Staff/person_maint.php?s_person_id=734
Former home page: http://www.bioinf.mdc-berlin.de/%7Eschober/

frank gibson

unread,
Dec 9, 2008, 6:45:23 AM12/9/08
to Daniel Schober, OBI Relations Mailing List, obi-instru...@lists.sourceforge.net
On Tue, Dec 9, 2008 at 10:51 AM, Daniel Schober <sch...@ebi.ac.uk> wrote:
> Hi instrumenteers.
>
> 1. I think implementing a few example instances for the Oonomasticon
> exteriment is a good idea.
>
> 2. Yes, I would think all of these are needed and for the moment they are
> siblings, because 'is vendor of' is not always a subrelation of 'is supplier
> of'. I would suggest the following relation pairs:
> is supplier of - has supplier
> is vendor of - has vendor ('is sold by' is not inharmony to the
> naming conventions)
> is manufacturer of - has manufacturer

The is_supplier relation is a synonym of is vendor_of. If you want to
be more specific in the mechanism of supply, we could do this by
roles, e.g vendor_role, distributor_role, manufacturer_role

>
> I would stick with the 'is manufacturer of'-'has manfacturer' pair and
> substitute/remove 'is manufactured by'. The reason of this is that it seem
> that the is_x_of - has_x naming convention allows to avoid lexical
> heterogenity. In our example above, the alternative convention is_x_of -
> is_xed_by will lead to the lexical heterogenous pair
> is vendor of - is vended by or 'is sold by'

Something that is manufactured, occurs by the organization
participating in a process. This is why we have the relation,
is_manufactured_by as opposed to is_manufacture_of. The relations
realizes is of similar form. Following this form the deliverables we
need are:

is_manufactured_by <--> manufactures

is_supplied_by <--> supplies

>
> 3. Is the domain of these a role , e.g. vendor role or the instance of
> organisation ?

The domain of both is artifact_object. The range is person(instance of
homo sapiens) or organiszation

Frank

> __________________________________________________________________________________________
>
> Dr. Daniel Schober
>
> NET Project - Ontologist
>
> The European Bioinformatics Institute email: sch...@ebi.ac.uk
> EMBL Outstation - Hinxton direct: +44 (0)1223 494410
> Wellcome Trust Genome Campus fax: +44 (0)1223 494 468
> Cambridge CB10 1SD, UK Room: A3-141 (extension building)
>
> Project page: www.ebi.ac.uk/net-project
>
> Personal page:
> http://www.ebi.ac.uk/Information/Staff/person_maint.php?s_person_id=734
> Former home page: http://www.bioinf.mdc-berlin.de/%7Eschober/
>
>

--

Alan Ruttenberg

unread,
Dec 9, 2008, 11:59:06 AM12/9/08
to frank gibson, OBI Relations Mailing List, obi-instru...@lists.sourceforge.net
I'd like to see a def of supplied-by.

-Alan

frank gibson

unread,
Dec 9, 2008, 1:27:46 PM12/9/08
to Alan Ruttenberg, OBI Relations Mailing List, obi-instru...@lists.sourceforge.net
On Tue, Dec 9, 2008 at 4:59 PM, Alan Ruttenberg
<alanrut...@gmail.com> wrote:
> I'd like to see a def of supplied-by.

It is currently in the tracker item at this link
https://sourceforge.net/tracker2/index.php?func=detail&aid=2310029&group_id=177891&atid=886178

Frank


>
> -Alan
>
> On Tue, Dec 9, 2008 at 6:45 AM, frank gibson <Frank....@ncl.ac.uk> wrote:

Reply all
Reply to author
Forward
0 new messages