Call for Papers Submissions

The CFPS (Call For Paper Submission) number is a unique identifier for each submitted document. Posted submissions may be referred to by title and author or by CFPS number as, e.g., CFPS 12.

The table may be sorted by clicking on column headers.

You may filter the rows by search string (keywords and visible text are searched as you type):

CFPS Submitter Title Type Created Updated Keywords Description See Also
114 Kessler, Louis Standardized Sources and Citation Templates Proposal 2014-08-30 2014-08-30 sources, citations, formatting, GEDCOM, repository, templates, data transfer This paper describes how GEDCOM currently handles sources and citations, and suggests how a new standard could and should handle them. 63, 65, 78, 112
112 Tychonievich, Luther Desirable Citation Properties Requirement 2014-08-20 2014-08-20 Citations, sources, properties A list of properties that a citation model should strive to achieve. It is unlike that any single model could achieve them all. 63, 65, 78, 114
104 Smith, Richard Proposal to use GEDCOM X’s container format Comment on CFPS 91 2014-02-01 2014-02-01 GEDCOM X, vision This paper considers the proposal to ratify GEDCOM X as a FHISO standard, and supports the adoption of GEDCOM X’s container file format. 91
103 Smith, Richard A trivial timestamp type Proposal 2014-01-29 2014-01-29 dates, timestamps, time zones This paper proposes a light-weight timestamp type for representing the creation and modification times of digital resources. 17, 91
102 Smith, Richard Proposal to support dates BC as negative years Proposal 2014-01-29 2014-01-29 dates, calendars, proleptic calendars, epoch, BC This paper presents a case for allowing dates BC to be recorded using the standard Julian and Gregorian calendars, proposes a representation for such dates that is naturally sortable. 17, 44
101 Trauring, Philip Name Templates Proposal 2014-01-17 2014-01-17 names, given names, surnames, family, religious, internationalization A look at how to include all names associated with a person, in different times, cultures, contexts, etc. A single person might have over a dozen name fields associated with them, and this proposal gives a way to organize them and display them properly, considering the many cultural differences in names. 88
98 Hill, Chris Thoughts on Genealogy Standards Requirement 2013-12-12 2013-12-12 Standards, Modelling, Data Formats, Structures This document has ideas on standards for genealogy systems, how to build them, and on information held within genealogy systems. 6
97 Smith, Richard Type safety in an extensible data model Comment on CFPS 79 2013-11-25 2013-11-25 None This paper resolves some type-safety issues raised in CFPS 79 about the statement formalism of CFPS 77, though which apply equally to CFPS 4′s node formalism. 4, 77, 79
96 Smith, Richard Proposal to allow recording the holders of offices, titles and land Proposal 2013-11-18 2014-02-02 titles, office holders, land ownership, hereditaments, regnal numbers This paper proposes a structured mechanism for recording the ownership of land, and the holders of titles and offices.
95 Smith, Richard Expressing time-dependent personal attributes Requirement 2013-11-16 2013-11-16 statements, properties, time-dependence This paper makes a functional requirement that all personal attributes can be dated, including those such as personal names that cannot be dated in GEDCOM. 4, 77
94 Smith, Richard Recording provenance using statements about statements Proposal 2013-11-14 2013-11-14 data model, statement, provenance, sources, metadata, inference, hypotheses, RDF This paper extends CFPS 77′s statement mechanism with a means of grouping statements into bundles for the purpose of description which it proposes to use to record provenance infomation and other metadata. 4, 77
93 Smith, Richard Requirements for storing media objects Requirement 2013-10-30 2013-10-30 media objects, images, audio, container files, jar files, MIME types, metadata, Dublin Core This paper discusses the requirements for storing media objects, such as images, vidoes and audio recordings, and attaching them to items of genealogical significance.
91 Heaton, Ryan A substantive vision and proposal to validate and ratify the GEDCOM X specification set Proposal 2013-03-29 2013-03-29 GEDCOM X, vision A substantive vision for FHISO, and a proposal that FHISO’s first step in fulfillment of this vision be to validate and ratify the GEDCOM X specification set. 103, 104
90 Gardner, Robert FHISO Microdata Markup Proposal Area to Standardise 2013-08-14 2013-08-14 microdata markup html This paper proposes a microdata markup standard based on the Schema.org vocabulary to be used for genealogical information published on the World Wide Web. The authors propose that FHISO assume responsibility for publishing, promoting, enhancing, and maintaining the standard.
89 Cothey, Viv Sources, events, personae, individuals and graphs Comment on CFPS 72 2013-08-06 2013-08-06 Persona, Person Record, Data Model, Research, Evidence, Conclusion, Nominal Record, Two-tier, N-tier The paper identifies an evidence graph as the basis for an explicitly evidence based and culturally agnostic approach to genealogical information systems. 4, 21, 22, 24, 25, 34, 63, 70, 72, 73, 78
88 Trauring, Philip Asynchronous Collaboration: A Proposal Proposal 2013-07-30 2013-07-30 collaboration, sharing, cloud storage, UUID, media, photographs, documents, sources, geographic, places, events A series of methods for sharing information between different researchers, that are investigating overlapping segments of their family trees, and receiving updates. 101
79 Tychonievich, Luther The Principle of Sensible Disbelief Comment on CFPS 77 2013-06-25 2013-06-25 data model, architecture, statement, graph, RDF The principle of sensible disbelief provides useful research-modelling and disagreement-moderating properties in CFPS 4 which are absent from CFPS 77. 4, 77, 97
78 Kessler, Louis Nine Necessities in a GEDCOM Replacement Requirement 2013-06-05 2013-06-05 sources, conclusions, citations, formatting, places, events, facts, data model, syntax, extensions, registration, testing, updates This paper describes requirements for a Source Detail record and a Place record to be added, and stresses issues such as no extensions, registration and compliance testing, and regular updates, as well as the need to keep the standard as simple as possible. 89, 112, 114
77 Smith, Richard A unified formalism for genealogical statements Comment on CFPS 4 2013-06-05 2013-06-05 Data model, architecture, research This paper proposes a way of unifying the various types of node in the formalism for modelling genealogical research proposed in CFPS 4. 4, 20, 79, 94, 95, 97
75 Smith, Richard Functional requirement for recording searches Requirement 2013-05-22 2013-05-22 search, inference, negative inference This paper discusses the requirement for recording searches, whether proposed, successful or unsuccessful, in addition to the results of the search.
74 Tychonievich, Luther Family History Lexicon Area to Standardise 2013-05-10 2013-05-10 lexicon, dictionary, terms, definitions, vocabulary FHISO should maintain a lexicon of terms and their several meanings to help mitigate confusions caused by terms with multiple distinct usages. And example lexicon is included 23
73 Johnston, Wesley Beyond Lineage-Linked Requirement 2013-05-09 2013-05-09 relationships, community trees, place, merging, sharing, manipulation, sorting, searching, aggregating, reporting, analysis There is a need to model, share, and manipulate relationships other than inter-personal lineage-linkage. 89
72 Wetmore, Thomas Persona Records Area to Standardise 2013-05-01 2013-05-01 Persona, Person Record, Data Model, Research, Evidence, Conclusion, Nominal Record, Two-tier, N-tier A persona record contains a transcription of information about a single person found in a single item from source material. Persona records are important components in genealogical systems that support recording evidence and research. 89
71 Johnston, Wesley Attachments Requirement 2013-05-07 2013-05-07 merge, atttachment, file, image, picture, photograph, document, pdf This paper identifies a few functional requirements for files attached to an entity within a GEDCOM database.
70 Johnston, Wesley Places Requirement 2013-05-07 2013-05-07 place, town, city, street, township, county, country This paper identifies several functional requirements for places within a GEDCOM database. 89
69 Fitzpatrick, Jerry A Transcription Notation for Genealogy Proposal 2013-05-05 2013-05-05 transcription, translation, notation, annotation, note A proposed notation for improving the transcription and translation of genealogical sources. 27
68 Smith, Richard Comments on the serialisation of date ranges in CFPS 17 and CFPS 40 Comment on CFPS 40 2013-04-30 2013-04-30 None Comments on alternative syntaxes for date ranges, and the need to define their semantics including the arithmetic of durations and dates. 17, 40, 67
67 Smith, Richard Proposal to extend the calendar style mechanism of CFPS 43 into an abstract formatting model Proposal 2013-04-30 2013-04-30 dates, calendars, date style, formatting, calendar facets CFPS 43′s style mechanism is extended into abstract formatting model that would allow applications to format correctly dates written in many unknown calendar systems. 17, 37, 38, 40, 43, 44, 68
65 Tychonievich, Luther A Gradual Path to Standardised Citations Proposal 2013-04-26 2013-04-29 sources, citations, names, outref, xref, cross-references, xlink, pointers, variants Citations are a mix of out-references and cross-references. These can be standardised independently of a Citations Names Authority. 112, 114
63 Proctor, Tony Proposal for Handling Sources and Citations Proposal 2013-04-22 2013-04-22 Sources, Citations Proposal for handling sources and citations 89, 112, 114
44 Smith, Richard Proposal to support the Julian calendar similarly to CFPS 17 Proposal 2013-04-19 2013-04-19 dates, calendars, Julian calendar, Gregorian calendar Proposal for a Julian calendar with years starting on 1 Jan 17, 67, 102
43 Smith, Richard Proposal to add style to the wholly-numeric representation of dates in CFPS 13 Proposal 2013-04-19 2013-04-19 dates, calendars, date style, Julian calendar, Roman calendar, regnal years Proposal to separate presentation from representation in calendars in order to avoid a proliferation of calendars. 13, 67
40 Tychonievich, Luther Sortable, Versatile CFPS 17 Comment on CFPS 17 2013-04-17 2013-04-17 Dates, ISO-8601, Quarters CFPS 17′s yearly quarters are not sortable with other dates; fixing this makes the proposal more general as well. 17, 67, 68
38 Smith, Richard Proposal for compound calendars to resolve a difficulty with default calendars Proposal 2013-04-14 2013-04-14 dates, calendars, calendar change, Gregorian calendar, Julian calendar, English calendar Proposal to allow the default calendar to be dependent on the date. 13, 67
37 Smith, Richard Proposal for a scalable extensibility mechanism Proposal 2013-04-12 2013-04-12 extensibility, vendor extensions, forwards compatibility, decentralised development, XML namespaces, URIs Proposal to address certain extensibility requirements by using XML namespaces, but without requiring the use of XML. 67
36 Proctor, Tony Proposal for Accommodating Custom Properties Proposal 2013-04-03 2013-04-20 Properties, Customisation, Person Proposal for accommodating custom properties for persons
34 Proctor, Tony Requirement to Separate Evidence and Conclusion Requirement 2013-03-30 2013-04-20 Evidence, Conclusion, Mark-up Requirement to separate evidence and conclusion 89
31 Proctor, Tony Requirement to Support Family History Data Requirement 2013-03-29 2013-04-20 Family-history, Genealogy, Events, Narrative Requirement to support both Family History and Genealogy data
27 Proctor, Tony Requirement for Representing Uncertain Characters Requirement 2013-03-27 2013-04-20 Transcription, Mark-up, UCF Requirement for representing uncertain characters in transcribed data 69
25 Proctor, Tony Proposal to Accommodate Structured Events Proposal 2013-03-07 2013-04-20 Events, Events-protracted, Events-hierarchical Proposal to accommodate protracted and hierarchical events 89
24 Proctor, Tony Proposal to Adopt Certain Core Record Linkages Proposal 2013-03-14 2013-04-20 Record-linkage, Events, Persons, Sources, Personae Proposal for the major record linkages in the data model 89
23 Proctor, Tony Proposal to Defining a Preferred Vocabulary Area to Standardise 2013-03-19 2013-04-20 Glossary, Vocabulary Proposal to define a Preferred Vocabulary and Glossary 74
22 Proctor, Tony Proposal for Handling Place References Proposal 2013-03-21 2013-04-20 Place-references, Place-hierarchies Proposal for Handling Place References 89
21 Proctor, Tony Proposal for Handling Personal Names Proposal 2013-03-19 2013-04-20 Personal-names Proposal for Handling Personal Names 89
20 Proctor, Tony Proposal for Handling Partially Controlled Vocabularies Proposal 2013-03-13 2013-04-20 Tag-Values, Namespaces, Software-vocabulary Proposal for handling partially controlled vocabularies for types 77
19 Proctor, Tony Proposal to Create a Standard Run-time Object Model Area to Standardise 2013-02-25 2013-04-20 Object-model, Scripting, Queries Proposal to have a standard object model to support scripting and query languages.
18 Proctor, Tony Proposal to Accommodate Mark-up in Narrative Text Proposal 2013-03-08 2013-04-20 Text, Narrative, Mark-up Proposal to accommodate mark-up in all forms of narrative text
17 Proctor, Tony Proposal to Accommodate Gregorian Dates using a Modified ISO 8601 Proposal 2013-03-06 2013-04-20 Dates, ISO-8601, Quarters Proposed adoption of a modified ISO 8601 subset to accommodate Gregorian dates, and yearly quarters thereof 40, 44, 67, 68, 102, 103
16 Proctor, Tony Requirement for Locale Independence in Data Representations Requirement 2013-03-11 2013-04-20 Locales, Portability, Serialisation-format Functional requirement for locale independence in representations of the Data Model.
15 Proctor, Tony Proposal to Accommodate Event Constraints Proposal 2013-03-06 2013-04-20 Events, Event-ordering Proposed adoption constraints between events
14 Proctor, Tony Proposal for a Generalised Dual-Date Representation Proposal 2013-03-06 2013-04-20 Dates, Dual-dates, World-calendars Proposal for a generalised dual-date representation that applies to multiple calendars 13
13 Proctor, Tony Proposal to Accommodate Alternative World Calendar Systems Proposal 2013-03-11 2013-04-20 Dates, World-calendars Proposed adoption of a date syntax applicable to multiple world calendars, both historical and modern-day. 14, 38, 43
8 Tychonievich, Luther Selector Language for Family History Conclusions Area to Standardise 2013-03-15 2013-03-15 selector, template, relationship, attribute, conclusion, regular expression, XPath There should be a standard way to express things like “two people, one the second cousin of the other, both from Prussia.” 5
7 Tychonievich, Luther Multi-Granularity Standards Requirement 2013-03-17 2013-03-17 Data model, requirement, conflict, multiple standards, import, export, granularity, lattice Tools must be able to import course-grained information because existing usage patterns presume incompatible data granularity.
6 Tychonievich, Luther Partial Implementations and Extensions Requirement 2013-03-15 2013-04-16 partial implementation, extension, collaboration Round-trip communication between tools supporting different portions of the data standard should behave sanely. Nine use cases demonstrate what that means. 98
5 Tychonievich, Luther Inference Rules Proposal 2013-03-15 2013-03-15 inference, indirect evidence, evidence, rule, extension Inference rules used in indirect evidence should be codified within the data model. 8
4 Tychonievich, Luther Modeling Research, not Conclusions Proposal 2013-03-10 2013-03-10 Data model, architecture, research An data model architecture for storing each step in the research process, simplifying collaboration. 77, 77, 79, 89, 94, 95, 97

To view a paper in your browser (if your browser supports viewing PDF files), simply click on any of the titles above. If you would like to save a copy locally, right click on the title and choose the “Save Link As…” option (or your browser’s equivalent).