[foaf-dev] Linking foaf and other rdf documents/resources

Bruce Whealton bruce at whealton.info
Wed Jun 29 02:11:57 CEST 2011


Hello all,
                So, there are a few ways that one can link various profiles, or RDF FOAF files/resources.  I’m wondering if there is a best practice.
I had been using 
<foaf:knows>
        <foaf:Person>
...
         <rdfs:seeAlso rdf:resource=”http://url/pathto/foaf.rdf"/>
        </foaf:Person>
</foaf:knows>

But some FOAF profiles I’ve seen setup with method #2.
<rdf: Description rdf: about=”http://pathToFileAboutPerson/longstringofcharacters” >
      ... information about the person
</rdf: Description>

then further down there would be a 
<foaf: knows resource=”http://pathToFileAboutPerson/longstringofcharacters”/>

I assume that the about="http://pathToFileAboutPerson/longstringofcharacters” refers to a FOAF file but I guess it doesn’t have to link to a foaf file.
I wonder if there is a benefit to using method #2 or a best practice that favors this?  I can see that it might make it easier if one had to refer, more than once, to the resource that represents a person (through their FOAF profile) in a document.
As one uses more vocabularies and has more extensive rdf files, it becomes more likely that one is going to make numerous assertions about that person (resource).  
Most importantly though, will there be any difference in the ability of crawlers or other apps to follow the links between various FOAF profile files?
Thanks,
Bruce
++++++++++++++++++++++++++++++++++++++++++++++++++
Bruce Whealton, Owner Future Wave Designs
FOAF: http://whealton.info/BruceWhealton1/foaf.rdf
Vcard: http://whealton.info/BruceWhealton1/brucewhealtonvcard.html
Web Design and Development http://FutureWaveDesigns.com
http://futurewavedesigns.com/wordpress/
Web Technology wiki: http://futurewavedesigns.com/w/
++++++++++++++++++++++++++++++++++++++++++++++++++
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.foaf-project.org/pipermail/foaf-dev/attachments/20110628/aa45844f/attachment.htm 


More information about the foaf-dev mailing list