Hi Ted Thanks, for your considerations.
But If I map the class Actor with foaf:Person, vcard:VCard and dbpedia:Actor classes (certainly handle by RDF), as following <http://www.example.com#actor_1 <http://www.example.com/#actor_1>> <rdf:type> <dbpedia:Actor> . <http://www.example.com#actor_1 <http://www.example.com/#actor_1>> <rdf:type> <foaf:Person> . <http://www.example.com#actor_1 <http://www.example.com/#actor_1>> <rdf:type> <vcard:VCard> . An actor could be a foaf:Person but an vcard:VCard, what about consistency and inference? Thanks in advance for your help Chris On Wed, Nov 10, 2010 at 12:06 AM, Ted Thibodeau Jr < [email protected]> wrote: > On Nov 5, 2010, at 7:54 PM, Christian Rivas <[email protected]> > wrote: > > > Hi Leigh > > > > you are absolutely right but what happen if I need to reuse > > a ontology term that belong to a different Domain > > as I exemplify before? > > > > Should I map Actor with foaf:Person and vcard:VCard and dbpedia:Actor > classes? > > > > Thanks for your help > > Sure! There are no rules anywhere that say you can or should only use one > ontology -- and in fact this is why there's the whole xmlns rigmarole. > > If you do have one ontology that does everything you need, great -- that > can lower confusion for people and minimize server requests when > dereferencing those terms. But if you don't? Cherry-pick the terms that make > the most sense from however many ontologies you need. > > RDF was made for sparse data -- and it can handle everything you've laid > out here. > > Be seeing you, > > Ted > > Sent from my iPhone, which doesn't have my .sig files
