-
Notifications
You must be signed in to change notification settings - Fork 4
Add gedcom-evidence extension v0.1.3 #178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,16 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| lang: en-US | ||
|
|
||
| type: enumeration set | ||
|
|
||
| uri: https://github.com/glamberson/gedcom-evidence/enumset-Confidence | ||
|
|
||
| enumeration values: | ||
| - "https://github.com/glamberson/gedcom-evidence/enum-High" | ||
| - "https://github.com/glamberson/gedcom-evidence/enum-Medium" | ||
| - "https://github.com/glamberson/gedcom-evidence/enum-Low" | ||
| - "https://github.com/glamberson/gedcom-evidence/enum-Hypothesis" | ||
|
|
||
| contact: "https://github.com/glamberson/gedcom-evidence" | ||
| ... |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,16 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| lang: en-US | ||
|
|
||
| type: enumeration set | ||
|
|
||
| uri: https://github.com/glamberson/gedcom-evidence/enumset-Confidence | ||
|
|
||
| enumeration values: | ||
| - "https://github.com/glamberson/gedcom-evidence/enum-High" | ||
| - "https://github.com/glamberson/gedcom-evidence/enum-Medium" | ||
| - "https://github.com/glamberson/gedcom-evidence/enum-Low" | ||
| - "https://github.com/glamberson/gedcom-evidence/enum-Hypothesis" | ||
|
|
||
| contact: "https://github.com/glamberson/gedcom-evidence" | ||
| ... | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| lang: en-US | ||
|
|
||
| type: enumeration | ||
|
|
||
| uri: https://github.com/glamberson/gedcom-evidence/enum-High | ||
|
|
||
| extension tags: _HIGH | ||
|
|
||
| specification: | ||
| - High Confidence | ||
| - Strong confidence in evidence relevance and interpretation | ||
|
|
||
| value of: | ||
| - https://github.com/glamberson/gedcom-evidence/enumset-Confidence | ||
|
|
||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| ... |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| lang: en-US | ||
|
|
||
| type: enumeration | ||
|
|
||
| uri: https://github.com/glamberson/gedcom-evidence/enum-Hypothesis | ||
|
|
||
| extension tags: _HYPOTHESIS | ||
|
|
||
| specification: | ||
| - Hypothesis | ||
| - Speculative connection requiring further research | ||
|
|
||
| value of: | ||
| - https://github.com/glamberson/gedcom-evidence/enumset-Confidence | ||
|
|
||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| ... |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| lang: en-US | ||
|
|
||
| type: enumeration | ||
|
|
||
| uri: https://github.com/glamberson/gedcom-evidence/enum-Low | ||
|
|
||
| extension tags: _LOW | ||
|
|
||
| specification: | ||
| - Low Confidence | ||
| - Weak confidence, significant uncertainty | ||
|
|
||
| value of: | ||
| - https://github.com/glamberson/gedcom-evidence/enumset-Confidence | ||
|
|
||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| ... |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| lang: en-US | ||
|
|
||
| type: enumeration | ||
|
|
||
| uri: https://github.com/glamberson/gedcom-evidence/enum-Medium | ||
|
|
||
| extension tags: _MEDIUM | ||
|
|
||
| specification: | ||
| - Medium Confidence | ||
| - Moderate confidence, some uncertainty remains | ||
|
|
||
| value of: | ||
| - https://github.com/glamberson/gedcom-evidence/enumset-Confidence | ||
|
|
||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| ... |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| lang: en-US | ||
| type: enumeration | ||
| uri: https://github.com/glamberson/gedcom-evidence/enum-High | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This seems like a duplicate of enumeration/extension/enum-High.yaml. |
||
| extension tags: | ||
| - _HIGH | ||
| specification: | ||
| - High Confidence | ||
| - Strong confidence in evidence relevance and interpretation | ||
| value of: | ||
| - https://github.com/glamberson/gedcom-evidence/enumset-Confidence | ||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| ... | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| lang: en-US | ||
| type: enumeration | ||
| uri: https://github.com/glamberson/gedcom-evidence/enum-Hypothesis | ||
| extension tags: | ||
| - _HYPOTHESIS | ||
| specification: | ||
| - Hypothesis | ||
| - Speculative connection requiring further research | ||
| value of: | ||
| - https://github.com/glamberson/gedcom-evidence/enumset-Confidence | ||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| ... |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| lang: en-US | ||
| type: enumeration | ||
| uri: https://github.com/glamberson/gedcom-evidence/enum-Low | ||
| extension tags: | ||
| - _LOW | ||
| specification: | ||
| - Low Confidence | ||
| - Weak confidence, significant uncertainty | ||
| value of: | ||
| - https://github.com/glamberson/gedcom-evidence/enumset-Confidence | ||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| ... |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| lang: en-US | ||
| type: enumeration | ||
| uri: https://github.com/glamberson/gedcom-evidence/enum-Medium | ||
| extension tags: | ||
| - _MEDIUM | ||
| specification: | ||
| - Medium Confidence | ||
| - Moderate confidence, some uncertainty remains | ||
| value of: | ||
| - https://github.com/glamberson/gedcom-evidence/enumset-Confidence | ||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| ... |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,31 @@ | ||
| %YAML 1.2 | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Current convention is that records go under structure (hence under structure/extension). Standard records are structure/standard/record-*.yaml. |
||
| --- | ||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| extension tags: _EVID | ||
| label: Evidence Container Record | ||
| lang: en-US | ||
| payload: null | ||
| specification: | ||
| - Evidence Container Record | ||
| - 'An _EVID record represents a piece of evidence as an independent object, | ||
| separate from any specific conclusion or individual. This allows "floating | ||
| evidence" that can be associated with multiple potential individuals or | ||
| left unassociated until identity can be determined. | ||
| Evidence containers preserve original source information exactly as found, | ||
| including names, dates, places, and relationships, without forcing premature | ||
| identity conclusions. This solves the "Which John Smith?" problem by allowing | ||
| evidence to exist independently until research determines the correct association.' | ||
| substructures: | ||
| https://gedcom.io/terms/v7/CHAN: '{0:1}' | ||
| https://gedcom.io/terms/v7/EXID: '{0:M}' | ||
| https://gedcom.io/terms/v7/NOTE: '{0:M}' | ||
| https://gedcom.io/terms/v7/SNOTE: '{0:M}' | ||
| https://gedcom.io/terms/v7/SOUR: '{1:M}' | ||
| https://gedcom.io/terms/v7/UID: '{0:M}' | ||
| https://github.com/glamberson/gedcom-evidence/_CONF: '{0:1}' | ||
| https://github.com/glamberson/gedcom-evidence/_FIND: '{0:M}' | ||
| https://github.com/glamberson/gedcom-evidence/_ID: '{0:M}' | ||
| superstructures: [] | ||
| type: record | ||
| uri: https://github.com/glamberson/gedcom-evidence/record-EVID | ||
| ... | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| extension tags: _RDOC | ||
| label: Research Documentation Record | ||
| lang: en-US | ||
| payload: null | ||
| specification: | ||
| - Research Documentation Record | ||
| - 'A record documenting research reasoning, analysis, and decisions. _RDOC | ||
| records capture the "why" behind associations between evidence and | ||
| individuals, including proof arguments and conflict resolution. | ||
| This supports the Genealogical Proof Standard by documenting reasonably | ||
| exhaustive searches, complete source citations, analysis and correlation, | ||
| resolution of conflicts, and soundly reasoned conclusions.' | ||
| substructures: | ||
| https://gedcom.io/terms/v7/CHAN: '{0:1}' | ||
| https://gedcom.io/terms/v7/DATE: '{0:1}' | ||
| https://gedcom.io/terms/v7/EXID: '{0:M}' | ||
| https://gedcom.io/terms/v7/NOTE: '{0:M}' | ||
| https://gedcom.io/terms/v7/SNOTE: '{0:M}' | ||
| https://gedcom.io/terms/v7/UID: '{0:M}' | ||
| https://github.com/glamberson/gedcom-evidence/_RACT: '{0:M}' | ||
| superstructures: [] | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. _CONC and _ID and _RACT all list _RDOC as a substructure, so should this list them as superstructures? Or is the intent to have those structures have substructures that point to an _RDOC? If so, that needs two URIs: one for the record (this one) and another for the pointer structure (compare pointer https://gedcom.io/terms/v7/SNOTE and record https://gedcom.io/terms/v7/record-SNOTE) |
||
| type: record | ||
| uri: https://github.com/glamberson/gedcom-evidence/record-_RDOC | ||
| ... | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| extension tags: _CONC | ||
| label: Evidence Conclusion | ||
| lang: en-US | ||
| payload: '@<https://github.com/glamberson/gedcom-evidence/_EVID>@' | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Because _EVID has a superstructure (is not a record) it cannot be pointed to. |
||
| specification: | ||
| - Evidence Conclusion | ||
| - 'A reference from an individual or family to evidence that supports | ||
| conclusions about that person or family. This creates the reverse | ||
| link from conclusions to supporting evidence. | ||
| _CONC structures allow individuals and families to document which | ||
| evidence supports their existence and characteristics, completing | ||
| the bidirectional relationship between evidence and conclusions.' | ||
| substructures: | ||
| https://gedcom.io/terms/v7/NOTE: '{0:M}' | ||
| https://gedcom.io/terms/v7/QUAY: '{0:1}' | ||
| https://github.com/glamberson/gedcom-evidence/_RDOC: '{0:M}' | ||
| superstructures: | ||
| https://gedcom.io/terms/v7/record-FAM: '{0:M}' | ||
| https://gedcom.io/terms/v7/record-INDI: '{0:M}' | ||
| type: structure | ||
| uri: https://github.com/glamberson/gedcom-evidence/_CONC | ||
| ... | ||
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,21 @@ | ||||||||
| %YAML 1.2 | ||||||||
| --- | ||||||||
| contact: https://github.com/glamberson/gedcom-evidence | ||||||||
| extension tags: _CONF | ||||||||
| label: Evidence Confidence | ||||||||
| lang: en-US | ||||||||
| payload: https://github.com/glamberson/gedcom-evidence/enumset-Confidence | ||||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||
| specification: | ||||||||
| - Evidence Confidence | ||||||||
| - 'Overall confidence assessment for a piece of evidence. This differs | ||||||||
| from QUAY (quality of data) by assessing the researcher''s confidence | ||||||||
| in the evidence''s relevance and interpretation. | ||||||||
| Confidence levels can change as additional evidence is discovered | ||||||||
| and analysis progresses.' | ||||||||
| substructures: | ||||||||
| https://gedcom.io/terms/v7/NOTE: '{0:M}' | ||||||||
| superstructures: | ||||||||
| https://github.com/glamberson/gedcom-evidence/_EVID: '{0:1}' | ||||||||
| type: structure | ||||||||
| uri: https://github.com/glamberson/gedcom-evidence/_CONF | ||||||||
| ... | ||||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| extension tags: _EVID | ||
| label: Evidence Reference | ||
| lang: en-US | ||
| payload: XREF | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The value of the payload for a pointer should be the URI it points to, like @https://github.com/glamberson/gedcom-evidence/_RACT@ (but replacing that with the correct URI, I'm not sure what it's pointing to. |
||
| specification: | ||
| - Evidence Reference | ||
| - 'A reference from an individual to an evidence container record, indicating | ||
| that this evidence may support conclusions about this individual. The reference | ||
| includes a confidence level indicating how strongly the evidence supports the | ||
| association with this specific individual.' | ||
| substructures: | ||
| https://github.com/glamberson/gedcom-evidence/_CONF: '{0:1}' | ||
| https://gedcom.io/terms/v7/NOTE: '{0:M}' | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Shouldn't this list include _ID and _FIND? They both list _EVID as a superstructure |
||
| superstructures: | ||
| https://gedcom.io/terms/v7/record-INDI: '{0:M}' | ||
| type: structure | ||
| uri: https://github.com/glamberson/gedcom-evidence/_EVID | ||
| ... | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| extension tags: _FIND | ||
| label: Evidence Finding | ||
| lang: en-US | ||
| payload: null | ||
| specification: | ||
| - Evidence Finding | ||
| - 'A specific finding or fact extracted from evidence. _FIND structures | ||
| represent individual pieces of information found in sources, such as | ||
| names, dates, places, ages, relationships, or occupations. | ||
| Findings preserve the exact information as it appears in the source, | ||
| including original spelling, formatting, and context, allowing researchers | ||
| to maintain data fidelity throughout the research process.' | ||
| substructures: | ||
| https://gedcom.io/terms/v7/AGE: '{0:1}' | ||
| https://gedcom.io/terms/v7/DATE: '{0:1}' | ||
| https://gedcom.io/terms/v7/NOTE: '{0:M}' | ||
| https://gedcom.io/terms/v7/PLAC: '{0:1}' | ||
| https://gedcom.io/terms/v7/TEXT: '{0:1}' | ||
| https://gedcom.io/terms/v7/TYPE: '{1:1}' | ||
| https://github.com/glamberson/gedcom-evidence/_ID: '{0:M}' | ||
| superstructures: | ||
| https://github.com/glamberson/gedcom-evidence/_EVID: '{0:M}' | ||
| type: structure | ||
| uri: https://github.com/glamberson/gedcom-evidence/_FIND | ||
| ... |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| extension tags: _ID | ||
| label: Evidence Identifier | ||
| lang: en-US | ||
| payload: '@<https://gedcom.io/terms/v7/record-INDI>@ | @<https://gedcom.io/terms/v7/record-FAM>@ | @<https://gedcom.io/terms/v7/record-SOUR>@' | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We don't currently have pointers that can point to multiple types of records in the spec, so this won't pass YAML validation. The workaround I know of now is replacing _ID with three different structures (perhaps _IDI, _IDF, and _IDS), each pointing to just one type of thing. Reverse pointers (from INDI to _ID) won't work because we also don't allow pointers to substructures. As an aside, I have proposed before being loser with identifiers, but because many software implementations use relational databases having polymorphic pointers or non-record pointers can be problematic form implementers and don't seem to be likely to be added anytime soon. |
||
| specification: | ||
| - Evidence Identifier | ||
| - 'An identifier reference from evidence to an individual, family, or other | ||
| record. This creates a bidirectional link between evidence and conclusions, | ||
| allowing evidence to be associated with multiple potential individuals. | ||
| The _ID structure supports gradual refinement of identity as research | ||
| progresses, with confidence levels and research documentation.' | ||
| substructures: | ||
| https://gedcom.io/terms/v7/NOTE: '{0:M}' | ||
| https://gedcom.io/terms/v7/QUAY: '{0:1}' | ||
| https://github.com/glamberson/gedcom-evidence/_RDOC: '{0:M}' | ||
| superstructures: | ||
| https://github.com/glamberson/gedcom-evidence/_EVID: '{0:M}' | ||
| https://github.com/glamberson/gedcom-evidence/_FIND: '{0:M}' | ||
| type: structure | ||
| uri: https://github.com/glamberson/gedcom-evidence/_ID | ||
| ... | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| %YAML 1.2 | ||
| --- | ||
| contact: https://github.com/glamberson/gedcom-evidence | ||
| extension tags: _RACT | ||
| label: Research Activity | ||
| lang: en-US | ||
| payload: null | ||
| specification: | ||
| - Research Activity | ||
| - 'A record of a specific research activity, including searches performed, | ||
| sources consulted, and findings. _RACT records support research logs | ||
| and document the research process over time. | ||
| Research activities can reference evidence found, conclusions drawn, | ||
| and documentation of negative searches (sources checked that yielded | ||
| no relevant information).' | ||
| substructures: | ||
| https://gedcom.io/terms/v7/CHAN: '{0:1}' | ||
| https://gedcom.io/terms/v7/DATE: '{0:1}' | ||
| https://gedcom.io/terms/v7/NOTE: '{0:M}' | ||
| https://gedcom.io/terms/v7/SNOTE: '{0:M}' | ||
| https://gedcom.io/terms/v7/SOUR: '{0:M}' | ||
| https://gedcom.io/terms/v7/TYPE: '{0:1}' | ||
| https://gedcom.io/terms/v7/UID: '{0:M}' | ||
| https://github.com/glamberson/gedcom-evidence/_RDOC: '{0:M}' | ||
| superstructures: {} | ||
| type: structure | ||
| uri: https://github.com/glamberson/gedcom-evidence/_RACT | ||
| ... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like a duplicate of enumeration-set/extension/enumset-Confidence.yaml.