Repository navigation
feat(schema): add an address record and map it to other formats - #73
Merged
Merged
Conversation
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
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.
A small JSON object for passing a whole Nigerian address between systems, built around the postcode reference this repository already defines.
docs/schemas/address.schema.jsonrequires onlypostcode(a postcode reference) andcountry. It adds optional names (state,lga,locality),street_address,description, andlocation. The MCP suite validates its examples, rejects malformed records, and resolves the nested reference from the file beside it.docs/address-record.mdsays where each field comes from and maps the record onto ISO 20022, FHIR, schema.org, and vCard. Names come from NIPOST's lookup at level 2, since the libraries hold no name tables.The payments note gives field lengths from the Federal Reserve's ISO 20022 sheet (16 characters for the postcode, so the hyphenated code fits). It states no date for Swift retiring unstructured addresses, because Swift's pages and bank guidance disagreed when I checked.