charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d">
<BLOCKQUOTE>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT face=3DT=
ahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Jim Ley=20
[mailto:jim@j...]<BR><B>Sent:</B> October 6, 2002 10:30=20
AM<BR><B>To:</B> rdfweb-dev@yahoogroups.com<BR><B>Subject:</B> Re:=20
[rdfweb-dev] FOAF, RDDL, and me<BR><BR></FONT></DIV><TT>"Doug Ransom"=20
<doug_ransom@t...><BR>> I would like to create a FOAF fil=
e for=20
myself. Should I give myself a<BR>URI,<BR>> place a RDDL docum=
ent=20
at that URI which provides links to a FOAF file<BR>(and<BR>> if so, =
what=20
are the nature and purpose).<BR><BR>Nah, no-one will use your URI, as=20
they'll never bother looking it up,<BR>they know your email address tho=
ugh,=20
yes you have a number, but that's<BR>okay, the semantic web will soon k=
now=20
the person with<BR>doug_ransom@t... and Doug.Ransom@p... are t=
he=20
same person (*)<BR>
<HR>
</BLOCKQUOTE>
<DIV><SPAN class=3D301023120-06102002><FONT face=3DArial color=3D#0000ff=
=20
size=3D2> Wouldn't it make sense that an email address we=
re the=20
property of a person, instead of being that person? An email addres=
s is=20
basically the URI of a postbox, something I own or lease.</FONT></SPAN></=
DIV>
<DIV><SPAN class=3D301023120-06102002></SPAN> </DIV>
<DIV><SPAN class=3D301023120-06102002></SPAN><SPAN=20
class=3D301023120-06102002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"><FONT face=3DArial colo=
r=3D#0000ff=20
size=3D2></FONT><FONT face=3DArial color=3D#0000ff size=3D2></FONT>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT face=3DAr=
ial=20
color=3D#0000ff size=3D2></FONT><BR>> I am not too deep into RDF and=
don't=20
plan to get too deep. Would<BR>friends<BR>> reference me with =
a URI=20
to my rddl page, to my foaf page, or just with<BR>an<BR>> email addr=
ess=20
(of which I have a fiew).<BR><BR>They'll just say, there's a person, th=
e=20
person has your email address (or<BR>just the sha1sum of it) the=
=20
agents know that email address are<BR>unambigous (I know e-mail address=
es=20
aren't, but you're only "allowed" to<BR>use one that is) so it knows th=
at=20
two foaf:Person's with the same<BR>foaf:mbox are the same=20
person.<BR><BR>> Is anyone embedding their FOAF into their XHTML hom=
e=20
page (and would<BR>that<BR>> perhaps be a better practice)?<BR><BR>u=
ntil=20
browsers actually start supporting XHTML, I can't see any point, no<BR>=
user=20
would ever know about the RDF info, as none would be getting the<BR>XHT=
ML=20
document (we can't embed RDF into a document sent as text/html, as<BR>i=
t=20
would not be a valid document for that mime-type, well if you embedded<=
BR>it=20
in any useful way.) using LINK to it, or as a simple <a href as=20
many<BR>people do from their blogs, seems a sensible approach.<BR><BR>I=
=20
don't really see resource discovery too much of a problem, if we can<BR=
>link=20
everyone to everyone in 6 degrees, foaf:knows rdfs:seeAlso is=20
likely<BR>enough.<BR><BR>(*) If you are indeed, I have no idea of cours=
e, I=20
just looked at google.<BR><BR></TT><BR></DIV></BLOCKQUOTE><BR><TT>To=20
unsubscribe from this group, send an email=20
to:<BR>rdfweb-dev-unsubscribe@egroups.com<BR><BR></TT><BR><BR><TT>Your us=
e of=20
Yahoo! Groups is subject to the <A=20
href=3D"http://docs.yahoo.com/info/terms/">Yahoo! Terms of Service</A>.</=
TT>=20
<BR></BLOCKQUOTE></BODY></HTML>