-
There exists today a way to use the EE certainty vocabulary to say things like:
- User A thinks Image B is _Certainly_ the source of Record C.
- User X thinks Persona Y is _Possibly_ a source for (con…
-
I realise the infinite flexibility of inheriting everything from a Resource and hence allowing it to be considered a source but this also makes for infinite complexity and infinite nonsense!
To allow…
-
The "Preferred" flag assumes that there is a single preference but does not allow for:
(a) instances where conflicting hypotheses may be of equal validity (and hence need further research to prove on…
-
[Analysis of the GEDCOM X file format](http://familysearch.github.com/gedcomx/2012/07/03/file-format-jeers-cheers.html) shows that the ZIP file format is significantly inefficient under certain scenar…
-
Over on https://github.com/gittip/shields.io/issues/15 you'll see that Gittip has acquired Shields, as far as @olivierlacan and I are concerned. However, in the spirit of openness and transparency, I'…
-
I love how gedcomx is generally based on modern formats and api approaches. But I'm struck in [GEDCOM X: File Format](http://www.gedcomx.org/File-Format.html) by the use of the ancient MIME format, w…
-
The “QName role” in RelationshipReference is “denormalized” information, right? The role is defined in the Relationship, so storing it in the reference is redundant and opens the possibility of it n…
-
I've had some experience working with Linked Data and the RDF data model, and, on perusing through several recipes and the documentation relating to the GEDCOM X data model, I am unclear how the GEDCO…
-
Is there supposed to be a connection between events and facts? I don't see any right now.
As an example of what I'm talking about:
- It seems that a Birth Event should somehow be connected to the Bi…
-
The current specification has the following "Known Relationship Types" defined:
> | URI | description |
> | --- | --- |
> | `http://gedcomx.org/Couple` | A relationship of a pair of persons. |
> | `h…