Search results

rfc2616 is now obsolete

Status: Open.

#338 In FamilySearch/gedcomx;

· MarioGravel opened on Aug 18, 2024

Limitations of Current Name Parts

Status: Open.

#330 In FamilySearch/gedcomx;

· clarkegj opened on Nov 6, 2020

Does the GroupRole type have any recommended role types?

Status: Open.

#325 In FamilySearch/gedcomx;

· eneufeld opened on Apr 25, 2019

Change 'gender' to 'sex' to align with contemporary usage

Status: Open.

#318 In FamilySearch/gedcomx;

· brylie opened on Jan 20, 2019

·  

2.0.0

JSON Schema

improvement

Status: Open.

#312 In FamilySearch/gedcomx;

· nealvs opened on Jun 11, 2018

Non-resolvable URIs

Status: Open.

#310 In FamilySearch/gedcomx;

· gmr opened on Jan 27, 2018

Metadata about the originating software of the GEDCOM X data

Status: Open.

#306 In FamilySearch/gedcomx;

· justincy opened on Feb 20, 2017

How should ambiguous relationships be expressed?

Status: Open.

#299 In FamilySearch/gedcomx;

· justincy opened on Jun 23, 2016

Link serialization specs to the conceptual model

Status: Open.

#294 In FamilySearch/gedcomx;

· justincy opened on May 27, 2016

ArgoUML model doesn't match online FamilySearch media types

Status: Open.

#260 In FamilySearch/gedcomx;

· bobfields opened on Jun 27, 2013

Updated "Home" page for GEDCOM X

Status: Open.

#252 In FamilySearch/gedcomx;

· thomast73 opened on May 16, 2013

Establish criteria/workflow for "standardization"

Status: Open.

#196 In FamilySearch/gedcomx;

· pipian opened on Jul 29, 2012