xfn-to-foaf - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:35:25Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:35, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~XFN → FOAF~~</entry-title>~~		{{DISPLAYTITLE:XFN → FOAF}}
	{{TOC-right}}		{{TOC-right}}
	by [[User:TobyInk\|Toby Inkster]]		by [[User:TobyInk\|Toby Inkster]]

TobyInk: /* Possible RDF Output */ slight changes

2008-12-05T00:12:14Z

Possible RDF Output: slight changes

← Older revision		Revision as of 00:12, 5 December 2008
Line 133:		Line 133:
	<pre><nowiki>		<pre><nowiki>
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<rdf:RDF xmlns="http://xmlns.com/foaf/0.1/"		<rdf:RDF xmlns:foaf="http://xmlns.com/foaf/0.1/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"		xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:xfn="http://vocab.sindice.com/xfn#"		xmlns:xfn="http://vocab.sindice.com/xfn#"
	xmlns~~:hcard~~="~~urn:ietf:rfc~~:~~2426~~#">		xmlns="http://www.w3.org/2006/vcard/ns#">

	<!-- Alice -->		<!-- Alice -->
	<~~Person~~ rdf:nodeID="bnode01">		<VCard rdf:nodeID="bnode01">

	<!-- data from Alice's hCard -->		<!-- data from Alice's hCard -->
	<~~hcard:~~fn>Alice Jones</~~hcard:~~fn>		<fn>Alice Jones</fn>
	<~~hcard~~:~~adr~~>		<adr rdf:parseType="Resource">
	<~~hcard:~~locality>Sydney</~~hcard:~~locality>		<locality>Sydney</locality>
	<~~hcard:~~country-name>Australia</~~hcard:~~country-name>		<country-name>Australia</country-name>
	</~~hcard:~~adr>		</adr>
	<~~hcard:~~url rdf:resource="http://alice.example.com/blog/" />		<url rdf:resource="http://alice.example.com/blog/" />

	<!-- data from Alice's XFN links -->		<!-- data from Alice's XFN links -->
	<page rdf:resource="http://alice.example.com/blog/" />		<foaf:page rdf:resource="http://alice.example.com/blog/" />
	<knows rdf:nodeID="bnode02" />		<foaf:knows rdf:nodeID="bnode02" />
	<xfn:met rdf:nodeID="bnode02" />		<xfn:met rdf:nodeID="bnode02" />
	<xfn:friend rdf:nodeID="bnode02" />		<xfn:friend rdf:nodeID="bnode02" />
	<knows rdf:nodeID="bnode03" />		<foaf:knows rdf:nodeID="bnode03" />
	<xfn:met rdf:nodeID="bnode03" />		<xfn:met rdf:nodeID="bnode03" />
	<xfn:co-worker rdf:nodeID="bnode03" />		<xfn:co-worker rdf:nodeID="bnode03" />
	<knows rdf:nodeID="bnode04" />		<foaf:knows rdf:nodeID="bnode04" />
	<xfn:met rdf:nodeID="bnode04" />		<xfn:met rdf:nodeID="bnode04" />
	<xfn:friend rdf:nodeID="bnode04" />		<xfn:friend rdf:nodeID="bnode04" />
	<xfn:neighbor rdf:nodeID="bnode04" />		<xfn:neighbor rdf:nodeID="bnode04" />
	<knows rdf:nodeID="bnode05" />		<foaf:knows rdf:nodeID="bnode05" />
	<xfn:met rdf:nodeID="bnode05" />		<xfn:met rdf:nodeID="bnode05" />

	</~~Person~~>		</VCard>

	<!-- Bob, data from hCard -->		<!-- Bob, data from hCard -->
	<~~Person~~ rdf:nodeID="bnode02">		<VCard rdf:nodeID="bnode02">
	<~~hcard:~~fn>Bob Smith</~~hcard:~~fn>		<fn>Bob Smith</fn>
	<~~hcard:~~url rdf:resource="http://bob.example.net" />		<url rdf:resource="http://bob.example.net" />
	</~~Person~~>		</VCard>

	<!-- Carol, implied data -->		<!-- Carol, implied data -->
	<Person rdf:nodeID="bnode03">		<foaf:Person rdf:nodeID="bnode03">
	<name>Carol Brown</name>		<foaf:name>Carol Brown</foaf:name>
	<page rdf:resource="http://carol.example.net" />		<foaf:page rdf:resource="http://carol.example.net" />
	</Person>		</foaf:Person>

	<!-- Dave, implied data -->		<!-- Dave, implied data -->
	<Person rdf:nodeID="bnode04">		<foaf:Person rdf:nodeID="bnode04">
	<name>Dave Wong</name>		<foaf:name>Dave Wong</foaf:name>
	<page rdf:resource="http://dave.example.net" />		<foaf:page rdf:resource="http://dave.example.net" />
	</Person>		</foaf:Person>

	<!-- Eve, data from hCard -->		<!-- Eve, data from hCard -->
	<~~Person~~ rdf:nodeID="bnode05">		<VCard rdf:nodeID="bnode05">
	<~~hcard:~~fn>Eve Ville</~~hcard:~~fn>		<fn>Eve Ville</fn>
	<~~hcard:~~url rdf:resource="http://eve.example.net" />		<url rdf:resource="http://eve.example.net" />
	<~~hcard:~~uid ~~rdf:resource="~~http://eve.example.net" />		<uid>http://eve.example.net"</uid>
	<~~hcard:~~email rdf:resource="mailto:eve@example.net" />		<email rdf:resource="mailto:eve@example.net" />
	</~~Person~~>		</VCard>

	</rdf:RDF>		</rdf:RDF>
	</nowiki></pre>		</nowiki></pre>

	Note that some personal data for contacts is expressed in the FOAF vocabulary, and some information is expressed in vCard/hCard vocabulary. User agents may use OWL or another technique to draw equivalencies between vocabularies, such as taking <code>~~hcard:~~fn</code> to be equivalent to <code>foaf:name</code>.		Note that some personal data for contacts is expressed in the FOAF vocabulary, and some information is expressed in vCard/hCard vocabulary. User agents may use OWL or another technique to draw equivalencies between vocabularies, such as taking <code>fn</code> to be equivalent to <code>foaf:name</code>.

	== Organisation hCards and XFN ==		== Organisation hCards and XFN ==

TobyInk: /* Determining the subject */ and again

2008-11-27T09:22:19Z

Determining the subject: and again

← Older revision		Revision as of 09:22, 27 November 2008
Line 23:		Line 23:
	#* (Parsers {{should}} impose a depth limit for crawling.)		#* (Parsers {{should}} impose a depth limit for crawling.)
	# If no hCard for the subject has been found, the subject is a person represented by the following RDF triples:		# If no hCard for the subject has been found, the subject is a person represented by the following RDF triples:
	<pre><nowiki>:bnode01 a foaf:Person;		<pre><nowiki>_:bnode01 a foaf:Person;
	foaf:page <http://alice.example.net>.</nowiki></pre>		foaf:page <http://alice.example.net>.</nowiki></pre>

TobyInk: /* Determining the object */ somehow the underscore had fallen off

2008-11-27T09:21:58Z

Determining the object: somehow the underscore had fallen off

← Older revision		Revision as of 09:21, 27 November 2008
Line 50:		Line 50:
	# If no hCard representing the object of the relationship has been found, then the object is taken to be a <code>foaf:Person</code> with a <code>foaf:name</code> corresponding to the link text and, depending on the kind of link provided in the <code>href</code> attribute, a <code>foaf:mbox</code> (for "mailto:" links), <code>foaf:mbox_sha1sum</code> (for "urn:sha1:" URLs), <code>foaf:img</code> (image links, determined by <code>type</code> attribute or HTTP headers, not by file name) or <code>foaf:page</code> (all other links). Our example would generate the following triples:		# If no hCard representing the object of the relationship has been found, then the object is taken to be a <code>foaf:Person</code> with a <code>foaf:name</code> corresponding to the link text and, depending on the kind of link provided in the <code>href</code> attribute, a <code>foaf:mbox</code> (for "mailto:" links), <code>foaf:mbox_sha1sum</code> (for "urn:sha1:" URLs), <code>foaf:img</code> (image links, determined by <code>type</code> attribute or HTTP headers, not by file name) or <code>foaf:page</code> (all other links). Our example would generate the following triples:

	<pre><nowiki>:bnode02 a foaf:Person;		<pre><nowiki>_:bnode02 a foaf:Person;
	foaf:page <http://bob.example.net>;		foaf:page <http://bob.example.net>;
	foaf:name "Bob Smith".</nowiki></pre>		foaf:name "Bob Smith".</nowiki></pre>

TobyInk: entities not allowed in it seems

2008-11-26T19:33:29Z

entities not allowed in <entry-title> it seems

← Older revision		Revision as of 19:33, 26 November 2008
Line 1:		Line 1:
	<entry-title>XFN ~~→~~ FOAF</entry-title>		<entry-title>XFN → FOAF</entry-title>
	{{TOC-right}}		{{TOC-right}}
	by [[User:TobyInk\|Toby Inkster]]		by [[User:TobyInk\|Toby Inkster]]

TobyInk: Minor updates, wiki-2-ification.

2008-11-26T19:31:35Z

Minor updates, wiki-2-ification.

← Older revision		Revision as of 19:31, 26 November 2008
Line 1:		Line 1:
	<h1>XFN → FOAF</h1>		<entry-title>XFN → FOAF</entry-title>
	{{TOC-right}}		{{TOC-right}}
	by [[User:TobyInk\|Toby Inkster]]		by [[User:TobyInk\|Toby Inkster]]

			(Contributors: Gabriele Renzi)

	<p> </p>		<p> </p>
Line 32:		Line 34:
	For <code>rel="me"</code> the predicate is <code>foaf:page</code>.		For <code>rel="me"</code> the predicate is <code>foaf:page</code>.

	For other relationships, the local name of the predicate is the same as the rel value, and the namespace URI is defined as <code><nowiki>http://~~gmpg~~.~~org~~/xfn~~/11~~#</nowiki></code>. Many non-me XFN values can be considered to be refinements of foaf:knows. As an example, the fully qualified URIs for the predicates associated with <code><nowiki>rel="met friend"</nowiki></code> are:		For other relationships, the local name of the predicate is the same as the rel value, and the namespace URI is defined as <code><nowiki>http://vocab.sindice.com/xfn#</nowiki></code>. Many non-me XFN values can be considered to be refinements of foaf:knows. As an example, the fully qualified URIs for the predicates associated with <code><nowiki>rel="met friend"</nowiki></code> are:

	* <code><nowiki>http://~~gmpg~~.~~org~~/xfn~~/11~~#met</nowiki></code>		* <code><nowiki>http://vocab.sindice.com/xfn#met</nowiki></code>
	* <code><nowiki>http://~~gmpg~~.~~org~~/xfn~~/11~~#friend</nowiki></code>		* <code><nowiki>http://vocab.sindice.com/xfn#friend</nowiki></code>
	* <code><nowiki>http://xmlns.com/foaf/0.1/knows</nowiki></code>		* <code><nowiki>http://xmlns.com/foaf/0.1/knows</nowiki></code>

Line 46:		Line 48:
	# In the high-bandwidth situation, parsers {{may}} follow the link target to look for a representative hCard for the object.		# In the high-bandwidth situation, parsers {{may}} follow the link target to look for a representative hCard for the object.
	#* (Parsers {{may}} then further follow rel="me" links from <nowiki>http://bob.example.net</nowiki> in order to find a "better" representative hCard for Bob.)		#* (Parsers {{may}} then further follow rel="me" links from <nowiki>http://bob.example.net</nowiki> in order to find a "better" representative hCard for Bob.)
	# If no hCard representing the object of the relationship has been found, then the object is taken to be a <code>foaf:Person</code> with a <code>foaf:name</code> corresponding to the link text and, depending on the kind of link provided in the <code>href</code> attribute, a <code>foaf:mbox</code> (for "mailto:" links), <code>foaf:mbox_sha1sum</code> (for "urn:sha1:" URLs), <code>foaf:img</code> (image links, determined by <code>type</code> attribute or HTTP headers, not by file name) or <code>foaf:page</code> (all other links). Our example would generate the following triples: <pre><nowiki>:bnode02 a foaf:Person;		# If no hCard representing the object of the relationship has been found, then the object is taken to be a <code>foaf:Person</code> with a <code>foaf:name</code> corresponding to the link text and, depending on the kind of link provided in the <code>href</code> attribute, a <code>foaf:mbox</code> (for "mailto:" links), <code>foaf:mbox_sha1sum</code> (for "urn:sha1:" URLs), <code>foaf:img</code> (image links, determined by <code>type</code> attribute or HTTP headers, not by file name) or <code>foaf:page</code> (all other links). Our example would generate the following triples:

			<pre><nowiki>:bnode02 a foaf:Person;
	foaf:page <http://bob.example.net>;		foaf:page <http://bob.example.net>;
	foaf:name "Bob Smith".</nowiki></pre>		foaf:name "Bob Smith".</nowiki></pre>
Line 52:		Line 56:
	A parser which understands RDFa or other semantics may use additional techniques to determine the object of the link, but those are beyond the scope of the Microformats wiki.		A parser which understands RDFa or other semantics may use additional techniques to determine the object of the link, but those are beyond the scope of the Microformats wiki.

	~~(TODO~~: ~~Add Gabriele Renzi~~'s ~~suggestion here~~.)		'''Is the link text really a person's name?''' sometimes it will be, sometimes it won't. If the link is part of an hCard which has used <code><nowiki><a class="fn url" ...></nowiki></code>, then it should be safe to suppose that it is a name, but at other times this is more of a risk. Often the link text will be a nickname. This is OK, as the definition of the <code>foaf:name</code> term is sufficiently broad to cover these cases. In other cases, it might not be a name at all. Depending on your application's needs, you may want to consider using <code>rdfs:label</code> instead of <code>foaf:name</code> or simply ignoring the link text completely.

	== Example ==		== Example ==
Line 131:		Line 135:
	<rdf:RDF xmlns="http://xmlns.com/foaf/0.1/"		<rdf:RDF xmlns="http://xmlns.com/foaf/0.1/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"		xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:xfn="http://~~gmpg~~.~~org~~/xfn~~/11~~#"		xmlns:xfn="http://vocab.sindice.com/xfn#"
	xmlns:hcard="urn:ietf:rfc:2426#">		xmlns:hcard="urn:ietf:rfc:2426#">

Line 238:		Line 242:
	=== Other ===		=== Other ===

	* [http://xen.adactio.com/ XHTML Enemies Network] - spoof of XFN. Can be easily implemented using the same algorithm. ~~Use namespace <code>~~http://~~xen~~.~~adactio~~.~~com~~/#</~~code>.~~		* [http://xen.adactio.com/ XHTML Enemies Network] - spoof of XFN. Can be easily implemented using the same algorithm.
			** [http://buzzword.org.uk/rdf/xen XHTML Enemies Network in RDF]
	* [[xpn\|XHTML Professionals Network]] - proposed extension to XFN to deal with corporate relationships. When/if completed, will probably be implementable using the algorithm on this page.		* [[xpn\|XHTML Professionals Network]] - proposed extension to XFN to deal with corporate relationships. When/if completed, will probably be implementable using the algorithm on this page.

TobyInk: /* Related Pages */ Add Richard Cyganiak's guide

2008-09-09T15:34:22Z

Related Pages: Add Richard Cyganiak's guide

← Older revision		Revision as of 15:34, 9 September 2008
Line 216:		Line 216:
	== Inspiration, References ==		== Inspiration, References ==

	* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011760.html Re: XFN is getting smoked by FOAF] - Toby Inkster, 2008-03-11		* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011760.html Re: XFN is getting smoked by FOAF] — Toby Inkster, 2008-03-11
	* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011772.html Re: XFN + hCard] - Toby Inkster, 2008-03-12		* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011772.html Re: XFN + hCard] — Toby Inkster, 2008-03-12
	* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011799.html Re: A (big) problem with XFN: identity of source and target not findable] - Toby Inkster, 2008-03-18		* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011799.html Re: A (big) problem with XFN: identity of source and target not findable] — Toby Inkster, 2008-03-18
	* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011800.html Re: A (big) problem with XFN: identity of source and target not findable] - David Janes, 2008-03-18		* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011800.html Re: A (big) problem with XFN: identity of source and target not findable] — David Janes, 2008-03-18
	* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011806.html Re: A (big) problem with XFN: identity of source andtarget not findable] - Toby Inkster, 2008-03-18		* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011806.html Re: A (big) problem with XFN: identity of source andtarget not findable] — Toby Inkster, 2008-03-18
	* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011851.html Re: A (big) problem with XFN: identity of source andtarget not findable] - Roger L Costello, 2008-03-20		* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011851.html Re: A (big) problem with XFN: identity of source andtarget not findable] — Roger L Costello, 2008-03-20
	* [http://microformats.org/discuss/mail/microformats-discuss/2008-April/012010.html Re: Coding mbox_sha1sum in XFN] - Toby Inkster, 2008-04-26		* [http://microformats.org/discuss/mail/microformats-discuss/2008-April/012010.html Re: Coding mbox_sha1sum in XFN] — Toby Inkster, 2008-04-26

	== Related Pages ==		== Related Pages ==

			* [http://vocab.sindice.com/xfn/guide.html Sindice: Expressing the XFN microformat in RDF] (largely compatible with this page) — Richard Cyganiak, 2008-06-27

	=== XFN ===		=== XFN ===

TobyInk: Updates reflecting experience parsing XFN in the wild.

2008-09-09T13:10:13Z

Updates reflecting experience parsing XFN in the wild.

← Older revision		Revision as of 13:10, 9 September 2008
Line 21:		Line 21:
	#* (Parsers {{should}} impose a depth limit for crawling.)		#* (Parsers {{should}} impose a depth limit for crawling.)
	# If no hCard for the subject has been found, the subject is a person represented by the following RDF triples:		# If no hCard for the subject has been found, the subject is a person represented by the following RDF triples:
	<pre><nowiki>~~<#x>~~ a foaf:Person;		<pre><nowiki>:bnode01 a foaf:Person;
	foaf:page <http://alice.example.net>.</nowiki></pre>		foaf:page <http://alice.example.net>.</nowiki></pre>

	A parser which understands RDFa or other semantics may use additional techniques to determine the subject of the link, but those are beyond the scope of the Microformats wiki.		A parser which understands RDFa or other semantics may use additional techniques to determine the subject of the link, but those are beyond the scope of the Microformats wiki.
Line 43:		Line 43:

	# If the link element is a descendant of an element with <code>class="vcard"</code> which is not the representative hCard for the page, then this hCard is taken to represent the person who is the object of the relationship.		# If the link element is a descendant of an element with <code>class="vcard"</code> which is not the representative hCard for the page, then this hCard is taken to represent the person who is the object of the relationship.
	# If a non-representative hCard exists on the page with a UID property which is identical to the target of the link element, then this hCard is taken to represent the object of the relationship.		<!-- # If a non-representative hCard exists on the page with a UID property which is identical to the target of the link element, then this hCard is taken to represent the object of the relationship. -->
	# In the high-bandwidth situation, parsers {{may}} follow the link target to look for a representative hCard for the object.		# In the high-bandwidth situation, parsers {{may}} follow the link target to look for a representative hCard for the object.
	#* (Parsers {{may}} then further follow rel="me" links from <nowiki>http://bob.example.net</nowiki> in order to find a "better" representative hCard for Bob.)		#* (Parsers {{may}} then further follow rel="me" links from <nowiki>http://bob.example.net</nowiki> in order to find a "better" representative hCard for Bob.)
	# If no hCard representing the object of the relationship has been found, then the object is taken to be a <code>foaf:Person</code> with a <code>foaf:name</code> corresponding to the link text and, depending on the kind of link provided in the <code>href</code> attribute, a <code>foaf:mbox</code> (for "mailto:" links), <code>foaf:mbox_sha1sum</code> (for "urn:sha1:" URLs), <code>foaf:img</code> (image links, determined by <code>type</code> attribute or HTTP headers, not by file name) or <code>foaf:page</code> (all other links). Our example would generate the following triples: <pre><nowiki>~~<#y>~~ a foaf:Person;		# If no hCard representing the object of the relationship has been found, then the object is taken to be a <code>foaf:Person</code> with a <code>foaf:name</code> corresponding to the link text and, depending on the kind of link provided in the <code>href</code> attribute, a <code>foaf:mbox</code> (for "mailto:" links), <code>foaf:mbox_sha1sum</code> (for "urn:sha1:" URLs), <code>foaf:img</code> (image links, determined by <code>type</code> attribute or HTTP headers, not by file name) or <code>foaf:page</code> (all other links). Our example would generate the following triples: <pre><nowiki>:bnode02 a foaf:Person;
	foaf:page <http://bob.example.net>;		foaf:page <http://bob.example.net>;
	foaf:name "Bob Smith".</nowiki></pre>		foaf:name "Bob Smith".</nowiki></pre>

	A parser which understands RDFa or other semantics may use additional techniques to determine the object of the link, but those are beyond the scope of the Microformats wiki.		A parser which understands RDFa or other semantics may use additional techniques to determine the object of the link, but those are beyond the scope of the Microformats wiki.
Line 135:		Line 135:

	<!-- Alice -->		<!-- Alice -->
	<Person rdf:~~about~~="~~http://alice.example.net~~">		<Person rdf:nodeID="bnode01">

	<!-- data from Alice's hCard -->		<!-- data from Alice's hCard -->
Line 147:		Line 147:
	<!-- data from Alice's XFN links -->		<!-- data from Alice's XFN links -->
	<page rdf:resource="http://alice.example.com/blog/" />		<page rdf:resource="http://alice.example.com/blog/" />
	<knows rdf:~~resource~~="~~#Bob~~" />		<knows rdf:nodeID="bnode02" />
	<xfn:met rdf:~~resource~~="~~#Bob~~" />		<xfn:met rdf:nodeID="bnode02" />
	<xfn:friend rdf:~~resource~~="~~#Bob~~" />		<xfn:friend rdf:nodeID="bnode02" />
	<knows rdf:~~resource~~="~~#Carol~~" />		<knows rdf:nodeID="bnode03" />
	<xfn:met rdf:~~resource~~="~~#Carol~~" />		<xfn:met rdf:nodeID="bnode03" />
	<xfn:co-worker rdf:~~resource~~="~~#Carol~~" />		<xfn:co-worker rdf:nodeID="bnode03" />
	<knows rdf:~~resource~~="~~#Dave~~" />		<knows rdf:nodeID="bnode04" />
	<xfn:met rdf:~~resource~~="~~#Dave~~" />		<xfn:met rdf:nodeID="bnode04" />
	<xfn:friend rdf:~~resource~~="~~#Dave~~" />		<xfn:friend rdf:nodeID="bnode04" />
	<xfn:neighbor rdf:~~resource~~="~~#Dave~~" />		<xfn:neighbor rdf:nodeID="bnode04" />
	<knows rdf:~~resource~~="~~http://eve.example.net~~" />		<knows rdf:nodeID="bnode05" />
	<xfn:met rdf:~~resource~~="~~http://eve.example.net~~" />		<xfn:met rdf:nodeID="bnode05" />

	</Person>		</Person>

	<!-- Bob, data from hCard -->		<!-- Bob, data from hCard -->
	<Person rdf:ID="~~Bob~~">		<Person rdf:nodeID="bnode02">
	<hcard:fn>Bob Smith</hcard:fn>		<hcard:fn>Bob Smith</hcard:fn>
	<hcard:url rdf:resource="http://bob.example.net" />		<hcard:url rdf:resource="http://bob.example.net" />
Line 169:		Line 169:

	<!-- Carol, implied data -->		<!-- Carol, implied data -->
	<Person rdf:ID="~~Carol~~">		<Person rdf:nodeID="bnode03">
	<name>Carol Brown</name>		<name>Carol Brown</name>
	<page rdf:resource="http://carol.example.net" />		<page rdf:resource="http://carol.example.net" />
Line 175:		Line 175:

	<!-- Dave, implied data -->		<!-- Dave, implied data -->
	<Person rdf:ID="~~Dave~~">		<Person rdf:nodeID="bnode04">
	<name>Dave Wong</name>		<name>Dave Wong</name>
	<page rdf:resource="http://dave.example.net" />		<page rdf:resource="http://dave.example.net" />
Line 181:		Line 181:

	<!-- Eve, data from hCard -->		<!-- Eve, data from hCard -->
	<Person rdf:~~about~~="~~http://eve.example.net~~">		<Person rdf:nodeID="bnode05">
	<hcard:fn>Eve Ville</hcard:fn>		<hcard:fn>Eve Ville</hcard:fn>
	<hcard:url rdf:resource="http://eve.example.net" />		<hcard:url rdf:resource="http://eve.example.net" />

TobyInk: /* Related Pages */ note about xen and xpn

2008-07-25T09:29:10Z

Related Pages: note about xen and xpn

← Older revision		Revision as of 09:29, 25 July 2008
Line 233:		Line 233:

	{{uf-rdf-related-pages}}		{{uf-rdf-related-pages}}

			=== Other ===

			* [http://xen.adactio.com/ XHTML Enemies Network] - spoof of XFN. Can be easily implemented using the same algorithm. Use namespace <code>http://xen.adactio.com/#</code>.
			* [[xpn\|XHTML Professionals Network]] - proposed extension to XFN to deal with corporate relationships. When/if completed, will probably be implementable using the algorithm on this page.

TobyInk: /* Determining the predicate */ XFN vs foaf:knows.

2008-07-25T09:11:56Z

Determining the predicate: XFN vs foaf:knows.

← Older revision		Revision as of 09:11, 25 July 2008
Line 32:		Line 32:
	For <code>rel="me"</code> the predicate is <code>foaf:page</code>.		For <code>rel="me"</code> the predicate is <code>foaf:page</code>.

	For other relationships, the local name of the predicate is the same as the rel value, and the namespace URI is defined as <code><nowiki>http://gmpg.org/xfn/11#</nowiki></code>. ~~All~~ non-me XFN values ~~are~~ considered to be refinements of foaf:knows. As an example the fully qualified URIs for the predicates associated with <code><nowiki>rel="met friend"</nowiki></code> are:		For other relationships, the local name of the predicate is the same as the rel value, and the namespace URI is defined as <code><nowiki>http://gmpg.org/xfn/11#</nowiki></code>. Many non-me XFN values can be considered to be refinements of foaf:knows. As an example, the fully qualified URIs for the predicates associated with <code><nowiki>rel="met friend"</nowiki></code> are:

	* <code><nowiki>http://gmpg.org/xfn/11#met</nowiki></code>		* <code><nowiki>http://gmpg.org/xfn/11#met</nowiki></code>
	* <code><nowiki>http://gmpg.org/xfn/11#friend</nowiki></code>		* <code><nowiki>http://gmpg.org/xfn/11#friend</nowiki></code>
	* <code><nowiki>http://xmlns.com/foaf/0.1/knows</nowiki></code>		* <code><nowiki>http://xmlns.com/foaf/0.1/knows</nowiki></code>

			'''Which XFN values are refinements of <code>foaf:knows</code>?''' This is a matter of debate. Although normally, say, a parent and child will have a close relationship, there are instances where they may have never met, and not know each other at all. The current list of XFN values which I treat as refinements of <code>foaf:knows</code> are: acquaintance, friend, met, co-resident, spouse, crush, date and sweetheart. Depending upon your application, you may wish to narrow or broaden your scope.

	== Determining the object ==		== Determining the object ==