Person Name Vocabulary

language en
Person Name Vocabulary
Version 1.1, release date: 2019-07-01
Authors:
Lodewijk Petram, Huygens Institute for the History of the Netherlands
Elvin Dechesne, Ordina, The Netherlands
Gijsbert Kruithof, National Archives, The Netherlands
Contributors:
Jeroen Balkenende, Central Bureau of Genealogy, The Netherlands
Gerrit Bloothooft, Utrecht University, The Netherlands
Bob Coret, Coret Genealogie
Sebastiaan Derks, Huygens Institute for the History of the Netherlands
Menno den Engelse, Hic Sunt Leones
Ed de Heer, National Archives, The Netherlands
Gerard Kuys, Ordina, The Netherlands
Harm Nijboer, Huygens Institute for the History of the Netherlands
Vincent Sleebe, National Archives, The Netherlands
Leon van Wissen, University of Amsterdam, The Netherlands
Publisher:
Lodewijk Petram, Huygens Institute for the History of the Netherlands
Involved institutions:
img/LOGO-officieel.gif

Machine-readable formats:
Turtle syntax, OWL/XML syntax, JSON-LD
Imported Ontologies:
foaf
schema
cidoc-crm
wikidata-wd
wikidata-wdt
DBpedia
License:
https://creativecommons.org/licenses/by-nc-sa/4.0/
Person Name Vocabulary Specification
Abstract
The Person Name Vocabulary (PNV) is an rdf vocabulary and data model for persons’ names. It is applicable to many datasets in which persons are described, as it accommodates different levels of data granularity. It furthermore allows for easy alignment of name elements, including idiosyncratic ones, such as family name prefixes and patronymics, with standard vocabularies such as schema.org, foaf, DBpedia and Wikidata, thus guaranteeing optimal data interoperability.

Table of contents
1. Introduction
1.1. Example 1: Jan de Vries
1.2. Example 2: Michiel Adriaensz. de Ruyter
2. PNV: Overview
3. PNV: Description
3.1. Name variants in PNV
3.2. Best practices for semantic annotations to persons and names
3.3. Modelling examples
4. Cross reference for PNV classes, properties and dataproperties
4.1. Classes
4.2. Object Properties
4.3. Data Properties
5. References
5.1. PNV implementations
5.2. Namespace declarations
5.3. XML vocabularies
6. Acknowledgements
Introduction back to ToC
This document describes the Person Name Vocabulary (PNV), an rdf vocabulary and data model for persons’ names. Since people are central to many (research) datasets, and the same persons may appear in multiple datasets, good findability, re-usability and interoperability of persons’ data is beneficial to data users. The PNV allows data providers to make their persons’ data findable, re-usable and interoperable, while maintaining the level of detail in which the persons’ names are described. It can be used to model a person and his/her name (including possible name variants) and as a controlled vocabulary for labelling name elements. While the PNV is suitable for names from many parts of the world, it was principally developed to model idiosyncrasies of (historical) Dutch names in rdf. The following two examples show how the PNV accommodates these idiosyncrasies.

Example 1: Jan de Vries
Jan de Vries is a short and simple name, but it is hard to model it correctly using standard vocabularies for persons’ names. The full name (‘Jan de Vries’) and given name (‘Jan’) do not pose any problems. The family name (‘de Vries’), however, is where it gets tricky. In the Netherlands, the prefix (‘de’) is generally separated from the base surname (‘Vries’), because family names are sorted by the base surname. This would not be too big a problem, but for the fact that ‘De Vries’ is seen in Belgium and other countries as an inseparable name. PNV allows Dutch users to model ‘Jan de Vries’ as follows:

Example Jan de Vries
Fig 1: Name elements of ‘Jan de Vries’ in PNV
Example 2: Michiel Adriaensz. de Ruyter
Michiel Adriaensz. de Ruyter, the name of a famous Dutch admiral, features a patronym (‘Adriaensz.’), a very common name element in the early-modern Low Countries. Using PNV, this name would be modelled as such:

