No need to define a prefix for each. Prefixes are just a convenient way to define URIs. So for example you can have: <http://topquadrant.com/foaf/ScottHenninger#me> foaf:knows <http:// fwwebdev.com/foaf/BruceWhealtonJr/foaf.rdf#me> <http://topquadrant.com/foaf/ScottHenninger#me> foaf:knows <http:// joe.org/foaf/joe#me> <http://topquadrant.com/foaf/ScottHenninger#me> foaf:knows <http:// bill.org/foaf/bill#me>
etc... If you decode to define a prefix for Joe, i.e.: @prefix joe: <http://joe.org/foaf/joe#> ...then joe:me expands to <http://joe.org/foaf/joe#me> by replacing the prefix "joe:" with the namespace "http://joe.org/foaf/joe#";. -- Scott On Jul 24, 3:22 pm, brucewhealton <[email protected]> wrote: > Scott, > I think the latter is correct, I want to have a foaf file > refer to others. However, if there are 100s of people that one knows, > should we create a prefix for each and every one? > How do I say this is me: > <http://fwwebdev.com/foaf/BruceWhealtonJr/foaf.rdf#me> inside my foaf > file? > Bruce > > On Jul 24, 11:48 am, Scott Henninger <[email protected]> > wrote: > > > On 7/23/11 7:55 PM, brucewhealton wrote:1) Suppose I have some FOAF files > > that I want to link to using foaf:knows. The path to each persons foaf file > > ishttp://fwwebdev.com/foaf/BruceWhealtonJr/foaf.rdfsoto refer to me, I'd > > usehttp://fwwebdev.com/foaf/BruceWhealtonJr/foaf.rdfIcould use a prefix > > defined within my RDF or OWL file I am creating inside TBC or I could use > > the full path as shown above. Is there another best practice? Maybe setup a > > namespace that equalshttp://fwwebdev.com/foaf/andcall it fwfoaf. Does that > > make sense?This part of the question has me confused a bit. I'll take a > > couple of guesses to see if we can get any closer. > > If you want to find out how to perform operations - inference, query, etc. > > across multiple foaf files I'd suggest creating a file named allFOAFs.ttl > > that owl:imports all of the foaf files you want. The you can operate on an > > entire set of foaf files from one open file. > > If you want one foaf file to refer to another one, and I suspect this is > > what do do want, then it's just a matter of aligning the URIs. There isn't > > a need to refer to the file itself. Just the URIs that you want to operate > > with. So if I know you then I'd add the following to my foaf file: > > <http://topquadrant.com/foaf/ScottHenninger#me>foaf:knows<http://fwwebdev.com/foaf/BruceWhealtonJr/foaf.rdf#me> > > If I had a couple of prefixes defined: > > @prefix scott: <http://topquadrant.com/foaf/ScottHenninger#> > > @prefix bruce:<http://fwwebdev.com/foaf/BruceWhealtonJr/foaf.rdf#> > > ...then I could write the aforementioned triple as: > > scott:me foaf:knows bruce:me > > -- Scott -- 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
