A short informal nickname characterising an agent (includes login identifiers, IRC and other chat nicknames).
Long before social networks had profile pages, people were known online by short handles: an IRC nickname, a Unix login, a forum name. foaf:nick was part of FOAF from early on precisely to capture that. Its definition is “a short informal nickname characterising an agent”, and the parenthesis spells out what is included: login identifiers, IRC and other chat nicknames.
One property, two kinds of nickname
The definition covers two quite different things. One is the social nickname: “Danny” for Daniel, “Kit” for Katherine. The other is the technical handle: dokafor on a chat server or a version control system. FOAF does not separate them, and a person’s description can hold several foaf:nick values of either kind, in any order.
This is convenient for casual profiles and a little loose for archival use. A record in a born-digital collection that needs to say which handle was used where (for example, to connect an email archive with chat logs from the same project) will want more structure than a list of strings.
Nick, name and online accounts
FOAF has three places for names of an agent, each with a different job:
| Property | Holds | Example |
|---|---|---|
| foaf:name | the formal name | “Daniel Okafor” |
| foaf:nick | an informal name or handle | “dokafor”, “Danny” |
| foaf:accountName (on foaf:OnlineAccount) | a username on a named service | “dokafor” at chat.example.org |
foaf:name is the property interfaces should display. foaf:nick is supplementary. When a username belongs to a particular service, the foaf:OnlineAccount pattern shown in the example records the service together with the name, which a bare nick cannot do.
There is no formal sub-property link between foaf:nick and rdfs:label, unlike foaf:name. A generic RDF browser will not show a nick as the resource’s caption, which is usually the desired behavior.
Nicknames in archival description
Personal papers and organizational records increasingly include email, chat exports and code repositories. In those sources, people often appear only under handles. Recording each handle as a foaf:nick (or as an account) on the person’s authority record gives researchers a way to connect a commit message signed “dokafor” to a named person.
Two cautions apply. First, handles can expose information the person did not intend to publish, such as an internal login that doubles as an email address. Privacy review applies to nicks exactly as it does to names, and perhaps more strictly. Second, a handle is not an identity. Many people have used “admin” or “dan” over the years, and merging records on a shared nick produces false matches. FOAF reflects this: properties like foaf:mbox are declared inverse functional so they can identify a person, while foaf:nick carries no such declaration.
Language and form
Nicknames are usually untagged literals. When a nickname is a word in a particular language (a translated pet name, for instance) a language tag can be added, but for technical handles it adds nothing and should be left off. Case should be preserved as the person or system used it, because some services treat DOkafor and dokafor as different accounts.
Nicknames in quotation marks inside a formal name (“Daniel ‘Danny’ Okafor”) are a habit carried over from print biographies. In FOAF data they are better split: the formal name in foaf:name, the nickname in its own foaf:nick statement, so neither search nor display has to strip punctuation.
For contact details that sit next to handles in many profiles, foaf:phone uses tel: URIs, and the FOAF vocabulary overview lists the other agent properties available.
Example in RDF
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
<https://example.org/id/person/0977> a foaf:Person ;
foaf:name "Daniel Okafor" ;
foaf:nick "dokafor" , "Danny" ;
foaf:account [
a foaf:OnlineAccount ;
foaf:accountServiceHomepage <https://chat.example.org/> ;
foaf:accountName "dokafor"
] .
Questions about foaf:nick
What is foaf:nick used for?
It records a short informal name for an agent: a nickname used by friends, a login identifier, or a handle on IRC or another chat system. The definition names all three, so the property covers both social nicknames and technical usernames.
What is the difference between foaf:nick and foaf:name?
foaf:name holds what a thing is formally called, such as a full personal or organization name. foaf:nick holds an informal alternative. A person can have one display name and several nicknames, each in its own foaf:nick statement.
Can a person have several foaf:nick values?
Yes. The property is not functional, so a person can list a childhood nickname, a work login and a chat handle. Nothing in FOAF says which one is current, so data that needs that distinction should add context elsewhere.
Should I use foaf:nick or foaf:OnlineAccount for a username?
For a username tied to a specific service, foaf:OnlineAccount with foaf:accountName and foaf:accountServiceHomepage is more precise, because it says which service the name belongs to. foaf:nick is fine when the service does not matter.
Is a nickname a reliable identifier?
No. Nicknames are reused by different people and change over time. FOAF treats identifying properties, such as foaf:mbox, as inverse functional; foaf:nick is not, so two records sharing a nick should never be merged on that basis alone.