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><SPAN class=3D085354713-22102002><FONT face=3DArial color=3D#0000ff si=
ze=3D2>I=20
guess the issue is that the person might change email addresses. But =
I=20
suppose a once-owned-address property might work if they ever generat=
e a=20
foaf (I doubt they ever will anyway).</FONT></SPAN></DIV>
<DIV><SPAN class=3D085354713-22102002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D085354713-22102002></SPAN> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT face=3DTah=
oma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Jim Ley=20
[mailto:jim@j...]<BR><B>Sent:</B> October 22, 2002 6:44=20
AM<BR><B>To:</B> rdfweb-dev@yahoogroups.com<BR><B>Cc:</B>=20
Jim@j...<BR><B>Subject:</B> Re: [rdfweb-dev] FOAF Use=20
Case<BR><BR></FONT></DIV><TT>"Doug" <doug_ransom@t...><BR>>=
I am=20
currently using rdfpic to put descriptions of photographs into<BR>> th=
ose=20
photos for a ski trip of last year. It would be nice if there<BR>&g=
t;=20
were a URI scheme to identify the members (none of whome have a foaf<BR>&=
gt;=20
file). I will eventually mine this data to produce a set of web<BR>=
>=20
pages and and RDF index which I hope will survive for 50 years (lets<BR>&=
gt;=20
see how long xhtml 1 is supported by browsers).<BR><BR>I assume you're us=
ing=20
an old version of RDFPic as the current version<BR>lets you describe the=
=20
people in the file in RDF aswell as just the<BR>descriptions.<BR><BR>Also=
,=20
tools exist to do stuff with this information, converting it into<BR>SVG=
=20
mostly...<BR><BR>I don't use RDFPic, but my tool (<BR><A=20
href=3D"http://jibbering.com/svg/AnnotateImage.html">http://jibbering.com=
/svg/AnnotateImage.html</A>=20
) produces similar RDF (yes<BR>we interoperate...) and then I have variou=
s=20
tools which take this RDF and<BR>produce various outputs, others not ment=
ioned=20
that page are<BR><A=20
href=3D"http://jibbering.com/2002/8/img-desc.svg">http://jibbering.com/20=
02/8/img-desc.svg</A>=20
(or the talking version<BR><A=20
href=3D"http://jibbering.com/2002/9/talking.html">http://jibbering.com/20=
02/9/talking.html</A> =20
) and<BR><A=20
href=3D"http://jibbering.com/rdf/codepiction.1">http://jibbering.com/rdf/=
codepiction.1</A> =20
all using the base RDF.<BR><BR>To identify the people you can just not gi=
ve=20
them an email address, and<BR>there's no problem (well it would be useful=
if=20
you could as otherwise we<BR>can't know that the person in one picture is=
the=20
same as the person in<BR>another)=20
e.g.<BR><BR><foaf:Person><BR><foaf:nick>freddie the=20
frog</foaf:nick><BR><foaf:name>Fred=20
Bloggs</foaf:name><BR></foaf:Person><BR><BR>You don't need an=
=20
actual URI for the person.<BR><BR>Jim.<BR><BR><BR><BR><BR><BR></TT><BR><B=
R><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>