Search Mailing List Archives
[protege-discussion] Included project etiquette in ProtegeFrames
Andrew.YOUNG at Tenix.com
Wed Dec 12 13:19:16 PST 2007
Thank you Samson,
Exactly the problem. I'm using XML format so I'll change the names in
my ETL tool before including.
From: protege-discussion-bounces at mailman.stanford.edu
[mailto:protege-discussion-bounces at mailman.stanford.edu] On Behalf Of
Sent: Thursday, 13 December 2007 4:09 AM
To: User support for Core Protege and the Protege-Frames editor
Subject: Re: [protege-discussion] Included project etiquette in
Usually instances included from multiple projects do not get merged. I
know of only one way that can happen: Some instances in Project 1 and
Projects 2 have the same instance names. If that's the case, you can add
the :NAME slot, in Project 1 and Project 2, to the classes that have
instances with shared instance names and rename them. (Alternatively,
open the .pins files and edit the instance names directly.)
YOUNG Andrew wrote:
> Hi guys,
> I'm trying to bundle several Frame projects - each with the same
> ontology, but different instances - together. "Including" these
> Projects into a base project ends in a merging of instances due to the
> ontologies being the same. For example If I "include" 10 instances in
> Project 1 with 15 instances in Project 2, I don't get 25 instances, I
> get 15 with the first 10 having two values for each slot.
> How do I stop these instances being overwritten (short of renaming
> each class and slot in each project to be included!).
> Can I use metaclasses and metaslots?
Samson Tu email: swt at stanford.edu
Senior Research Scientist web: www.stanford.edu/~swt/
Center for Biomedical Informatics Research phone: 1-650-725-3391
Stanford University fax: 1-650-725-7944
protege-discussion mailing list
protege-discussion at lists.stanford.edu
Instructions for unsubscribing:
The contents of this e-mail including any attachments are intended only
for the person or entity to which this e-mail is addressed. If you are not,
or believe you may not be, the intended recipient, please advise the sender
immediately by return e-mail, delete this e-mail and destroy any copies.
Tenix does not warrant nor guarantee that this email communication is free
from errors, virus, interception or interference.
More information about the protege-discussion