This is the main public IssueTracker for FOAF open issues. It should be consulted by the spec editor (DanBri) when revising the FOAF specification. The list (and substantive FOAF updates) was largely on-hold 2006-2008 despite a few updates/additions (eg. foaf:openid). Future editions of the FOAF specification will be more closely cross-referenced to this list; it remains a good place to record issues.
Note that the list archives for pre-2007 discussion are for rdfweb-dev. The main FOAF list is now foaf-dev. While foaf-dev's archive includes historical rdfweb-dev posts, they are numbered differently. These issues often point to the older static archive of rdfweb-dev.
Nearby: Dublin Core Agents Wiki, where the relationship between DC and FOAF can be worked out.
Status: As of 2009-01-12, all non-closed issues are listed together as 'unsorted'. Some of them are probably closed or no longer relevant. Candidate issues and ill-formed thoughts are recorded lower in the page. Please help sort these by editing their pages, modernising Wiki syntax, and sending mail to foaf-dev with proposed resolutions! Thanks! -- DanBri
Issues for Review
|FOAF and Contact Ontology Issue||2010-05-17||Bob Ferris, zazi at elbklang.net||How to connect FOAF to the Contact Ontology?||foaf mailing list||proposal created|
|foaf:Image + foaf:img Issue||2010-05-17||Bob Ferris, zazi at elbklang.net||foaf:Image subclassOf foaf:Document or not? + Domain of foaf:img = foaf:Agent?||foaf mailing list||issue noticed|
|FOAF and Information Services||2010-05-17||Bob Ferris, zazi at elbklang.net||Modelling of link to information services||foaf mailing list||issue outsourced to the Info Service Ontology|
|Connect FOAF And VCard Issue||2010-05-17||Josef Petrák me at jspetrak.name, Bob Ferris zazi at elbklang.net||A new Property called foaf:businessCard to link a business card, e.g. of rdf:type vcard:VCard, to a FOAF profile.||foaf mailing list||proposal created|
|DeprecateFundedByAndThemeIssue||2009-12-12||Libby Miller libby at nicecupoftea.org||These properties are marked, respectively: 'This property is under-specified, experimental, and should be considered liable to change.' and 'The foaf:theme property is rarely used and under-specified'||foaf mailing list||fixed in 2009-12-15|
|LowHangingAligmentIssue||2009-12-01||Melvin Carvalho melvincarvalho at gmail.com||givenname -> givenName, family_name -> familyName, And as a maybe, title -> honorificPrefix||foaf mailing list||fixed in 2009-12-15|
|SpecVersionWrongIssue||2009-11-24||Antoine Zimmermann antoine.zimmermann at gmail.com||the specfication at  says that "this version" is http://xmlns.com/foaf/spec/20071002.html, which turns out to be different than the current version||foaf mailing list||fixed in 2009-12-15|
|FoafAgentDCTAgentIssue||2009-11-24||Antoine Zimmermann antoine.zimmermann at gmail.com||foaf:Person is now asserted to be equivalent to dcterm:Agent. This is very weird since Agent is described as "[a] resource that acts or has the power to act" and dcterm says "examples of Agent include person, organization, and software agent".||foaf mailing list||fixed in 2009-12-15|
|DisjointPersonOrgIssue||2009-11-24||Antoine Zimmermann antoine.zimmermann at gmail.com||the "foaf:Person owl:disjointWith foaf:Organization" axiom has been commented with the text "Oh no it isn't".||foaf mailing list||suggest fix next|
|MissingWordnetOntologyIssue||2009-11-24||Antoine Zimmermann antoine.zimmermann at gmail.com||all references to the wordnet ontology have been removed. What is the rationale behind this?||foaf mailing list||explained in 2009-12-15|
|RDFXMLRelicTextIssue||2009-01-20||Shepard||http://xmlns.com/foaf/spec/ says "All FOAF documents must be well-formed RDF/XML documents." - is that a relic that should be removed?||swig irc||fixed in 2009-12-15|
|FoafVcardPortablecontactsMappingIssue||2009-11-16||Melvin Carvalho melvincarvalho at gmail.com||Mappings foaf / vcard / portable contacts - google spreadsheet||foaf mailing list|
|FoafTopicInterestThingsIssue||2009-09-02||danbri||This actually echoes some discussion I've had with folk lately about foaf:interest and foaf:topic_interest, and whether the latter could reasonably be used to point to both things and SKOS concepts for those things. I was already leaning towards proposing a "yes" there, but if DCMI are doing it, then it is good company to be in :)||foaf mailing list|
|MissingFoafOpenIdPropertyIssue||2009-09-27||Richard Cyganiak richard at cyganiak.de||According to the spec, FOAF has a foaf:openid property: http://xmlns.com/foaf/spec/#term_openid But I can't find any trace of this property in the spec at http://xmlns.com/foaf/spec/index.rdf||foaf mailing list||fixed in 2009-12-15|
|MyersBriggsObjectPropertyErrorIssue||2009-09-27||Richard Cyganiak richard at cyganiak.de||The definition of foaf:myersBriggs, http://xmlns.com/foaf/0.1/myersBriggs The typing as an owl:ObjectProperty is surely an error? Also not the first time this was reported: http://lists.foaf-project.org/pipermail/foaf-dev/2007-November/008718.html Any chance of getting this fixed?||foaf mailing list||fixed in 2009-12-15|
|MigrateToFoafAccountIssue||2009-09-22||danbri||migrate from foaf:holdsAccount to foaf:account?||foaf mailing list||fixed in 2009-12-15|
|MissingFoafSpecProcessissue||2009-07-31||Sergey Chernyshev sergey.chernyshev at gmail.com||How do I get the spec changed?||foaf mailing list|
|MissingAccountProfilePage||2009-07-31||Sergey Chernyshev sergey.chernyshev at gmail.com||I was adding account editing functionality to MySemanticProfile and looking through a few FOAF files around, I found foaf:accountProfilePage indicating user's profile page (account's homepage if you will). I did implement it to provide support for it and you can see the module here: http://www.sergeychernyshev.com/my-semantic-profile/demo/admin/?module=accounts and RDF/XML here: http://www.sergeychernyshev.com/my-semantic-profile/demo/admin/?module=rdfxml But I'm obviously worried that it's not in the spec.||foaf mailing list|
|RDFXMLInSpecValidationIssue||2009-06-05||danbri||RDF/XML embedded in the spec means that it doesn't validate correctly||foaf mailing list||fixed in 2009-12-15|
|FoafPersonalPhoneIssue||2009-05-26||Kjetil Kjernsmo kjetil at kjernsmo.net||So, nowadays people run around with a mobile phone that is just theirs, thus the phone number for that phone is for all practical purposes an IFP. Thus, it would be nice to have it declared a such||foaf mailing list|
|StablizeFoafPhoneIssue||2009-05-26||Kjetil Kjernsmo kjetil at kjernsmo.net||foaf mailing list|
|FoafTopicDCSubjectIssue||2009-04-23||Danny Ayers danny.ayers at gmail.com||make foaf:topic
rdfs:subPropertyOf dcterms:subject ?
|foaf mailing list|
|FoafInterestMinorInconsistencyIssue||2009-02-03||Danny Ayers danny.ayers at gmail.com||The foaf:interest property represents an interest of a foaf:Agent, ... the last text line here suggests the domain is foaf:Agent, though the RDF version has foaf:Person||foaf mailing list||suggest fix next|
|FoafAccountAccessPageIssue||2009-02-03||Olivier GENDRIN olivier.gendrin at gmail.com||Looking at Danny RDF version of the semwab twitter pack , I think
that we may need a foaf:accountAccesspage in foaf:OnlineAccount, in order not to have to guess the account page URL just with foaf:accountServiceHomepage and foaf:accountName
|foaf mailing list|
|FoafMemberConfusingNamingIssue||2009-02-06||Juan Sequeda juanfederico at gmail.com||I am wondering why the property foaf:member has domain foaf:Group and range foaf:Agent. For me, it is obvious that it should be the other way around because an Agent is member of a Group.||foaf mailing list similar issue|
|BirthdayIssue||mortenf||What to do: A property or set of properties indicating age, birthday and/or birthdate of a person?|
|SpokenLanguages||thomas||Is there a property for languages a person speaks?. See speaks, reads, writes|
|PersonWeblogRssDocumentationIssue||mortenf||How-to: It's often useful to be able to connect people or their weblogs with RSS feeds.|
|OnlineAccountHomepageIssueemail@example.com||Add a new property to tie an account to its related homepage|
|OwnsIssuefirstname.lastname@example.org||to add or not to add foaf:owns rdfweb-dev email|
|SpecialPowerIssueemail@example.com||to add or not to add (maybe in kitchen sink namespace?)rdfweb-dev email|
|KitchenSinkNamespaceIssuefirstname.lastname@example.org||new namespace for less serious properties rdfweb-dev email|
|DocumentMetadataConventions||not assigned||Julian's suggestion to suggest good practice for document infor like last modified,created, etc rdfweb-dev email|
|WordnetIssueemail@example.com||Wordnet namespace RDF is wrong.|
|NameVocabIssuefirstname.lastname@example.org||firstname/surname/given/family underspecified, inconsistent...|
|HashSlashIssueemail@example.com||We lack confirmation that it is OK to deploy class and pr...|
|ChatVocabIssuefirstname.lastname@example.org||foaf:chat sub-properties could be better described|
|MemberVocabIssueemail@example.com||esigler's question about rdf syntax / foaf:member not having an inverse|
|XsltDocumentationIssuefirstname.lastname@example.org||documentation of xslt-conversion deployment technique (danc's homepage, xfn mapping etc)|
|SchemaTranslationIssueemail@example.com||would like to solicit translations of core documentation (classes/properties at least)|
|PreferredContactIssuefirstname.lastname@example.org||2004-01-12 proposal by Julian Bond: foaf:preferredContact, to Provide a public contact point where a person is happy to receive unsolicited messages from people who have found their FOAF. (email/phone/IM/etc)|
|KnowsAgentVocabIssueemail@example.com or firstname.lastname@example.org?||(jim) 2004-01-17 foaf:knows widened to encompass agents, or a superProperty instead.|
|ChatIdSubPropertiesIssueemail@example.com||foaf:chat sub-properties could be better described|
|TrustVocabIssuefirstname.lastname@example.org||PGP key vocabulary not documented or in schema 7 bugs found.|
|PgpVocabUndocumentedIssueemail@example.com||PGP key vocabulary not documented or in schema|
|SubscribesToForListsIssuefirstname.lastname@example.org||Would be good to express mailing list membership etc using the groups mechanism|
|MirrorServiceIssue||not assigned||How to say 'I mirror this' e.g. Jim's airports service rdfweb-dev email|
|LostPropertyIssue||not assigned||being able to tag a person as lost rdfweb-dev email|
|CurrentPastProjectConnectionsIssue||not assigned||"Further work is needed to specify the connections between this class [foaf:Project] and the FOAF properties foaf:currentProject and foaf:pastProject." see spec and rdfweb-dev email|
|VersionVocabIssue||not assigned||Version vocab addition for deprecation handling - Danny Ayers email to rdfweb-dev|
|NickTitleDomainRangeMissingIssue||not assigned||nick and title have no domain and range email to rdfweb-dev|
|SkypeIdIssue||not assigned||how to use sype ids with foaf Skype ID mail to rdfweb-dev form Julian Bond|
|CurrentPastProjectRangeIssue||not assigned||tighten up range of current and past project? mailtto rdfweb-dev|
|KnowsInverseIssue||not assigned||does knows need an inverse? Julian's mail to rdfweb-dev|
|SchematronSchemasIssues||not assigned||possible edits to the schematron profiles of foaf Julian's email to rdfweb-dev|
|CommentsOnPeopleIssue||not assigned||saying e.g. Dave is a GUI expert Kartik's mail to rdfweb-dev|
|OwlClassFoafSpecIssueemail@example.com||can we add owl:Class as well as rdfs:Class to the foaf spec? email from Benjamin Nowak to rdfweb-dev|
|UsingTapForIdentificationIssuefirstname.lastname@example.org||how can we use a TAP id to identify e.g. dead people or famous ones esp for codepiction email to rdfweb-dev|
|TelAsIfpIssue||not assigned||should phone be an inverse functional property? message from Jim Ley to rdfweb-dev|
|AuthoredCoauthoredIssue||not assigned||authored coauthored new properties? mail to rdfweb-dev from Earle Martin|
|MboxSha1SumCaseIssueemail@example.com||leadin zeros and upper/lowercase rdfweb-dev email|
|InverseOfThumbnailIssuefirstname.lastname@example.org||foaf:thumbnail doesn't have an inverse message from Morten Frederiksen|
|MissingClassesAndPropertiesIssueemail@example.com||Following present in human-readable spec but missing from the embedded RDF version: OnlineAccount, OnlineChatAccount, gender, OnlineEcommerceAccount, OnlineGamingAccount, member, PersonalProfileDocument, accountName, accountServiceHomepage, holdsAccount, membershipClass, primaryTopic, tipjar. rdfweb-dev email|
|CommentsIssuefirstname.lastname@example.org||Embedded RDF version of vocab in spec is rendered with <-- --> instead of rdfweb-dev email|
|OwlImportsIssue||not assigned||FOAF RDFS file imports the OWL and RDFS ontologies; this is not necessary and not recommended|
|GroupIssueemail@example.com||We need a consistent way of representing groups|
|MissingXmlBaseIssuefirstname.lastname@example.org||FOAF RDFS file contains owl:Ontology header whose URI does not match the file's URL, xml:base addition would correct this.|
|DocumentIssue||not assigned||foaf:Document is lacking a proper definition|
|OnlineAccountSubClassIssue||not assigned||Typo: in the schema, the various Online*Account classes are subclass of a wordnet:OnlineAccount rather than foaf:OnlineAccount Ian's summary of problem|
|PersonalProfileDocumentIssueemail@example.com||Should be added to spec? useful to identify that this is a particular person's foaf file email to rdfweb-dev - see term definition|
|PrimaryTopicIssuefirstname.lastname@example.org||"the notion of "the main topic" rather than "a topic" " rdfweb-dev email - see term definition|
|ImageIssueemail@example.com||foaf:Image is undocumented|
|ChatSubPropertyIssuefirstname.lastname@example.org||several subproperties of foaf:chat are misdeclared|
|IchatIdRedundantIssueemail@example.com||foaf:ichatID redundant since ichat uses AIM|
|MboxUnderconstrainedIssuefirstname.lastname@example.org||foaf:mbox is undersconstrained (no domain, range) This fix is not showing up in the RDF in spec. at  --SimonP|
|ImagePartsIssue||DanBri||depicts has domain Image so can't be used for parts of image Masahide's email to rdfweb-dev (resolved with new vocab)|
|SpatialThingIssue||not assigned||Person being a subclass of SpatialThing prevents usage with dead or fictitious people Dan's summary of the property IRC mention by IanDavis - SpatialThing includes abstract spaces such as cubes|
|HomepageDomainIssueemail@example.com(??)||things other than agents have homepages chumped summary for events, same issue for Pubs, inconsistency with foaf:Project --- RESOLVED with the Galway update to the spec, removing the domain specification|
Other issues that should be written up as BlahBlahIssue entries. If you write up an issue, please try to get danbri or libby to acknowledge it by email in rdfweb-dev, so we can track its status and resolution. If email doesn't get answered (sometimes life gets in the way...), IRC might be a good way of chasing up acknowledgement/status/closure.
Brief note of issue content, name in brackets is person who documented it here.
- swig IRC: Shepard tell danbri http://xmlns.com/foaf/spec/ says "All FOAF documents must be well-formed RDF/XML documents." - is that a relict that should be removed?
using IM uris (Ian Davis)
other identifying features of people (Stephen Pollei)
documenting foaf/vcard equivalence (Danny Ayers)
nice scutters (Edd Dumbill)
nice scutters (Julian Bond)
how best to describe the location of an image (Morten Frederiksen) -- note that the post refers to dc:spatial, should be dcterms:spatial.
seealsos issues (Libby Miller)
[18:42] phenny: danbri: 11 May 22:18Z <earle> tell danbri I notice you seem to be using "foaf:pubkeyAddress", did you mean "wot:pubkeyAddress"? [18:42] phenny: danbri: 11 May 22:27Z <earle> tell danbri also s/keyid/hex_id/ ? [18:42] phenny: danbri: 12 May 00:12Z <earle> tell danbri Actually, are you the maintainer for WOT? If so I have a suggestion. [18:42] phenny: danbri: 04:12Z <kasei> tell danbri I think the foaf spec (html version only) is missing the OWL type (functional) for primaryTopic while isPrimaryTopicOf properly lists it as an IFP.
From Laconica IRC: "duck1123: so do you guys know if anyone has come up with a good foaf property to discover a Person's open microblog url?"
relating agents to orgs
[13:39] danbri: bengee: what's missing, though is the relation between the person and the org [13:39] danbri: [11:18] bengee: i.e. an rdf property for hcard's "org" [15:13] arc-bot: http://arc.semsol.org/community/irc/logs/2008/07/10#T14:13:27Z
foaf:logo should be an IFP?
[09:01] kwijibo: danbri: why isn't foaf:logo an IFP ? (not that there's a really strong reason it needs to be I suppose...) [09:01] kwijibo: but can more than one thing have the same logo? [09:06] danbri: i think we discussed it, and were concerned that sites were autogenerating foaf and leaving default.png in there [09:06] danbri: actually that's for foaf:img more [09:06] danbri: it's certainly a candidate [09:08] kwijibo: thanks danbri - so it's something that could possibly change in the next overhaul you talked about? [09:09] danbri: yeah, if we can find evidence of use, and no evidence it'll cause a mess
is workInfoHomepage inverse functional
Often two parts of the same HTML document describe people in stafflist, for example.
Should we add IFP-ness to the schema definition?
sub-issue, see #foo and document identity