Election-Tech-Initiative / Election-Tech-Initiative/electionguard
✨ Create a definitive sample manifest to avoid confusion and illustrate all important formatting requirements
- Dominant language
- Python
- Stars
- 872
- Forks
- 131
- PR merge metrics
- No merged PRs in 30d
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Suggestion
There are currently a variety of sample election manifests used for different purposes (development, testing, and full, etc.). However none of them are fully comprehensive and only a subset have any internationalization support.
We should instead have a definitive, comprehensive sample manifest that illustrates sufficient electoral complexity (see [our Hamilton County example here](https://www.electionguard.vote/concepts/Manifest_Building/)), [adheres to the proposed NIST](https://pages.nist.gov/ElectionResultsReporting/) and [Civics data format](https://developers.google.com/civics-data/guides) standards, and exercises a subset of relevant internationalization convetnions (specifically [UTF-8 _special characters_](https://www.utf8-chartable.de/) and a [right-to-left language](https://www.andiamo.co.uk/resources/right-to-left-languages/)
### Possible Implementation
_No response_
### Anything else?
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.