Assertion Workflow Example
This example demonstrates the two approaches to recording genealogical data in GLX and when to use each.
The Two Approaches
Approach 1: Direct Property Setting
Set properties directly on entities without creating assertions:
persons:
person-alice-chen:
properties:
name:
value: "Alice Chen"
fields:
given: "Alice"
surname: "Chen"
born_on: "1985-06-15"
born_at: "place-boston"
occupation: "software engineer"Best for:
- Initial data entry from family records
- Quick capture (document evidence later)
- Personal research with trusted sources
- Early stages before formal research begins
Limitations:
- No documented evidence chain
- Hard to verify conclusions later
- Doesn't capture conflicting evidence
Approach 2: Assertion-Backed Properties
Create assertions that document evidence for each property value:
# First, set the property on the person
persons:
person-robert-chen:
properties:
born_on: "1955-03-22"
# Then, create an assertion documenting the evidence
assertions:
assertion-robert-birth:
subject:
person: person-robert-chen
property: born_on
value: "1955-03-22"
citations:
- citation-robert-birth-cert
confidence: high
status: proven
notes: "Primary source: original birth certificate"Best for:
- Professional genealogy research
- Documenting conflicting evidence
- Collaborative research projects
- Building verifiable research trails
The Evidence Chain
Complete evidence documentation follows this pattern:
Repository → Source → Citation → Assertion → Property
↓ ↓ ↓ ↓ ↓
Archives Records Specific Evidence- Concluded
& Docs Reference Based Claim ValueExample chain in this archive:
- Repository:
repository-nyc-records(NYC Department of Records) - Source:
source-nyc-birth-records(NYC Birth Certificates) - Citation:
citation-robert-birth-cert(specific certificate reference) - Assertion:
assertion-robert-birth(claim that Robert was born March 22, 1955) - Property:
person-robert-chen.properties.born_on: "1955-03-22"
Recommended Workflow
For Quick Data Entry
- Create person with properties directly
- Add a note indicating source isn't documented
- Return later to add assertions with evidence
persons:
person-alice-chen:
properties:
born_on: "1985-06-15"
notes: |
Quick entry from family records.
TODO: Add source citations when time permits.For Rigorous Research
- Create sources and repositories first
- Add citations referencing specific evidence
- Create assertions linking citations to claims
- Set properties based on assertion conclusions
Iterative Approach (Best Practice)
Start with direct properties, then add evidence chain incrementally:
- Day 1: Quick data entry with properties
- Week 2: Add source for key documents
- Month 3: Create citations for specific references
- Ongoing: Build assertions as you research
Confidence vs Status
Assertions have two independent fields for tracking certainty and verification:
confidence— how certain you are about the claim (high,medium,low,disputed)status— the research state of the assertion (proven,speculative,disproven)
A confidence: high + status: speculative assertion means "I'm fairly sure this is right, but I haven't verified it yet."
Properties vs Assertions: Key Differences
| Aspect | Properties Only | With Assertions |
|---|---|---|
| Speed | Fast | Slower |
| Evidence | Implicit | Explicit |
| Verification | Difficult | Easy |
| Conflicts | Hidden | Documented |
| Collaboration | Limited | Excellent |
| Audit Trail | None | Complete |
Existential Assertions
An assertion with neither property nor participant is an existential assertion — it simply says "this entity is evidenced by these sources." This is the minimum useful assertion, and is especially helpful for relationships and events where you want to document existence without claiming any specific property value.
relationships:
rel-robert-alice-parent-child:
type: parent_child
participants:
- person: person-robert-chen
role: parent
- person: person-alice-chen
role: child
assertions:
assertion-robert-alice-parentage:
subject:
relationship: rel-robert-alice-parent-child
date: "1990"
citations:
- citation-1990-census-chen
confidence: high
notes: "1990 census lists Robert Chen as head of household with Alice Chen (age 5) as daughter"Adding date makes it temporal: "this relationship existed in 1990." Without date, the assertion simply says the relationship is evidenced by the source, with no temporal scope.
When to use existential assertions:
- Relationships — evidencing a parent-child or marriage without asserting a specific property
- Events — confirming an event occurred without asserting its date or place yet
- Places — documenting that a place existed at a given time
Multiple Evidence for Same Property
Assertions can corroborate each other:
assertions:
assertion-robert-financial-advisor:
subject:
person: person-robert-chen
property: occupation
value: "financial advisor"
citations:
- citation-2000-census-chen # Census record
- citation-linkedin-career # LinkedIn profile
confidence: high
notes: "Multiple sources confirm career change in 1995"Temporal Properties with Assertions
For properties that change over time, create separate assertions for each time period:
persons:
person-robert-chen:
properties:
occupation:
- value: "accountant"
date: "FROM 1978 TO 1995"
- value: "financial advisor"
date: "FROM 1995 TO 2020"
assertions:
assertion-robert-accountant:
subject:
person: person-robert-chen
property: occupation
value: "accountant"
citations: [citation-1990-census-chen]
assertion-robert-financial-advisor:
subject:
person: person-robert-chen
property: occupation
value: "financial advisor"
citations: [citation-2000-census-chen, citation-linkedin-career]Files in This Example
archive.glx- Single-file archive demonstrating both approachesREADME.md- This documentation
See Also
- Temporal Properties Example - Detailed temporal value patterns
- Complete Family Example - Full multi-file archive structure
- Participant Assertions Example - Evidencing who participated in an event
- Core Concepts - Assertion-Aware Data Model
- Assertion Entity - Existential Assertions