TK; The modified foaf model is also delivered with TBC - see the TopBraid library project. To use this, and similar models, create the file you want and use the Imports view to import the ontology.
The modifications of foaf are pretty much as the documentation says. foaf properties make heavy use of domain and range definitions. This causes a large number of properties to be displayed when an instance of a foaf class is created in Composer and other editors. There are also implications for reasoners. The foaf vocabulary is retained throughout the modified foaf file, so you can easily merge with other foaf files. In terms of your DOAP/DOAC/EARL ontologies, to modify them, copy them to your TBC workspace and edit as desired. Make sure the URIs of the resources remain the same so they refer to the same resources as the original models. I would also suggest changing the base URI to denote that your version of DOAP.owl, etc. is different than the originals. In case there is confusion, there are two senses of "import" in Composer. The first is as described here. If you want to refer to resources from another file without copying all of the resources into a file, then owl:imports is used. This is what the Imports view does in Composer. The second is importing a file/data store into triples from some other format. For example, when you import a spreadsheet, XML, relational store, etc., Composer converts the format to triples. If a file is already in a RDF serialization (.n3, .rdf, .rdfs, .owl, .nt) then Composer can directly read the file without any import mechanism. -- Scott On May 31, 11:23 am, TK <[email protected]> wrote: > TBC-users, > I want to make sure I am using the tool the way it was intended so I > have a few questions. > > FOAF -- > If I go to the canonical URIhttp://xmlns.com/foaf/0.1/using the > File:Import..., > I end up with a lot of data in TBC that at first seemed very > confusing. Then I found an edited FOAF file on Holger's blog (thanks > so much) which had these annotated modifications: > -- > This is a modified version of the official FOAF specification, > optimized for editing tools such as TopBraid. > Changes include: > - removed { ?p rdf:type rdf:Property } on properties that are also > owl:DatatypeProperty etc > - removed { ?p rdfs:domain owl:Thing } to prevent these properties > from showing up on all forms > - removed { ?p rdfs:range owl:Thing } especially for inverse > properties for the same reason > - removed subclass relationships into external ontologies such as > wordnet to keep the class tree flat > -- > * Why is it that the canonical version not be friendly to the editing > tools and what is lost by making these edits? > * Was it generated from a tool that was too verbose? or Should TBC > just filter out this redundant triples? > Ultimately, I'm trying to understand these changes such that I too can > clean up these ontologies so that they are readable and useful to > TBC. > > Other Ontologies -- > I'm looking at playing with DOAP (Description of a Program), DOAC > (Description of a Career), EARL (Evaluation and Reporting Language) , > etc. Lets take DOAP as a example so I can make sure I am using TBC > correctly. > I'm assuming that the process is the same: > - find the DOAP website http://trac.usefulinc.com/doap > - find the ontology. In this case it is not OWL but an > RDF-Shttp://usefulinc.com/ns/doap# > - using File:Import... I use import file from web and name the file > doap.rdf (should I have done doap.owl? gut says yes) > If this process is correct, then it would appear that I need to follow > a similar modification process like Holger did for foaf.owl > > I have another related question but I will ask it in another thread. > > --tk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. 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-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
