gedcom x
play

GEDCOM X http://gedcomx.org/ Ryan Heaton, FamilySearch GEDCOM X - PowerPoint PPT Presentation

GEDCOM X http://gedcomx.org/ Ryan Heaton, FamilySearch GEDCOM X Genealogical Data Exchange Media Types (e.g. JSON) Standard Interface (e.g. REST) SDKs (Java, JavaScript, C#, etc.) application/xml application/pdf


  1. GEDCOM X http://gedcomx.org/ Ryan Heaton, FamilySearch

  2. GEDCOM X ● Genealogical Data Exchange – Media Types (e.g. JSON) – Standard Interface (e.g. REST) – SDKs (Java, JavaScript, C#, etc.)

  3. application/xml application/pdf application/json audio/mpeg image/jpeg image/png image/gif multipart/mixed Media Types text/csv text/css text/html text/plain video/mp4 application/vnd.ms-excel application/calendar+xml application/gzip

  4. GEDCOM X: Media Types ● Semantics – Sources – Persons – Relationships – Evidence – Places – Analysis – Etc.

  5. GEDCOM X: Media Types ● Formats – XML – JSON

  6. GEDCOM X: Date Format Date Description Encoding Type January 18, 1752 at 10:14 +1752-01-18T22:14 Simple Date p.m. From April 13, 1825 to +1825-04-13/+1825-11-26 Date Range November 26, 1825 Until May, 1887 /+1887-03 Open-ended Date Range About 1680 A+1680 Approximate Date Sometime between April 13, A+1825-04-13/+1825-11-26 Approximate Date 1825 and November 26, 1825 Range

  7. GEDCOM X: XML Format <gedcomx xmlns=”http://gedcomx.org/v1”> <person id=”P1”> <source description=”#SD1”/> <name>...</name> </person> <person id=”P2”> <source description=”#SD2”/> <name>...</name> </person> <relationship> <person1 resouce=”#P1”/> <person2 resource=”#P2”/> </relationship> <sourceDescription id=”SD1”> <citation>...</citation> </sourceDescription> <sourceDescription id=”SD2”> <citation>...</citation> </sourceDescription> </gedcomx>

  8. GEDCOM X: JSON Format { “persons” : [ { “id” : “P1”, “sources” : [ { “description” : “#SD1” } ], “names” : [ … ], }, { “id” : “P2”, “sources” : [ { “description” : “#SD2” } ], “names” : [ … ], }, ], “relationships” : [ { “person1” : { “resource” : “#P1” }, “person2” : { “resource” : “#P1” } } ], “sourceDescriptions” : [ { “id” : “SD1”, “citation” : { … }, }, { “id” : “SD2”, “citation” : { … }, } ] }

  9. GEDCOM X: API ● Conforms to REST ● Based on Hypermedia ● Designed for reusable consumer code

  10. GEDCOM X: API <gedcomx xmlns=”http://gedcomx.org/v1”> <person id=”P1”> <link rel=”parents” href=”/path/to/parents”/> <link rel=”children” href=”/path/to/children”/> <link rel=”spouses” href=”/path/to/spouses”/> <name>...</name> </person> <collection id=”P1”> <link rel=”search” template=”/path/to/search{?q}”/> <link rel=”persons” href=”/path/to/persons”/> <link rel=”artifacts” href=”/path/to/artifacts”/> <title>...</title> </person> </gedcomx>

  11. GEDCOM X @FamilySearch ● FamilySearch API ● Internal data exchange – Tree – Records – Sources ● External data exchange – Ancestry – MyHeritage – Etc.

  12. GEDCOM X Start Here http://gedcomx.org/

  13. Questions? Ryan Heaton, FamilySearch

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend