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

Braille Code Metadata: do we need a dedicated field for the braille code revision? #284

Open
bertfrees opened this issue Oct 8, 2024 · 1 comment
Labels
Topic - metadata Issue with the package document metadata

Comments

@bertfrees
Copy link
Member

There are some examples of entries in the list that have a year in them, e.g. Danish codes have a "1993" and a "2022" version. In Liblouis (on which the initial list is based), we decided to keep separate tables for some of the older revisions, such as the 1993 version of Danish braille, because they are still in use, and we didn't want to force everyone to use the 2022 revision of the code right away. There are however potentially much more braille code revisions that could be included in the list. Liblouis is a braille translation software that doesn't need to support every braille code that ever existed. But it could be a different story for eBraille: it is a file format that could potentially be used for archiving.

@bertfrees bertfrees added the Topic - metadata Issue with the package document metadata label Oct 8, 2024
@bertfrees
Copy link
Member Author

With "field" I mean part of the metadata term, like grade and specialization are also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Topic - metadata Issue with the package document metadata
Projects
None yet
Development

No branches or pull requests

1 participant