Thanks Irene. It took me a while to reconfigure things, but now I've got the imports working properly as you suggested. Rich
On Tuesday, July 15, 2014 10:17:30 AM UTC-7, Irene Polikoff wrote: > > You only need a statement <baseURU1> owl:imports <baseURI2>. It is better > to also have a statement <baseURI1> rdf:type owl:Ontology (this way you > will see imports in the Imports tab), but not 100% necessary. > > > > *From:* [email protected] <javascript:> [mailto: > [email protected] <javascript:>] *On Behalf Of *Rich Keller > *Sent:* Tuesday, July 15, 2014 12:00 PM > *To:* [email protected] <javascript:> > *Subject:* Re: [topbraid-users] Best TBC Practices re: segregating > instances from classes > > > > But owl:imports is a relationship between two ontologies. There is no > ontology defined in the instances file. Are you suggesting that there > should be a second ontology defined in the instances file, and that the > purpose of this ontology is simply to import the base ontology? Rich > > On Monday, July 14, 2014 11:13:30 PM UTC-7, Scott Henninger wrote: > > Just to add a bit to this, owl:imports, as designed in TopBraid Suite, is > precisely the "include capability" you seek. > > -- Scott > > On 7/14/2014, 6:24 PM, Irene Polikoff wrote: > > Best practice is to maintain schema and instances as separate graphs and > owl:import schema into the instances graph. > > > > Hope this helps, > > > > Irene > > > On Jul 14, 2014, at 5:18 PM, Rich Keller <[email protected]> wrote: > > Hi. I was wondering if you could recommend any best practices for > separating ontology classes from instances in TBC. I currently have a set > of 3 or 4 ontologies that comprise a project I’m developing. I have code > that generates (large numbers of) instances of the classes in these > ontologies. > > Originally, my practice was to actually output the base ontology plus > instances into a separate file with a different base namespace so that I > could open up the ontology+instances in TBC. But it gets messy and > confusing to maintain two separate namespaces. > > Now I am generating the instances just as a set of triples without any > base ontology in a separate file. Then I use TBC ‘import triples’ to import > these triples on top of the base model. But if I want to make any changes > to the base ontology, I will have to save the triples plus the base model, > and I don’t want to do that. > > Maybe what I want is some sort of include capability. > > I think this must be a common issue, so I’m probably missing something > basic here. > > Any suggestions? > Thanks, Rich > > -- > -- You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include Enterprise > Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid > Insight, SPARQLMotion, SPARQL Web Pages and SPIN. > To post to this group, send email to > [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/topbraid-users?hl=en > --- > You received this message because you are subscribed to the Google Groups > "TopBraid Suite Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > -- > -- You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include Enterprise > Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid > Insight, SPARQLMotion, SPARQL Web Pages and SPIN. > To post to this group, send email to > [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/topbraid-users?hl=en > --- > You received this message because you are subscribed to the Google Groups > "TopBraid Suite Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > > -- > -- You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include Enterprise > Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid > Insight, SPARQLMotion, SPARQL Web Pages and SPIN. > To post to this group, send email to > [email protected] <javascript:> > To unsubscribe from this group, send email to > [email protected] <javascript:> > For more options, visit this group at > http://groups.google.com/group/topbraid-users?hl=en > --- > You received this message because you are subscribed to the Google Groups > "TopBraid Suite Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
