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

SSSOM output #33

Open
cbizon opened this issue Jan 19, 2022 · 1 comment · May be fixed by #328
Open

SSSOM output #33

cbizon opened this issue Jan 19, 2022 · 1 comment · May be fixed by #328

Comments

@cbizon
Copy link
Contributor

cbizon commented Jan 19, 2022

Instead of a special file format, we should perhaps be writing out SSSOM file.

Is that going to make the files even more gigantic? Probably? Is that a problem?

@gaurav
Copy link
Collaborator

gaurav commented Nov 27, 2022

We currently have SSSOM output working as part of Babel Validator, but we could modify Babel to directly produce SSSOM instead of the custom JSON format. The main question is the urgency: do we want to try to get this done in Jan-Mar 2023, or can it wait until later that year?

This will need to be developed in sync with TranslatorSRI/NodeNormalization#111 (PR TranslatorSRI/NodeNormalization#145).

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

Successfully merging a pull request may close this issue.

2 participants