<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 10">
<meta name=Originator content="Microsoft Word 10">
<link rel=File-List href="cid:filelist.xml@01C34A1A.5CB3D3C0">
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]-->
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
span.EmailStyle17
{mso-style-type:personal-compose;
mso-style-noshow:yes;
mso-ansi-font-size:10.0pt;
mso-bidi-font-size:10.0pt;
font-family:Arial;
mso-ascii-font-family:Arial;
mso-hansi-font-family:Arial;
mso-bidi-font-family:Arial;
color:windowtext;}
span.SpellE
{mso-style-name:"";
mso-spl-e:yes;}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:464156157;
mso-list-type:hybrid;
mso-list-template-ids:846770108 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
</style>
<![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple style='tab-interval:.5in'>
<div class=Section1>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Here’s what I’ve been thinking could be the three
ways to keep FOAF files in sync between a centralized service (like <span
class=SpellE>FOAFster</span>) and a decentralized approach – where everyone
had possession of their own FOAF file.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<ol style='mso-margin-top-alt:0in' start=1 type=1>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;tab-stops:list .5in'><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Opt-in<o:p></o:p></span></font></li>
</ol>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>In this first scenario, an end-user comes to the <span
class=SpellE>FOAFster</span> environment with a ‘kosher’ FOAF file.
<span style='mso-spacerun:yes'> </span>By kosher I mean it adheres to the current
‘master’ version of FOAF that exists (somewhere in FOAF we can I
assume – maintained by the FOAF gods.)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>The end-user ‘seeds’ the system with their own
FOAF file – allowing it to now be intermeshed with the rest of the FOAF-based
social network.<span style='mso-spacerun:yes'> </span><span class=GramE>When
the end-user deposits their original FOAF file, they also <span class=SpellE>signidfy</span>
an ftp account, where they’d like updates to be sent.</span> <span
style='mso-spacerun:yes'> </span>As each additional ‘friend’
or ‘friend of a friend’, etc. gets added to the end-user file, it
is mirrors back to the outside ftp location.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<ol style='mso-margin-top-alt:0in' start=2 type=1>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;tab-stops:list .5in'><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Opt-out<o:p></o:p></span></font></li>
</ol>
<p class=MsoNormal style='margin-left:.25in;text-indent:-13.5pt'><font size=2
face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:4.5pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'>In this scenario the system
initially creates the end-user’s FOAF file.<span
style='mso-spacerun:yes'> </span>Its master is maintained within our
centralized database until the end-user chooses to ‘Opt-out’.<span
style='mso-spacerun:yes'> </span>At that point – the FOAF file is transferred
to the end-user’s designating ftp location – and a mirroring
relationship is set up.<span style='mso-spacerun:yes'> </span>Any changes
made to the end-user’s FOAF file – gets sent to our system.<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:4.5pt'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<ol style='mso-margin-top-alt:0in' start=3 type=1>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;tab-stops:list .5in'><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'>Manual<o:p></o:p></span></font></li>
</ol>
<p class=MsoNormal style='margin-left:.25in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>The tried and true manual method has the end-user with two
separate FOAF files.<span style='mso-spacerun:yes'> </span>The internal
version of the FOAF file – within the social network of <span
class=SpellE>FOAFster</span> – keeps in sync with the social
network.<span style='mso-spacerun:yes'> </span>An external FOAF end-user can
grab – at any time – a copy of their internal file – and choose
to do what they wish with it.<span style='mso-spacerun:yes'> </span>Most
likely they’d use it to bridge or gateway their external ‘experiments’,
developments, innovative new ideas and features, etc. – into this stand
alone <span class=SpellE>FOAFster</span> community.<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.25in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Since everyone is using FOAF – these new developments
can be very easily encompassed into the social network.<o:p></o:p></span></font></p>
<div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'>
<p class=MsoNormal style='border:none;mso-border-bottom-alt:double windowtext 2.25pt;
padding:0in;mso-padding-alt:0in 0in 1.0pt 0in'><font size=2 face=Arial><span
style='font-size:10.0pt;font-family:Arial'><o:p> </o:p></span></font></p>
</div>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>So now the question comes up – how’s it going on
defining and setting up a<span style='mso-spacerun:yes'> </span>system to
maintain the ‘master’ version of FOAF – so as new extensions
come into being – we all know where to reference that spec?<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>- Marc Canter<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>415-296-9401<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
</div>
</body>
</html>