Add registry-compliant YAML files for v0.1.1 - #1
Merged
Conversation
- Added registry-yaml/ directory with official GEDCOM registry format - Includes all 12 required files (7 structures, 4 enumerations, 1 enumeration-set) - These files were submitted to GEDCOM registry via PR #173 - Validated using official GEDCOM registry validator - Added VERSION file (0.1.1) - Added CHANGELOG.md to track version history - Updated README with registry submission status and documentation links The original yaml/ directory is preserved for backward compatibility, but registry-yaml/ contains the authoritative definitions. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Reviewer's GuideThis PR prepares the v0.1.1 release by incorporating official GEDCOM registry-compliant YAML definitions under a new registry-yaml directory, adding release metadata files, and updating documentation to reference the registry submission and new authoritative definitions. Entity relationship diagram for new registry-compliant GEDCOM YAML structureserDiagram
_EVID {
string contact
string label
string lang
string payload
string specification
string type
string uri
}
_FIND {
string contact
string label
string lang
string payload
string specification
string type
string uri
}
_ID {
string contact
string label
string lang
string payload
string specification
string type
string uri
}
_CONC {
string contact
string label
string lang
string payload
string specification
string type
string uri
}
_CONF {
string contact
string label
string lang
string payload
string specification
string type
string uri
}
_RDOC {
string contact
string label
string lang
string payload
string specification
string type
string uri
}
_RACT {
string contact
string label
string lang
string payload
string specification
string type
string uri
}
_EVID ||--o{ _FIND : contains
_EVID ||--o{ _ID : contains
_EVID ||--o| _CONF : contains
_FIND ||--o{ _ID : contains
_ID ||--o{ _RDOC : contains
_CONC ||--o{ _RDOC : contains
_RACT ||--o{ _RDOC : contains
_EVID ||--o| _CONF : has
_CONF }o--|| enumset_Confidence : uses
enumset_Confidence {
string uri
}
enumset_Confidence ||--o{ enum_High : includes
enumset_Confidence ||--o{ enum_Medium : includes
enumset_Confidence ||--o{ enum_Low : includes
enumset_Confidence ||--o{ enum_Hypothesis : includes
enum_High {
string uri
}
enum_Medium {
string uri
}
enum_Low {
string uri
}
enum_Hypothesis {
string uri
}
Class diagram for registry-compliant GEDCOM YAML structure typesclassDiagram
class _EVID {
+contact: string
+label: string
+lang: string
+payload: null
+specification: string[]
+substructures: map
+superstructures: map
+type: structure
+uri: string
}
class _FIND {
+contact: string
+label: string
+lang: string
+payload: null
+specification: string[]
+substructures: map
+superstructures: map
+type: structure
+uri: string
}
class _ID {
+contact: string
+label: string
+lang: string
+payload: string
+specification: string[]
+substructures: map
+superstructures: map
+type: structure
+uri: string
}
class _CONC {
+contact: string
+label: string
+lang: string
+payload: string
+specification: string[]
+substructures: map
+superstructures: map
+type: structure
+uri: string
}
class _CONF {
+contact: string
+label: string
+lang: string
+payload: string
+specification: string[]
+substructures: map
+superstructures: map
+type: structure
+uri: string
}
class _RDOC {
+contact: string
+label: string
+lang: string
+payload: string
+specification: string[]
+substructures: map
+superstructures: map
+type: structure
+uri: string
}
class _RACT {
+contact: string
+label: string
+lang: string
+payload: null
+specification: string[]
+substructures: map
+superstructures: map
+type: structure
+uri: string
}
_EVID --> _FIND : contains
_EVID --> _ID : contains
_EVID --> _CONF : contains
_FIND --> _ID : contains
_ID --> _RDOC : contains
_CONC --> _RDOC : contains
_RACT --> _RDOC : contains
_CONF --> enumset_Confidence : uses
class enumset_Confidence {
+uri: string
+enumeration_values: string[]
}
enumset_Confidence --> enum_High : includes
enumset_Confidence --> enum_Medium : includes
enumset_Confidence --> enum_Low : includes
enumset_Confidence --> enum_Hypothesis : includes
class enum_High {
+uri: string
}
class enum_Medium {
+uri: string
}
class enum_Low {
+uri: string
}
class enum_Hypothesis {
+uri: string
}
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey @glamberson - I've reviewed your changes and they look great!
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds the GEDCOM registry-compliant YAML files and prepares for the v0.1.1 release.
Changes
registry-yaml/directory with official GEDCOM registry formatContext
These YAML files were submitted to the official GEDCOM registry via PR #173 and have been validated using the official GEDCOM registry validator.
The original
yaml/directory is preserved for backward compatibility, butregistry-yaml/contains the authoritative definitions going forward.Registry Compliance
The key differences from our original YAML files:
type: record→type: structure🤖 Generated with Claude Code
Summary by Sourcery
Add registry-compliant YAML definitions for gedcom-evidence and prepare v0.1.1 release.
New Features:
Enhancements:
Documentation: