Jewish family name
Enable an agent to recognise and document a family name associated with Jewish naming contexts, assess the evidence for that association, and use it without inferring a bearer's religion or ancestry from the name alone.
Bundle → Layer → Finding → Questions Filled
6 bundles · 11 layers · 16 findings · 26 questions
Family-name boundary Establishes which designation is being modelled and whether it functions as a family name.
Name function
Examines the role of the designation in its recorded naming context.
Evidence of surname function
Record why the designation is treated as a family name and preserve ambiguity where its role is unresolved.
- What evidence establishes that this designation functions as a family name in the relevant record or community? definition
- Could it instead be a given name, patronymic, title or ritual-name element in this context? boundary
Name and lineage
Separates a shared designation from family-specific instances of its use.
Shared name, distinct families
Record family-specific evidence without making the name itself stand for a single descent group.
- Does the evidence concern the name generally or one identified family's use of it? boundary
- What evidence beyond matching surnames supports any proposed relationship between these families? provenance
Jewish-context association Documents the basis and limits of associating the family name with Jewish naming contexts.
Association basis
Captures what a source actually establishes about Jewish usage of the name.
Attributable association
Distinguish a source's explicit classification from evidence that only attests use by a particular family.
- Which source establishes Jewish-context usage, and what precisely does it claim? provenance
- Is the association with a specific family, a community naming practice or a broader surname category? definition
Association limits
Bounds the association by documented setting and avoids claims of exclusivity.
Context without identity inference
Record the geographic, historical and community limits of usage while keeping bearer identity a separate question.
- For which places, periods and Jewish communities is this association actually documented? boundary
- How should the description express the association without implying that every bearer is Jewish? action
Forms and equivalence Organises attested written forms and the evidence connecting them.
Attested writing
Preserves original spellings and distinguishes source text from editorial rendering.
Original and rendered forms
Record the attested string alongside any transcription, transliteration or normalized search form.
- What exact family-name form appears in the source, and which script and language can be established? provenance
- Which characters or spelling choices were introduced by transcription, transliteration or editorial normalization? boundary
Variant linking
Assesses whether different forms represent related names or merely resemble one another.
Supported form relationships
Type each proposed connection and preserve competing or unconfirmed matches.
- What evidence connects these forms as spelling variants, transliterations, translations or replacements? provenance
- Should retrieval expand to this form, or would doing so merge names whose relationship remains unproven? action
Derivation and family history Separates explanations of the name's formation from documented events in a family's use of it.
Derivation claims
Records proposed linguistic or referential origins with their evidentiary status.
Qualified etymology
Keep proposed meanings, source languages and derivations attributable, including disagreements.
- Which derivation is proposed, by whom, and from what linguistic or documentary evidence? provenance
- Does the proposed meaning establish anything about a particular family's origin, or would that require separate evidence? boundary
Adoption and change
Captures evidenced adoption, inheritance and replacement in a particular family history.
Documented name events
Record who used which form and when, separating attested changes from inferred motives or general historical explanations.
- Which records establish the family's earlier and later name forms, and how narrowly can the transition be dated? measurement
- Is the stated reason for adoption or change documented for this family or inferred from wider circumstances? provenance
Evidence and agent use Governs how an agent evaluates surname claims and applies them in descriptions, retrieval and record comparison.
Claim assessment
Evaluates support for each claim about Jewish usage, name forms and family history.
Traceable surname claims
Attach an inspectable source passage or record reference to each substantive claim and distinguish independent evidence from repetition.
- Which inspected passage or record supports this specific claim about the name? provenance
- Do apparently corroborating surname references supply independent evidence or repeat the same unsupported account? provenance
Bounded application
Determines what the evidence permits an agent to do with the name.
Qualified retrieval and description
Allow contextual description and candidate matching while requiring separate evidence for personal identity or kinship claims.
- Can this evidence support a catalogue association, a search expansion or only a research lead? action
- What additional evidence is required before linking records to one person or treating bearers as relatives? boundary
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these check these first hold for the sense of Jewish family name this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these kinds and varieties hold for the sense of Jewish family name this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these real-world use hold for the sense of Jewish family name this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these failure modes and hazards hold for the sense of Jewish family name this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these regional variation hold for the sense of Jewish family name this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Jewish family name this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Information and virtual systems
- Entry kind
- thing
- Plane
- INF
- Domain
- INF.MED
- Other names and narrower kinds
- Jewish surname-abbreviation
What it is Filled
A Jewish family name is a surname historically used by Jewish families or communities, whose association with Jewish naming traditions does not by itself establish a bearer's ancestry, religion or identity.
In scope
- Family-name forms, scripts, spellings and transliterations
- Evidence supporting a Jewish naming-context association
- Geographic, linguistic and historical limits of that association
- Documented derivations, adoption and changes of family-name forms
- Distinctions between name equivalence, shared spelling and shared lineage
- Permissible interpretation and use of name evidence
Out of scope
- A person's religious affiliation, ethnicity or eligibility for religious status
- Complete genealogies and biological ancestry
- Given names, patronymics, titles and ritual names except where their relationship to a family name requires clarification
- Jewish communities and their institutional histories as independent subjects
- Identity documents and archival collections as complete artifacts
- General models of surnames and personal naming systems
Why it exists Filled
Enable an agent to recognise and document a family name associated with Jewish naming contexts, assess the evidence for that association, and use it without inferring a bearer's religion or ancestry from the name alone.
Distinguishing features Filled
- The designation functions as a family name in the documented context, rather than merely resembling a patronymic, title or given name.
- Its association with Jewish naming contexts has attributable evidence rather than resting on perceived spelling or sound.
- The association specifies a community, place, period or family where evidence permits, rather than treating Jewish usage as uniform.
- Identical spelling does not establish that separate bearers belong to one lineage.
- Classification of the name does not establish that every bearer is Jewish or that the name is exclusively Jewish.
What robots and AI may and may not do Filled
Must not
- Infer or label a person as Jewish from their surname.
- Compile, sort or filter lists of people by supposedly Jewish surnames.
- Use surnames to target people for harassment, exclusion or discrimination.
- Repeat antisemitic claims about names or the people who bear them.
Only with a human decision
- Any use of surname origin in research on identifiable living people.
- Genealogical claims about a specific family that could reveal sensitive heritage.
May
- Explain the historical origins and naming traditions behind a surname from cited sources.
- State clearly that a surname alone does not establish anyone's ancestry, religion or identity.
Moral aspects Filled
- Surname lists have been used to persecute Jews; inference from names must not be repeated.
- Religion and ethnic origin are special categories of personal data in many laws.
Who is affected
- Bearers of these surnames
- Jewish communities
- Families researching their history
Owners Filled
Steward
Nobody owns a surname; the family and each bearer decide how it is used and described.
Links to other meta-models Filled
parent
- Q33283501 - registry parent class
- Q862091 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.jewish-family-name
- Wikidata: Q612090 (https://www.wikidata.org/wiki/Q612090)
Direct properties not applicable Not applicable
- Attested name form: Exact recorded text with language and script where established
- Family-name function: Established family name; context-dependent; disputed; unresolved
- Jewish-context association: Name linked to an evidenced family, community or naming practice with contextual limits
- Variant relationship: Spelling variant; transliteration; translation; documented replacement; proposed relationship; unrelated homograph
- Usage context: Documented place, period, language and community, each allowing unknown values
- Derivation assessment: Supported; competing explanations; conjectural; unknown
- Family-specific name history: Dated or approximately dated adoption, transmission or change linked to a documented family
- Evidence adequacy: Direct attestation; attributed secondary account; uncorroborated report; conflicting evidence; insufficient evidence
Plane INF: no invented physical properties.
Recognition optional Filled
- Appears in text as an ordinary surname; spelling, script or form never settles whether a bearer is Jewish.
- Scholarly onomastic dictionaries and archival records are the evidence for a name's history, not its appearance.
Capabilities and actions required Filled
- Retrieve documented spelling and script variants while retaining their original forms.
- Explain why a name is associated with a particular Jewish naming context and cite the supporting evidence.
- Compare proposed name relationships and flag unsupported equivalence or lineage claims.
- Trace an evidenced family's name adoption or change without generalizing it to all bearers.
- Identify unresolved derivations or classifications and formulate targeted archival research questions.
- Produce qualified catalogue descriptions that do not infer an individual's religion or ancestry.
Hazards and failure modes required Filled
- Name-based inference produces false and harmful labels about individuals.
- Lists of names have been used to target people for persecution and hate.
Standards and interfaces required Filled
- General Data Protection Regulation (EU) 2016/679, European Union, which treats racial or ethnic origin and religious beliefs as special categories of personal data.
Context of use required Filled
- Such surnames are encountered in family histories, archival records and studies of Jewish communities and migration.
- Genealogical and linguistic research examines their documented spellings, geographic contexts and transmission between generations.
- A surname's historical association provides research context but does not establish an individual bearer's religion, ancestry or identity.
Sources Filled
- Wikidata item Q612090: Jewish family name - identity and sense of the item
- Wikipedia: Jewish surname - general description of the item
Open questions
- What operational definition should this registry adopt for 'Jewish family name': documented Jewish usage, association with a Jewish naming tradition, or an attributed scholarly classification?
- Which inspected sources provide adequate coverage across different Jewish communities, languages and historical periods?
- When should distinct derivations or unrelated uses of an identical spelling be represented as separate name senses within this entry?
- What evidence threshold should distinguish an accepted variant relationship from a tentative retrieval alias?
- How should context-dependent family-name status be represented when records do not clearly distinguish surnames from patronymics, titles or ritual-name elements?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q612090/spec.json