Presentation is loading. Please wait.

Presentation is loading. Please wait.

Copyright, Brigham Young University 2001 Brigham Young University Family History Conference March 29, 2001 Marriott School of Management E-Business Center.

Similar presentations


Presentation on theme: "Copyright, Brigham Young University 2001 Brigham Young University Family History Conference March 29, 2001 Marriott School of Management E-Business Center."— Presentation transcript:

1 Copyright, Brigham Young University 2001 Brigham Young University Family History Conference March 29, 2001 Marriott School of Management E-Business Center Genealogy Network Transfer Protocol Note from Conan Albrecht: This project will be run very much like an open- source project. All code written will be under the GNU Public License, and the protocol and architecture will be open to all. I will be setting up a CVS tree for source code management in the next few weeks. If you would like to help by writing a client, a directory server, or helping with the protocol, please e-mail me at conan@warp.byu.edu

2 Copyright, Brigham Young University 2001 Brigham Young University Family History Conference March 29, 2001 Marriott School of Management E-Business Center Genealogy Network Transfer Protocol Conan C. Albrecht, Douglas Dean, Robert B. Jackson, Stephen W. Liddle, Rayman D. Meservy

3 Current Limitations Non-Digital Formats Not searchable in automated waysNot searchable in automated ways Single, unique books exist in different libraries around the worldSingle, unique books exist in different libraries around the world

4 Current Limitations Central Repository (LDS Church) VoluminousVoluminous u Hard to index and search u Costly to store and access u Many delays to publication Management (most complex problem)Management (most complex problem) u Resolution of data conflicts u Owners of data are #1-qualified caretakers Multiplicity of central repositoriesMultiplicity of central repositories

5 Current Limitations WWW Keeps control with owners, butKeeps control with owners, but Unstructured data formatsUnstructured data formats u HTML is a presentation language, not a structured data type language u Hard to search in automated ways u Requires very intelligent agent software u Page scraping

6 Potential Solutions WWW 1.Create smarter agents that can scrape page with near-100% accuracy 2.Make the data more structured

7 Potential Solutions WWW 1.Create smarter agents that can scrape page with near-100% accuracy 2.Make the data more structured

8 Current Limitations XML Distributed and structured, butDistributed and structured, but A document type definition only structures the dataA document type definition only structures the data It does not define how the data is accessed, where it is located, what port to access it through, etc.It does not define how the data is accessed, where it is located, what port to access it through, etc. What automated sharing benefits does it give us beyond GEDCOM?What automated sharing benefits does it give us beyond GEDCOM?

9 Questions That Must Be Answered Why will I share my data?Why will I share my data? u Genealogical researchers are eager to share What data will I share?What data will I share? u Structured genealogical data: family group records, individual records, etc., in XML or GEDCOM format Where will I share it with them?Where will I share it with them? u The Internet is a ubiquitous network Who will I share data with?Who will I share data with? u A registry or index is needed How will I share it with them?How will I share it with them? u A common transfer protocol must be defined u A common searching language must be defined

10 GNTP Protocol and architecture (not an application)Protocol and architecture (not an application) Peer-to-peerPeer-to-peer Central ring of directory serversCentral ring of directory servers Outer ring of data providers (individuals)Outer ring of data providers (individuals)

11 Individual Node Types Directory Server (indexes publishers)Directory Server (indexes publishers) Publisher (publishes source data)Publisher (publishes source data) Publisher/Uploader (accepts uploads from non-technical or non-connected researchers)Publisher/Uploader (accepts uploads from non-technical or non-connected researchers) Searcher (simply searches the network)Searcher (simply searches the network)

12 GNTP Architecture

13 GNTP Protocol Defined similar to SMTP, HTTP, POP3, and other standard protocolsDefined similar to SMTP, HTTP, POP3, and other standard protocols Includes commands for:Includes commands for: u Publication on the network u Directory server indexing of nodes u Node-to-node searching Standard directory server and inter- node searching languageStandard directory server and inter- node searching language

14 GNTP Benefits Supports exact searching with structured data typesSupports exact searching with structured data types Independence from WWW reduces potential for illicit information on networkIndependence from WWW reduces potential for illicit information on network Retains control with users (little overhead to data corrections, additions, etc.)Retains control with users (little overhead to data corrections, additions, etc.)

15 GNTP Benefits Allows immediate, real-time updatingAllows immediate, real-time updating Simple clients with automatic publication and searching allow less- advanced users to participateSimple clients with automatic publication and searching allow less- advanced users to participate

16 GNTP Benefits Distributed as free software (GPL) and protocol definitions, opening boundaries between organizationsDistributed as free software (GPL) and protocol definitions, opening boundaries between organizations We expect many organizations will open their databases as nodes on the networkWe expect many organizations will open their databases as nodes on the network Organizations can still maintain revenue streams as uploaders for researchersOrganizations can still maintain revenue streams as uploaders for researchers

17 Status GNTP 1.0 protocol is nearly finishedGNTP 1.0 protocol is nearly finished Reference implementation client and initial directory server will be finished by JuneReference implementation client and initial directory server will be finished by June Web site and directory server go live July 1, 2001Web site and directory server go live July 1, 2001 LDS Church will create a link on familysearch.org to the “experimental” networkLDS Church will create a link on familysearch.org to the “experimental” network LDS Church will provide genealogical database for initial publisher nodeLDS Church will provide genealogical database for initial publisher node

18 Involvement Research into the most efficient architecture for the inner-ring of directory servers is neededResearch into the most efficient architecture for the inner-ring of directory servers is needed Node interface to the Church genealogical database needs to be developedNode interface to the Church genealogical database needs to be developed Several end-user, publisher clients need to be created (Windows, Mac, Unix, Java, etc.)Several end-user, publisher clients need to be created (Windows, Mac, Unix, Java, etc.)


Download ppt "Copyright, Brigham Young University 2001 Brigham Young University Family History Conference March 29, 2001 Marriott School of Management E-Business Center."

Similar presentations


Ads by Google