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

Conversion between types - is ABIF the base for all conversions? #2

Open
masiarek opened this issue Aug 21, 2023 · 2 comments
Open

Comments

@masiarek
Copy link

masiarek commented Aug 21, 2023

.

@masiarek
Copy link
Author

masiarek commented Aug 21, 2023

conversions between formats - do we need to convert first to ABIF - or we plan direct conversions between formats?

Illustration - 3 Candidates and 2 ballot

Columns:
A, B, C
5, 3, 1
4, 2, 5

ABIF:
A/5, B/3, C/1
A/4, B/2, C5

Format "two enter characters" separate the next ballot
A = 5
B = 3
C = 1

A = 4
B = 2
C = 5

@masiarek masiarek changed the title Please activate discussion link Conversion between types - is ABIF the base for all conversions? Aug 22, 2023
@robla
Copy link
Contributor

robla commented Aug 22, 2023

The ABIF tool is uses an internal JSON model as its conversion format. That format: ".jabmod". ".jabmod" takes its letters from the following:

  • "J" is for "json"
  • "ab" is for "abif"
  • "mod" is for "model"

The idea behind converting to/from .jabmod is to make it so that programmers who are more comfortble building internal data structures can dump/convert to .jabmod, rather than having to serialize the output in .abif format (and write a new parser).

.jabmod isn't well specified yet, unfortunately. I'm hoping to define the model as I write a tool that converts .abif to all sorts of other formats. Does that make sense?

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