-
Notifications
You must be signed in to change notification settings - Fork 7
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
TEI: DTABf vs DFG-Anwendungsprofil for manuscripts #61
Comments
@sebastian-meyer you are the first author of the DFG TEI Anwendungsprofil for manuscripts – could you please enlighten us to what extent DFG Viewer already supports or is planned to support TEI as input, and what role the profile currently has in the field (esp. compared to DTA-Basisformat)? |
The DFG Viewer (and its application profile) supports TEI as an descriptive metadata format for medieval manuscripts. So essentially you can use TEI(-Header) as an alternative to MODS. This was specified in cooperation with the DFG-funded manuscript centers in Leipzig, Munich and Wolfenbüttel. The DFG Viewer doesn't support TEI(-Body) as a full text format, yet. But we are working on TEI support in Kitodo.Presentation, so adding this to the DFG Viewer as well will be no big deal. |
I see. And how does the
Understood. So we will soon have a TEI use-case on the Presentation/Viewer input side in addition to the aspired download option on the output side which this repo tries to provide. But then the question of the concrete and formal TEI profile becomes even more important (as you must have a definition of what the program must be able to render). So again, do we rely on DTABf, or is it going to be something independent? |
Is there an agreement/compliance relation between DTABf and DFG-Anwendungsprofil?
If not, do we support one or both (configurably) or a compromise?
The text was updated successfully, but these errors were encountered: