The function of the Registry of Peoples (ROP) is to document standardized codes used for identifying the primary peoples of the world. The ROP provides a reference list of identifiers representing discrete human aggregations.
The Editor and Steward of the Registry of Peoples is Jim Courson, IMB.
1. Identifiers – The Registry provides a unique code and preferred name for each people.
- ROP3 – ROP3 codes are the primary codes within ROP. ROP3 Codes are 6-digit, numeric fields that provide a unique identifier for each people. Each code is perpetual; it will not be used more than once, even if the people it identifies is removed from the database.
- ROP3 PeopleName – ROP3 PeopleNames are identifiers recommended as standard reference names. Each reference name is based on the self-name or a representative construct name of a people as determined by the Registry Editor. These identifiers are stored in tblROP3people as PeopleName.
2. Descriptors – The Registry provides two descriptors for each people group. A minimum of two descriptors is necessary to accurately define a people.
- Location Descriptor – People live in an identifiable location. Each code will reference at least one location descriptor, although it will sometimes reference more, as many people groups of the world are spread across geo-political boundaries. Location descriptors (People in Country) are stored in tblROP3geoIndex and a Primary Location (PLOC) descriptor is identified in tblROP3people.
- Language Descriptor – People communicate using language. Each code should include at least one language descriptor. As language for a given people group often varies by country, language descriptors are stored in tblROP3geoIndex and a Primary Language (PROL) descriptor is identified in tblROP3people.
3. Hierarchy – The Registry includes a hierarchy that moves from Affinity Bloc to People Cluster to Kinship Group to People.
- Registry Hierarchy – With the latest update, each code references a ROP2.5 Kinship Group code (tblROP25kinshipgroup). Each ROP2.5 Kinship Group code references a ROP2 People Cluster code (tblROP2peoplecluster). Each ROP2 People Cluster code references a ROP1 Affinity Bloc code (tblROP1affinitybloc).
Code Tables within the Registry of Peoples follow a naming convention that begins with tblROP.
tblROP3people is the primary code table of the registry, containing the ROP3 code and the recommended reference name for each people. Primary consideration is given to the name by which the people call themselves. Each ROP3 code references a ROP2.5 Kinship Group code (tblROP25kinshipgroup). For legacy code support, each ROP3 code also references a ROP2 People Cluster code (tblROP2peoplecluster).
tblROP3people contains the following fields:
tblROP25kinshipgroup codes relate ROP3 peoples that share an ethnic kinship. Each ROP2.5 Kinship Group code references a ROP2 People Cluster code (tblROP2peoplecluster).
tblROP25kinshipgroup contains the following fields:
tblROP2peoplecluster codes relate kinship groups of people that share a common identity. Each ROP2 People Cluster code references a ROP1 Affinity Bloc code (tblROP1affinitybloc).
tblROP2peoplecluster contains the following fields:
tblROP1affinitybloc codes relate people clusters that share an affinity based on common language, history, or culture.
tblROP1AffinityBloc contains the following fields:
tblROP3geoIndex is a linking table that cross-references each ROP3 People code to codes for one or more geographical locations in which the people are reported to live.
tblROP3geoIndex contains the following fields:
This section defines the process that the registry editor will follow to maintain the registry.
1. Governing Philosophy – Changes will be made to the Registry of Peoples as often as needed to add, remove, or clarify the codes.
2. How to make a change request – Any query, perceived error, or suggested clarification may be proposed by email to firstname.lastname@example.org.
3. How change requests are processed – When a change request is received, review and dialogue will be conducted and changes, if required, will be made to the appropriate code table as soon as possible.
4. How Updates are Made – Registry code tables are updated regularly, and web APIs reflect the latest edits
ROP code tables are available through an ArcGIS web API: