Skip to content
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

Use human-readable identifiers for EDF and CVR elements #62

Open
ion-oset opened this issue Aug 30, 2022 · 3 comments
Open

Use human-readable identifiers for EDF and CVR elements #62

ion-oset opened this issue Aug 30, 2022 · 3 comments

Comments

@ion-oset
Copy link

ion-oset commented Aug 30, 2022

It is much easier to verify and debug EDFs if the @ids are human readable and describe the element and context they are in. For the current test cases we don't need a perfect scheme just a reasonably well-defined one.

Discussion of the details will be ongoing at Human-readable identifiers in NIST documents.

@trustthevote
Copy link
Member

Heck yes.

Cliff and I had a schema for this a while back, where there was a human readable that was usually but not guaranteed to be unique with an EDF, appended with an ordinal to be unique.

As I recall contests were like contest-mayor, candidates were like candidate-spacely-contest-mayor and candidate-writein-1-contest-spaceport-board; and question-helium-initiative etc. The ballot section IDs would be directly derived from them like selection-candidate-spacely-contest-mayor and selection-question-helium-initiative-yes

In a later phase I want a generation tools to follow some rubric roughly like this, but for now, the yucky IDs are what we've got to work with on a tight schedule.

@ion-oset
Copy link
Author

@trustthevote to be clear: this ticket isn't tied to the current milestones, and we're not trying to solve this before the tight schedule is done. It's here so we can track on it going forward, and because it's come up in BallotLab debugging.

Fwiw we're going to be collecting ideas for that scheme/algorithm at the discussion I linked in the top post.

@ion-oset
Copy link
Author

ion-oset commented Sep 1, 2022

@cwulfman I've realized there's potentially two different issues here.

  1. A general ask to come up with an algorithm or scheme for identifiers (which is what I was posting on based on our recent conversations). That has no immediate milestone or deadline. It might take some care to get corner cases right to our satisfaction, but I think the ones that have been described here and elsewhere are trending towards consensus.
  2. A specific fix to address the needs of a test ballot cited in BallotLab #86.

Do you think it makes sense to split 2 into a separate ticket or is it good enough as it is?

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

No branches or pull requests

2 participants