Scott, so you are saying like Irene, to have my ontology import foaf? I do like the Top Braid products. Ensemble requires a special server doesn't it? The costs for both the product and the server are hard for smaller businesses. Someday, though, I'd like to use these products. It might be good to offer a product that one can purchase and not also have to pay an ongoing fee. Purchasing software is a major expense for the web developer and when you add a monthly fee, that makes it even more difficult. Perhaps TB is targeting Organizations and such. Bruce
On Nov 2, 10:15 am, Scott Henninger <[email protected]> wrote: > Bruce; As Irene states, the best practice is to create an ontology and > use owl:imports to import the foaf model. Then the application uses > your ontology, which contain foaf and your ontology, provided the > application can properly apply owl:imports. > > Just as a side-note, Ensemble is a collaborative Web-based interface > that is basically a Wiki out-of-the-box. The interface can be > customized to provide features as desired. > > -- Scott > > On Nov 1, 6:25 pm, "Irene Polikoff" <[email protected]> wrote: > > > > > > > > > Bruce, > > > If your application was running on TopBraid Live server, you would need to > > create myfoaf ontology, import foaf into it using owl:import statement and > > then define the two extra properties in myfoaf. The TopBraid infrastructure > > would take care of getting foaf and (virtually) merging it with myfoaf to > > derive the full model. > > > I can't speak for how Drupal or Semantic Media Wiki work and what issues > > they would (or not) have in this scenario. Of course, if the import approach > > did not work and you decided to duplicate all of foaf in myfoaf, there would > > be no reason for you to also include foaf. > > > Regards, > > > Irene > > > -----Original Message----- > > From: [email protected] > > > [mailto:[email protected]] On Behalf Of Bruce Whealton > > Sent: Tuesday, November 01, 2011 7:03 PM > > To: TopBraid Suite Users > > Subject: [topbraid-users] Question: re expanding an existing ontology > > > Hello, > > I was wondering what the best practice is for working with > > custom vocabularies that one extends from existing vocabularies. For > > example, suppose one starts with FOAF and then decides 2 new terms are > > needed for an application. This would give, > > myfoaf. > > I am guessing I would publish myfoaf on my own domain. Ok, > > is there a way to say, import foaf from where it is defined/specified > > and then add these properties? > > My applications will use Drupal and MediaWiki with the > > Semantic MediaWiki extensions. Has anyone used these? I assume there > > would be a problem if I refer to a property that is not part of the > > foaf specification.. Both of these have ways for importing > > vocabularies. Much duplication can happen if one's extended foaf > > ontology had just two new fields and one was importing into the > > software both foaf and myfoaf, and my foaf had all of foaf plus 2 new > > terms. > > Sorry, I'm not sure why I am getting hung up on this. > > Bruce > > > -- > > You received this message because you are subscribed to the Google > > Group "TopBraid Suite Users", the topics of which include TopBraid Composer, > > TopBraid Live, TopBraid Ensemble, SPARQLMotion 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 > > athttp://groups.google.com/group/topbraid-users?hl=en -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion 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
