<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>FOAFMap: Web2.0 meets the Semantic Web</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Laboratoire LaLICC</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>e Paris IV</institution>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2003</year>
      </pub-date>
      <abstract>
        <p>FOAFMap - http://foafmap.net - is an online service providing geolocation with a FOAF and Google Maps mashup, as a mix of both Semantic Web and Web 2.0 technologies. FOAFMap users don't need to register, but just have to provide a FOAF ¯le URL, which could point to either a personal pro¯le or a group document. After identifying the document type (personal pro¯le or group), the service retrieves people referenced in the ¯le. For each people found, the script parses his personal FOAF ¯le - if any - and extracts geolocation information that he may have provided with Geo Vocabulary2. Then, it displays these people on a Google Map, with other personal information: name, weblog or email, and even a resized picture if available on the pro¯le. As parsing the pro¯le and retrieving ¯les can be really long when there is a lot of people referenced in it, FOAFMap allows users to cache the created map in its ¯lesystem, so that it can then be displayed faster. Since tagging became a common practice in Web2.0 services, FOAMap also allows people to tag their maps, but once again, tags are not created locally but extracted from FOAF ¯les. Actually, the retrieved tags are foaf:interest properties of the user or group mentioned in the ¯le. Tags are identi¯ed with their URL, and FOAFMap provides a way to see aliases of the same tag, as anyone can provide the title he wants using dc:title. Like most of the tools using folksonomies, FOAFMap allows people to see who shares common tags,</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Motivations</title>
      <p>Web 2.0 geolocation services such as Frappr!1 allow users to create, or subscribe
to, groups and related maps.</p>
      <p>
        FOAFMap's idea is to provide an equivalent service using decentralized
pro¯le and data management, thanks to Semantic Web principles and FOAF[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
vocabulary. Thus, people manage themselves their data while the tool just reads,
understands and displays it in an appropriate way.
so that you can ¯nd people with the same interests as you3. It also provides an
RSS 1.0 feed of the latest created and updated maps.
      </p>
      <p>
        FOAFMap's source code strongly depends on PHOAF4, a PHP5 API based
on RAP[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] providing a set of classes and methods for easy information extraction
from FOAF ¯les without any knowledge of FOAF and RDF. FOAFMap and
PHOAF handle FOAF and RELATIONSHIP[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] vocabularies to identify relations
between people - RAP inference engine is used so that relations can be retrieved
either they are de¯ned by foaf:knows or rel:xxx. Finally, FOAFMap also uses
MySQL to store some data as users and tags, and runs on LAMP.
3
      </p>
    </sec>
    <sec id="sec-2">
      <title>Conclusion and Future Work</title>
      <p>FOAFMap certainly won't evolve a lot in the future, as the goal was mainly to
develop a basic prototype that could show connections between Semantic Web
and user-oriented model of Web 2.0. Yet, I hope that such services can help
end-users to see what FOAF and Semantic Web can bring us.
3 http://foafmap.net/tag/3
4 http://gna.org/projects/phoaf</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Brickley</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miller</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>FOAF Vocabulary Speci¯cation</article-title>
          .
          <source>Technical report, FOAF Project</source>
          ,
          <year>2003</year>
          . http://xmlns.com/foaf/0.1
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Oldakowski</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizer</surname>
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Westphal</surname>
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>RAP: RDF API for PHP. In Scripting for the Semantic Web</article-title>
          , May
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>David</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vitiello</surname>
          </string-name>
          , E.:
          <article-title>RELATIONSHIP: A vocabulary for describing relationships between people http://vocab</article-title>
          .org/relationship/
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>