Product: Linked Data Interfaces

Welcome! Forums Technical Details Product: Linked Data Interfaces

Tagged: ,

This topic contains 0 replies, has 1 voice, and was last updated by  Brandon 2 years, 7 months ago.

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #146

    Brandon
    Keymaster

    One “product” that we have discussed is to build a Linked Data interface to each of the online databases (FamilySearch, EarlyLDS, Nauvoo Community, MormonPlaces) to enable them to link to each other, and to better enable software to read and work with the data automatically. That is, each person in EarlyLDS would have a URL/web page (separate from the existing page) that would be formatted very similarly to a page for that person in the Nauvoo Community site.

    Here are some possible discussion points:

    1. FamilySearch already has an API; would it be worthwhile to build an API for EarlyLDS, Nauvoo, etc.?
    2. What are the formats to support in a linked data API? JSON-LD? RDF? The existing pages+RDFa?
    3. What ontologies/vocabularies/schemas can we leverage (e.g., schema.org, FOAF, BIO, GEDCOMX)? What will we need to invent?
    4. Will we need to transform the data model of each database into a common model, or can we just represent the data as-is?
Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.