Example Michiel Adriaensz. de Ruyter
Fig 2: Name elements of ‘Michiel Adriaensz. de Ruyter’ in PNV
As can be seen from the two examples, the PNV accommodates up to eleven different name elements, which will be further introduced in the data properties section below. What is important to add at this point, is that those properties for which an equivalent property exists in foaf, schema.org of Wikidata, are automatically mapped to their equivalent properties. pvn:baseSurname does not have an equivalent property, but when joined together with pnv:surnamePrefix a pnv:surname is formed, which is equivalent to schema-org:familyName, foaf:familyName and wikidata-wdt:P734. All name elements taken together form pnv:literalName, which is equivalent to schema-org:name, foaf:name, and wikidata-wdt:P2561. Figure 3 shows how the name ‘Jan de Vries’ would ultimately be described in PNV, with a decreasing level of granularity when going from left (to be used e.g. for sorting, automated entity linkage, or onomastics research) to right (to be used e.g. for exposing the data to search engines).

Example Jan de Vries in full
Fig 3: Jan de Vries in PNV
PNV is flexible: users can pick and choose which properties to use and which to leave blank. The pnv:literalName property is an exception. This property may only be left blank if a person’s name is unknown or if a person was unnamed (e.g. a child that died shortly after being born).

PNV: Overview back to ToC
The PNV has the following classes and properties.

Classes
Person (@nl: persoon)
A person’s name (@nl: Naam van een persoon)
cidoc-crm:E21_Person
dbpedia:Person
wikidata-wd:Q5
schema:Person
foaf:Person
dbpedia:Name
wikidata-wd:Q1071027
cidoc-crm:E41_Appellation
Data Properties
base surname (@nl:basis achternaam)
disambiguating description (@nl:onderscheidend achtervoegsel)
first name (Biodes) (@nl:voornaam BioDes)
full name (@nl:volledige naam)
given name suffix (@nl:toevoegsel voornaam)
given name (@nl:een of meer voornamen)
honorific suffix (@nl:titel (adellijk of burgerlijk) als achtervoegsel)
infix title (@nl:adellijke titel in het midden van een naam)
infix (BioDes)
initials (@nl:initialen)
name specification (@nl:naamspecificatie)
patronym (@nl:patroniem)
prefix (@nl:voorvoegsel)
suffix (BioDes) (@nl:achtervoegsel BioDes)
surname (@nl:familienaam)
surname prefix (@nl:tussenvoegsel)
trailing patronym (@nl:patroniem na achternaam)
foaf:name
schema:name
wikidata-wdt:P2561
foaf:familyName
schema:familyName
wikidata-wdt:P2561
foaf:givenName
schema:givenName
wikidata-wdt:P735
schema:honorificPrefix
schema:honorificSuffix
schema:disambiguatingDescription
PNV: Description back to ToC
PNV is aimed at correctly describing (and thus identifying) persons. Figure 4 shows the structure of the vocabulary: there is a number of data properties that describe name elements or specify the type of name (variant). Taken together, these properties define a class: a name. This class is related to the person class (pnv:Person, which is equivalent to cidoc:E21, dbpedia:Person and schema:Person), as it is the name of a person.

Visualization of Person Name Vocabulary
Fig 4: Visualization of PNV structure
Some of the properties are very similar (pnv:givenName and pnv:firstName, for example). Naturally, they are not meant to be used simultaneously. The availability of similar-looking properties stems from the premise of creating a flexible vocabulary, with a broad choice of options so that there is always a (near-)perfect fit for a user’s data elements. Figure 5 shows how the various properties are related. Most users would start with the properties on the left side of the diagram and go from there to the centre. However, users who have modelled their data following the BioDes rules, would find that they have e.g. first names and patronyms in one field. To accommodate these users, extra properties were created, which are shown on the right side of the diagram.

Structure of Person Name Vocabulary
Fig 5: Full PNV menu
Name variants in PNV
A person can have multiple pnv:hasName relations to multiple pnv:PersonName objects, each describing a different name variant. Figure 6 shows how three different observations of the name of a particular person can be modelled in PNV. This figure also goes to show that if person’s name is known, the full name should always be stated using the pnv:literalName property. The pnv:nameSpecification property can be used to specify the type of name. See the next section (3.2) for best practices of further annotations, including specifying the time period in which a name variant was used.

Name variants in PNV
Fig 6: Name variants in PNV
Best practices for semantic annotations to persons and names
It is recommended to add semantic annotations to pnv:Person objects, as this increases readability of the data for both humans and machines. Furthermore, semantic annotations to pnv:PersonName objects can be used for indicating particularities of a specific name (variant).

The following annotations are recommended for pnv:Person objects:

Include semantic information on the object in an rdfs:label property, indicating that the object describes a person observation. The value of the rdfs:label property for a pnv:Person object on Albert Einstein would e.g. be “Albert Einstein (person)”.
Include (the preferred variant of) the person’s full name in a skos:prefLabel property to allow for easy display of the name.
The following annotations are recommended for pnv:PersonName objects—mainly for person’s names with multiple variants (otherwise optional):

Include semantic information on the object in an rdfs:label property, e.g. indicating that the object describes a particular variant of a person’s name. The value of the rdfs:label property for a pnv:PersonName object that describes the married name of the Dutch journalist that figures in the explanation of Name variants in PNV would e.g. be “Annemarie de Bourbon de Parme-Gualtherie van Weezel (married name)”.
Include the person’s full name (variant) in a skos:prefLabel property to allow for easy display of the name.
Use pnv:nameSpecification for a short description of the name variant being described. The value can be a text string (e.g. “married name”) or a URI (e.g. “https://www.wikidata.org/prop/direct/P2562”).
Use dct:coverage to specify a date (use xsd:date or xsd:dateTime) or time period for a name (variant). To specify a time periode, the property can be linked to e.g. a sem:Time object, with a sem:hasLatestBeginTimeStamp and, optionally, also a sem:hasEarliestEndTimeStamp, or to a crm:E52_Time-Span object, with a crm:P81a_end_of_the_begin and, optionally, also a crm:p81b_begin_of_the_end, or to an an edm:TimeSpan object, with an edm:begin and, optionally, also an edm:end.
References to other rdf resources or a web page can be added using a rdfs:seeAlso property.
Modelling examples
PNV example 1 – Leiden archive (Erfgoed Leiden en Omstreken – Historisch Leiden in kaart) – Menno den Engelse
@prefix schema: <http://schema.org/> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix pnv: <https://w3id.org/pnv#> . @prefix roar: <https://w3id.org/roar#> . @prefix persooninbron: <https://historischleideninkaart.nl/persooninbron/> . persooninbron:508 schema:gender schema:Male ; rdfs:label “Symon bestorven zoon van Zybrant Gerytsz botercoper” ; pnv:hasName [ a pnv:PersonName ; pnv:givenName “Zybrant” ; pnv:patronym “Gerytsz” ; pnv:literalName “Zybrant Gerytsz” ; ]; a roar:PersonObservation .
PNV example 2 (name variants of Annemarie de Bourbon de Parme) – Lodewijk Petram
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix pnv: <https://w3id.org/pnv#> . <http://example.com/24008889> a pnvPerson ; rdfs:label “Annemarie de Bourbon de Parme – Gualthérie van Weezel (person) ; skos:prefLabel: “Annemarie de Bourbon de Parme – Gualthérie van Weezel” ; pnv:hasName [ a pnv:PersonName ; rdfs:label “Annemarie de Bourbon de Parme – Gualthérie van Weezel” ; pnv:literalName “Annemarie de Bourbon de Parme – Gualthérie van Weezel” ; pnv:nameSpecification <https://www.wikidata.org/prop/direct/P2562> ] , [ a pnv:PersonName ; rdfs:label “Annemarie de Bourbon” ; pnv:literalName “Annemarie de Bourbon” ] , [ a pnv:PersonName ; rdfs:label “Annemarie Cecilia Gualthérie van Weezel” ; pnv:surname “Gualthérie van Weezel” ; pnv:givenName “Annemarie Cecilia” ; pnv:literalName “Annemarie Cecilia Gualthérie van Weezel” ; pnv:nameSpecification “birth name” ] .
PNV example 3 (name variant) – Amsterdam City Archives – Leon van Wissen
@prefix schema: <http://schema.org/> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix pnv: <https://w3id.org/pnv#> . saaPerson:saaId26049798p2 a saa:Person ; rdfs:label “Anna Beumier”, “Anna Beunjer” ; schema:gender schema:Female ; pnv:hasName [ a pnv:PersonName ; rdfs:label “Anna Beumier” ; pnv:baseSurname “Beumier” ; pnv:givenName “Anna” ; pnv:literalName “Anna Beumier” ], [ a pnv:PersonName ; rdfs:label “Anna Beunjer” ; pnv:baseSurname “Beunjer” ; pnv:givenName “Anna” ; pnv:literalName “Anna Beunjer” ] .
Cross reference for PNV classes, properties and dataproperties back to ToC
This section provides details for each class and property defined by PNV.
Classes
Person (@nl: persoon)
A person’s name (@nl: Naam van een persoon)
cidoc-crm:E21_person
dbpedia:Person
wikidata-wd:Q5
schema:Person
foaf:Person
dbpedia:Name
wikidata-wd:Q1071027
cidoc-crm:E41_Appellation
Personc back to ToC or Class ToC
@nl:Persoonc back to ToC or Class ToC
IRI: https://w3id.org/pnv#Person

A Person is a human being whose individual existence can somehow be documented

is in domain of
has name (@nl: heeft naam) op
is disjoint with
A person’s name (@nl: Naam van een persoon) c
A person’s namec back to ToC or Class ToC
@nl:Naam van een persoonc back to ToC or Class ToC
IRI: https://w3id.org/pnv#PersonName

A name is considered to be a resource type in its own right

PersonName

is in domain of
base surname (@nl:basis achternaam) dp, disambiguating description (@nl:onderscheidend achtervoegsel) dp, first name (Biodes) (@nl:voornaam BioDes) dp, full name (@nl:volledige naam) dp, given name suffix (@nl:toevoegsel voornaam) dp, given name (@nl:een of meer voornamen) dp, honorific suffix (@nl:titel (adellijk of burgerlijk) als achtervoegsel) dp, infix title (@nl:adellijke titel in het midden van een naam) dp, infix (BioDes) dp, initials (@nl:initialen) dp, name specification (@nl:naamspecificatie) dp, patronym (@nl:patroniem) dp, prefix (@nl:voorvoegsel) dp, suffix (BioDes) (@nl:achtervoegsel BioDes) dp, surname (@nl:familienaam) dp, surname prefix (@nl:tussenvoegsel) dp, trailing patronym (@nl:patroniem na achternaam) dp
is in range of
has name (@nl: heeft naam) op
is disjoint with
Person (@nl:Persoon) c
cidoc_crm:E21_Personc back to ToC or Class ToC
IRI: http://www.cidoc-crm.org/cidoc-crm/E21_Person

is equivalent to
Person (@nl:Persoon) c
dbpedia:Personc back to ToC or Class ToC
IRI: http://dbpedia.org/ontology/Person

is equivalent to
Person (@nl:Persoon) c
wikidata-wd:Q5c back to ToC or Class ToC
IRI: https://www.wikidata.org/entity/Q5

is equivalent to
Person (@nl:Persoon) c
schema:Personc back to ToC or Class ToC
IRI: http://schema.org/Person

is equivalent to
Person (@nl:Persoon) c
foaf:Personc back to ToC or Class ToC
IRI: http://xmlns.com/foaf/0.1/Person

is equivalent to
Person (@nl:Persoon) c
dbpedia:Namec back to ToC or Class ToC
IRI: http://dbpedia.org/ontology/Name

is equivalent to
A person’s name (@nl:Naam van een persoon) c
wikidata-wd:Q1071027c back to ToC or Class ToC
IRI: https://www.wikidata.org/entity/Q1071027

is equivalent to
A person’s name (@nl:Naam van een persoon) c
cidoc-crm:E41_Appellationc back to ToC or Class ToC
IRI: http://www.cidoc-crm.org/cidoc-crm/E41_Appellation

is equivalent to
A person’s name (@nl:Naam van een persoon) c
Object Properties
has name (@nl:heeft naam)
has nameop back to ToC or Object Property ToC
@nl:heeft naamop back to ToC or Object Property ToC
IRI: https://w3id.org/pnv#hasName

has domain
Person (@nl:Persoon) c
has range
A person’s name (@nl:Naam van een persoon) c
Data Properties
base surname (@nl:basis achternaam)
disambiguating description (@nl:onderscheidend achtervoegsel)
first name (Biodes) (@nl:voornaam BioDes)
full name (@nl:volledige naam)
given name suffix (@nl:toevoegsel voornaam)
given name (@nl:een of meer voornamen)
honorific suffix (@nl:titel (adellijk of burgerlijk) als achtervoegsel)
infix title (@nl:adellijke titel in het midden van een naam)
infix (BioDes)
initials (@nl:initialen)
name specification (@nl:naamspecificatie)
patronym (@nl:patroniem)
prefix (@nl:voorvoegsel)
suffix (BioDes) (@nl:achtervoegsel BioDes)
surname (@nl:familienaam)
surname prefix (@nl:tussenvoegsel)
trailing patronym (@nl:patroniem na achternaam)
foaf:name
wikidata-wdt:P2561
foaf:familyName
schema:familyName
wikidata-wdt:P734
foaf:givenName
schema:givenName
wikidata-wdt:P735
schema:honorificPrefix
schema:honorificSuffix
schema:disambiguatingDescription
base surnamedp back to ToC or Data Property ToC
@nl:basis achternaamdp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#baseSurname

BioDes:achternaam

A2A:PersonNameLastName

A Base surname is a family name without any prefixes, if those prefixes need to be ignored in sorting. If the family name is e.g. ‘de Vries’ and it needs to be sorted under ‘V’, the Base surname is ‘Vries’. Base surname is equivalent to BioDes:geslachtsnaam.

has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
disambiguating descriptiondp back to ToC or Data Property ToC
@nl:onderscheidend achtervoegseldp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#disambiguatingDescription

A Disambiguating description is a name part that is appended to make sure that the right person is designated. Name parts like ‘Sr.’ and ‘Jr.’, used to distinguish a child from his parent, are disambiguating descriptions.

has equivalent properties
schema:disambiguatingDescriptione dp
has super-properties
suffix (BioDes) (@nl:achtervoegsel BioDes) dp
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
first name (Biodes)dp back to ToC or Data Property ToC
@nl:voornaam BioDesdp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#firstName

BioDes:voornaam

A First name is a combination of a given name, a patronym (if any) and a given name suffix. This property is only to be used by data providers who have combined these name elements into one field (following the BioDes structure). First name is equivalent to BioDes:voornaam.

has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
full namedp back to ToC or Data Property ToC
@nl:volledige naamdp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#literalName

A2A:PersonNameLiteral

Literal name designates a full personal name. This property may only be left blank if a person’s name was unknown or if a person was unnamed (e.g. a child that died shortly after being born), in which cases the property pnv:nameSpecification should state “unknown” or “unnamed”.

has equivalent properties
foaf:name dp, wikidata-wdt:P2561 dp
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
given name suffixdp back to ToC or Data Property ToC
@nl:toevoegsel voornaamdp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#givenNameSuffix

A Given name suffix is a name part that is appended to a given name. In the name of the fifteenth-century Duke of Burgundy Philip the Good, for example, ’the Good’ is the Given name suffix.

has super-properties
given name (@nl: een of meer voornamen) dp
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
given namedp back to ToC or Data Property ToC
@nl:een of meer voornamendp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#givenName

A2A:PersonFirstName

A Given name designates the name(s) given to someone at birth or any other name-giving event.

has equivalent properties
foaf:givenName dp, schema:givenName dp, wikidata-wdt:P735 dp
has sub-properties
given name suffix (@nl:toevoegsel voornaam) dp
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
honorific suffixdp back to ToC or Data Property ToC
@nl:titel (adellijk of burgerlijk) als achtervoegseldp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#honorificSuffix

An Honorific suffix is a name part that is appended to distinguish someone.

has equivalent properties
schema:honorificSuffix dp
has super-properties
suffix (BioDes) (@nl:achtervoegsel BioDes) dp
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
infix titledp back to ToC or Data Property ToC
@nl:adellijke titel in het midden van een naamdp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#infixTitle

An Infix title designates a title in the middle of a name.

has super-properties
infix (BioDes) dp
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
initialsdp back to ToC or Data Property ToC
@nl:initialendp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#initials

A2A:PersonNameInitials

An initial is the first letter of a person’s given name (or sometimes a combination of letters). The Initials property can be used to separately record the initial(s) of a person’s given name(s). Each initial should be followed by a dot. It is recommended to always use the Initials property to record initials, but if only the initials of a given name are known, they may also be recorded using pnv:givenName (or pnv:firstName). Example 1: “Peter R. de Vries” would be modelled using pnv:initials “P.R.” and pnv:givenName “Peter R.”. Example 2: “C.Joh. Kieviet” would ideally be modelled using pnv:initials “C.Joh.”, but pnv:givenName “C.Joh.” is also possible. Example 3: “H.A.F.M.O. (Hans) van Mierlo” would be modelled using pnv:initials “H.A.F.M.O.” and pnv:givenName “Hans”.

has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
name specificationdp back to ToC or Data Property ToC
@nl:naamspecificatiedp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#nameSpecification

The Name specification property can be used to specify the type of name, e.g. to discern between name variants, or to state that the person’s name is unknown or that the person was unnamed, e.g. in the case of a child that died before it was given a name. It can be a string (e.g. “unknown”, “unnamed”, “religious name”, “stage name”, “pen name”, “married name” or “birth name”) or a reference to a controlled vocabulary.

has domain
A person’s name (@nl:Naam van een persoon) c
patronymdp back to ToC or Data Property ToC
@nl:patroniemdp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#patronym

A2A:PersonNamePatronym

A Patronym is a name element based on the given name of one’s father or grandfather. This is also the preferred property for a matronym (i.e. a name element based on the given name of one’s mother or grandmother).

has sub-properties
trailing patronym (@nl:patroniem na achternaam) dp
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
prefixdp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#prefix

BioDes:prepositie

A2A:PersonNameTitle

A2A:PersonNameTitleOfNobility

A Prefix is a noble or honorific title prefixing a name, e.g. ‘Prof. dr.’ or ‘Jhr.’

has equivalent properties
schema:honorificPrefix dp
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
suffix (BioDes)dp back to ToC or Data Property ToC
@nl:achtervoegsel BioDesdp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#suffix

BioDes:postpositie

A Suffix designates name elements that come after the family name. This property is only to be used by data providers who have structured their name elements following the BioDes structure.

has sub-properties
disambiguating description (@nl:onderscheidend achtervoegsel) dp, honorific suffix (@nl:titel (adellijk of burgerlijk) als achtervoegsel) dp
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
surnamedp back to ToC or Data Property ToC
@nl:familienaamdp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#surname

A2A:PersonNameFamilyName

A surname is the name of the family a person is born into, including one or more prefixes. In some cases the honorific prefix can be incorporated into the surname (e.g. Van Welderen baron Rengers).

has equivalent properties
foaf:familyName dp, schema:familyName dp, wikidata-wdt:P734 dp
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
surname prefixdp back to ToC or Data Property ToC
@nl:tussenvoegseldp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#surnamePrefix

A2A:PersonNamePrefixLastName

A Surname prefix is a name part prefixing the surname (e.g. ‘van’ or ‘van den’).

has super-properties
top data property
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
trailing patronymdp back to ToC or Data Property ToC
@nl:patroniem na achternaamdp back to ToC or Data Property ToC
IRI: https://w3id.org/pnv#trailingPatronym

A Trailing patronym refers to the parent’s given name, suffixing the person’s family name, mostly used for disambiguation.

has super-properties
patronym (@nl: patroniem) dp
has domain
A person’s name (@nl:Naam van een persoon) c
has range
string
foaf:namedp back to ToC or Data Property ToC
IRI: http://xmlns.com/foaf/0.1/name

has equivalent properties
full name (@nl:volledige naam) dp, wikidata-wdt:P2561 dp
wikidata-wdt:P2561dp back to ToC or Data Property ToC
IRI: https://www.wikidata.org/prop/direct/Property:P2561

has equivalent properties
full name (@nl:volledige naam) dp, foaf:name dp
foaf:familyNamedp back to ToC or Data Property ToC
IRI: http://xmlns.com/foaf/0.1/familyName

has equivalent properties
surname (@nl:familienaam) dp, schema:familyName dp, wikidata-wdt:P734 dp
schema:familyNamedp back to ToC or Data Property ToC
IRI: https://schema.org/familyName

has equivalent properties
surname (@nl:familienaam) dp, foaf:familyName dp, wikidata-wdt:P734 dp
wikidata-wdt:P734dp back to ToC or Data Property ToC
IRI: https://www.wikidata.org/prop/direct/Property:P734

has equivalent properties
surname (@nl:familienaam) dp, foaf:familyName dp, schema:familyName dp
foaf:givenNamedp back to ToC or Data Property ToC
IRI: http://xmlns.com/foaf/0.1/givenName

has equivalent properties
given name (@nl:een of meer voornamen) dp, schema:givenName dp, wikidata-wdt:P735 dp
schema:givenNamedp back to ToC or Data Property ToC
IRI: https://schema.org/givenName

has equivalent properties
given name (@nl:een of meer voornamen) dp, foaf:givenName dp, wikidata-wdt:P735 dp
wikidata-wdt:P735dp back to ToC or Data Property ToC
IRI: https://www.wikidata.org/prop/direct/Property:P735

has equivalent properties
given name (@nl:een of meer voornamen) dp, foaf:givenName dp, schema:givenName dp
schema:honorificPrefixdp back to ToC or Data Property ToC
IRI: https://schema.org/honorificPrefix

has equivalent properties
prefix dp
schema:honorificSuffixdp back to ToC or Data Property ToC
IRI: https://schema.org/honorificSuffix

has equivalent properties
honorific suffix (@nl:titel (adellijk of burgerlijk) als achtervoegsel) dp
schema:disambiguatingDescriptiondp back to ToC or Data Property ToC
IRI: https://schema.org/disambiguatingDescription

has equivalent properties
disambiguating description (@nl:onderscheidend achtervoegsel) dp
Legend back to ToC
c: Classes
op: Object Properties
dp: Data Properties
ni: Named Individuals
References back to ToC
PNV implementations
Links to Linked Open Data collections that use PNV:

*** for corrections / updates please contact the publisher of this vocabulary ***
Golden Agents
Historisch Leiden in Kaart (Erfgoed Leiden en Omstreken)
Nationaal Archief (National Archives of the Netherlands)
Genealogie Online – WO2 slachtoffers
Soon: Digital data collections of Huygens Institute for the History of the Netherlands
Namespace declarations
Table 1: Namespaces used in this document
pnv <https://w3id.org/pnv#>
foaf <http://xmlns.com/foaf/0.1>
owl <http://www.w3.org/2002/07/owl>
rdf <http://www.w3.org/1999/02/22-rdf-syntax-ns>
cidoc-crm <http://www.cidoc-crm.org/cidoc-crm>
wikidata-wd <http://www.wikidata.org/entity>
wikidata-wdt <http://www.wikidata.org/prop/direct/>
xsd <http://www.w3.org/2001/XMLSchema>
schema <http://schema.org>
skos <http://www.w3.org/2004/02/skos/core>
rdfs <http://www.w3.org/2000/01/rdf-schema>
dbpedia <http://dbpedia.org/ontology>
default namespace <https://w3id.org/pnv#>
XML vocabularies
Links to XML vocabularies referred to in this documentation:

A2A
BioDes
Acknowledgements back to ToC
The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document, and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.