serialize a person and a parent-child/couple relationship using the gedcom x conceptual model

domain: gedcomx.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Reference the GEDCOM X Conceptual Model and JSON Format specs in github.com/FamilySearch/gedcomx/specifications — this is the same model FamilySearch's own Family Tree API returns as application/x-gedcomx-v1+json
  2. Build a root gedcomx JSON object holding a persons[] array; give each person an id, gender (type URI such as http://gedcomx.org/Male), and a names[] array with a nameForm and typed parts (Given, Surname)
  3. Add facts[] entries typed with GEDCOM X fact-type URIs (e.g. http://gedcomx.org/Birth, http://gedcomx.org/Residence) each carrying a date.original/formal and place.original
  4. To express a relationship, add a relationships[] entry with type http://gedcomx.org/ParentChild (directional: person1=parent, person2=child) or http://gedcomx.org/Couple per relationship-types-specification.md
  5. Optionally attach sourceDescriptions[] and reference them from a person/relationship's sources to carry citations, mirroring how FamilySearch's Person resource embeds a sourceDescriptions array

Known gotchas

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans