Skip to content
This repository is currently being migrated. It's locked while the migration is in progress.

Add JSON Schema for VA Form 27-2008#1171

Draft
tarratsco wants to merge 3 commits into
masterfrom
optimus/27-2008-schema
Draft

Add JSON Schema for VA Form 27-2008#1171
tarratsco wants to merge 3 commits into
masterfrom
optimus/27-2008-schema

Conversation

@tarratsco
Copy link
Copy Markdown
Contributor

⚠️ AI-Generated PR — This pull request was automatically generated by Optimus. All code requires human review and testing before merging.

New schema — VA Form 27-2008

Summary

This schema covers VA Form 27-2008 — Application for United States Flag for Burial Purposes. It is authored against JSON Schema Draft-04 and includes the following key elements:

  • Shared definitions for common field types: date (ISO 8601 format, YYYY-MM-DD pattern), ssn (9-digit string), phone (10-digit string), email (format-validated, max 254 characters), and usaState (enum of all U.S. state and territory abbreviations including DC).
  • additionalProperties: false is set at the root level, enforcing a strict schema boundary and preventing undeclared fields from being accepted.
  • The schema is expected to capture veteran identification details, service history, burial information, and applicant/requester contact information consistent with the purpose of the form (requesting a U.S. burial flag for a deceased veteran).
  • Field patterns follow conventions already established in the vets-json-schema repository (e.g., ssn as a plain 9-digit string without hyphens, 10-digit phone without formatting).

Files

  • src/schemas/27-2008-schema.json

Notes for reviewer

  • Please ensure you have incremented the version in package.json
  • Please add backend-review-group as a reviewer
  • The usaState enum should be verified for completeness — the artifact summary was truncated before the full list of state codes was visible. Please confirm all 50 states, DC, and any applicable territories are included.
  • The ssn pattern (^\d{9}$) stores Social Security Numbers without hyphens — confirm this is consistent with how downstream consumers (vets-api, vets-website) expect to receive this value.
  • The phone pattern (^\d{10}$) does not account for extensions or international numbers — confirm this is acceptable for the form's use case.
  • Draft-04 is used for consistency with other schemas in this repository; no upgrade to a later draft is assumed.

Pull Requests to update the schema in related repositories

  • vets-api: pending
  • vets-website: pending

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant