[foaf-dev] Re: updated FOAF spec

Dan Brickley danbri at danbri.org
Fri May 25 10:37:10 BST 2007

ps. here's a handy query that can be run direct on Dave Beckett's online 
SPARQL service. It lists properties and their status.

PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX vs: <http://www.w3.org/2003/06/sw-vocab-status/ns#>
SELECT DISTINCT ?status ?x ?label
  ?x a rdf:Property .
  ?x rdfs:label ?label .
  ?x vs:term_status ?status .
ORDER BY ?status

(a similar query can be run for rdfs:Class, I tried combining the two 
with UNION but either I don't understand, or the engine doesn't support 
enough SPARQL, to make that work).

I'm copying the results here as its a handy overview, probably should do 
something similar in the FOAF spec itself. A direct if lengthy link to 
this online is
...alternatively, enter the above query, plus
http://xmlns.com/foaf/0.1/index.rdf as RDF content URI, into the form at

I should also mention that SKOS has some definitions for 
stable/unstable/testing, see the section in
http://www.w3.org/TR/swbp-skos-core-spec/#secChange and which look like 
a good basis for inclusion in the FOAF spec.

     The term is unstable, and feedback is welcomed on its current form 
and utility. It may currently be poorly defined. Its meaning and/or form 
may be expected to change at any time. Do not implement mission critical 
systems that depend on this term persisting in its current form. 
(Changes corresponding to DCMI Namespace Policy types A, B or C may occur.)

     The term has gone beyond the raw proposal stage, and is undergoing 
testing. This term may still change in response to feedback from 
testing, although it may be expected not to undergo any radical change. 
The cost to early implementors of changing the term will be considered, 
however the goal of achieving wider interoperability and long-term 
stability may override those considerations. (Changes corresponding to 
DCMI Namespace Policy types A or B may occur.)

     No substantial (i.e. meaning-changing) alterations will take place. 
Implementors can expect the term to persist in its current form 
indefinitely. (Minor editorial changes corresponding to DCMI Namespace 
Policy type A may occur.)

Query results in txt format copied below for info. This list might be a 
handy way for people here to express a preference for which term 
statuses might best be changed next.

BTW since SKOS uses the same vocab status markup, you can run a similar 
query against the SKOS RDF here:



1 	stable	member	http://xmlns.com/foaf/0.1/member
2 	stable	maker	http://xmlns.com/foaf/0.1/maker
3 	stable	made	http://xmlns.com/foaf/0.1/made
4 	stable	homepage	http://xmlns.com/foaf/0.1/homepage
5 	stable	personal mailbox	http://xmlns.com/foaf/0.1/mbox
6 	testing	page	http://xmlns.com/foaf/0.1/page
7 	testing	is primary topic of	http://xmlns.com/foaf/0.1/isPrimaryTopicOf
8 	testing	primary topic	http://xmlns.com/foaf/0.1/primaryTopic
9 	testing	topic	http://xmlns.com/foaf/0.1/topic
10 	testing	logo	http://xmlns.com/foaf/0.1/logo
11 	testing	past project	http://xmlns.com/foaf/0.1/pastProject
12 	testing	current project	http://xmlns.com/foaf/0.1/currentProject
13 	testing	interest_topic	http://xmlns.com/foaf/0.1/topic_interest
14 	testing	interest	http://xmlns.com/foaf/0.1/interest
15 	testing	knows	http://xmlns.com/foaf/0.1/knows
16 	testing	schoolHomepage	http://xmlns.com/foaf/0.1/schoolHomepage
17 	testing	work info homepage	http://xmlns.com/foaf/0.1/workInfoHomepage
18 	testing	workplace homepage	http://xmlns.com/foaf/0.1/workplaceHomepage
19 	testing	myersBriggs	http://xmlns.com/foaf/0.1/myersBriggs
20 	testing	thumbnail	http://xmlns.com/foaf/0.1/thumbnail
21 	testing	depicts	http://xmlns.com/foaf/0.1/depicts
22 	testing	depiction	http://xmlns.com/foaf/0.1/depiction
23 	testing	image	http://xmlns.com/foaf/0.1/img
24 	testing	plan	http://xmlns.com/foaf/0.1/plan
25 	testing	tipjar	http://xmlns.com/foaf/0.1/tipjar
26 	testing	weblog	http://xmlns.com/foaf/0.1/weblog
27 	testing	phone	http://xmlns.com/foaf/0.1/phone
28 	testing	family_name	http://xmlns.com/foaf/0.1/family_name
29 	testing	Surname	http://xmlns.com/foaf/0.1/surname
30 	testing	Given name	http://xmlns.com/foaf/0.1/givenname
31 	testing	firstName	http://xmlns.com/foaf/0.1/firstName
32 	testing	name	http://xmlns.com/foaf/0.1/name
33 	testing	MSN chat ID	http://xmlns.com/foaf/0.1/msnChatID
34 	testing	Yahoo chat ID	http://xmlns.com/foaf/0.1/yahooChatID
35 	testing	ICQ chat ID	http://xmlns.com/foaf/0.1/icqChatID
36 	testing	AIM chat ID	http://xmlns.com/foaf/0.1/aimChatID
37 	testing	jabber ID	http://xmlns.com/foaf/0.1/jabberID
38 	testing	nickname	http://xmlns.com/foaf/0.1/nick
39 	testing	title	http://xmlns.com/foaf/0.1/title
40 	testing	geekcode	http://xmlns.com/foaf/0.1/geekcode
41 	testing	gender	http://xmlns.com/foaf/0.1/gender
42 	testing	sha1sum of a personal mailbox URI name
43 	unstable	birthday	http://xmlns.com/foaf/0.1/birthday
44 	unstable	membershipClass	http://xmlns.com/foaf/0.1/membershipClass
45 	unstable	account name	http://xmlns.com/foaf/0.1/accountName
46 	unstable	account service homepage
47 	unstable	holds account	http://xmlns.com/foaf/0.1/holdsAccount
48 	unstable	theme	http://xmlns.com/foaf/0.1/theme
49 	unstable	funded by	http://xmlns.com/foaf/0.1/fundedBy
50 	unstable	publications	http://xmlns.com/foaf/0.1/publications
51 	unstable	based near	http://xmlns.com/foaf/0.1/based_near
52 	unstable	sha1sum (hex)	http://xmlns.com/foaf/0.1/sha1
53 	unstable	DNA checksum	http://xmlns.com/foaf/0.1/dnaChecksum

More information about the foaf-dev mailing list