Open berndmoos opened 3 months ago
@Herrner (who knoweth things): if I introduce an optional attribute in the schema, COMA will read it and write it, it just won't be visible to the user. Right?
Example:
<Transcription theNewAttribute="theNewValue">
I guess so, but let me have a look first...
When looking at the code, I'm wondering whether you would have to add anything to the Schema at all, but better do so. I hardly remember anything, but COMA builds the DOM with a SaxBuilder and writes it using JDOM. Very confusing, all in all.
I just added a new attribute to a transcription, changed stuff with the transcription in COMA and wrote the file back, and the attribute survived, so...
I need the schema because I want other people to write COMA XML outside COMA. I will add surviving optional attributes then for a start. Using a SAXBuilder for reading does not mean that no (J)DOM comes out of it afaik.
I will also put the schema inside GIT (it is not there, or is it?).
The very big thing: changes, additions for a better, stronger COMA, such as
- Metadata for Speakers in Communications
- Multilingual metadata
- Other transcription formats, e.g. FLK, EAF, ISO/TEI
All of these (3.) are very much relevant for INEL.
All of these (3.) are very much relevant for INEL.
Duly noted. But this issue needs a premium sponsor - I am sort of working on it.
There's three things:
The second point is relevant for TGDP.