Data Model based on OntoLex TEI Lex0
This describes the common elements of the TEI-Lex0 and OntoLex-Lemon model and proposes a model that can inform the LEXIDMA standard
- Element: TEI
- Children: teiHeader, text
- Mapping to OntoLex: ignored
- Role in EDM: None
- Element: teiHeader
- Children: ?
- Mapping to OntoLex: unclear
- Role in EDM: Should be harmonized with existing metadata in D2.1
- Element: body
- Children: entry
- Role in EDM: None
- Element: entry
- Children: form, sense, cit, xr, usg, etym, gramGrp, entry
- Attributes: type=mainEntry, wordFamily, homonymEntry, relatedEntry, id
- Mapping to OntoLex: Represented by two elements lexicog:Entry ---describes→ ontolex:LexicalEntry types are mapped to a new lexinfo property range. If entry is a child of an entry, it is mapped by lexicog:subcomponent
- Role in EDM: Entry
- Element: form
- Children: lang, orth, gramGrp
- Attributes: id, type=simple, lemma, variant, compound, derivative, inflected, phrase
- Mapping to OntoLex: ontolex:Form, lemma is canonicalForm, inflected/variant is otherForm
- Role in EDM: Lemma, Variant, Inflected
- Element: lang
- Children: none
- Mapping to OntoLex: ontolex:language or tag on string as appropriate
- Role in EDM: Language
- Notes: TEI-Lex0 should probably support normalization to IETF language tags
- Element: orth
- Children: none
- Attributes: type=??? xml:lang
- Mapping to OntoLex: ontolex:writtenRep (type values should probably be mapped to the appropriate form)
- Role in EDM: None?
- Notes: It is not clear what values this can have as a type
- Element: gramGrp and gram
- Children: none
- Attributes: type norm
- Mapping to OntoLex: Various LexInfo properties according to type
- Role in EDM: Not clear, this could cause huge issues for the ELEXIS data model…
- Element: sense
- Children: def, cit, xr, usg, etym, gramGrp, sense
- Attributes: id
- Mapping to OntoLex: If no sense children then to LexicalSense, otherwise to Lexicographic components
- Role in EDM: Sense
- Element: def
- Mapping to OntoLex: skos:definition
- Element: cit
- Attributes: type=example, translation
- Mapping to OntoLex: If example, then use FrAC module, translations can use vartrans module
- Role in EDM: Example, Translation
- Element: usg
- Attributes: type: time, geographic, socioCultural, domain, frequency, attitude, normativity, meaningType, textType, hint
- Mapping to OntoLex: Various lexinfo properties
- Role in EDM: Usage Label (if the EDM has some idea of subtypes??)
- Element: etym
- Attributes: Mapping to OntoLex: lexinfo:etymology (maybe in the future new modules, but the TEI-Lex0 mapping is also undefined at the moment)
- Role in EDM: etymology
- Element: gramGrp/colloc/xr
- Mapping to OntoLex: lexinfo:collocation
- Notes: TEI-Lex0 mapping is weirdly complex, and OntoLex mapping is too simplified
- Role in EDM: Collocation
- Element: xr
- Attributes: Synonymy, hyponymy, hypernymy, meronymy, antonymy, related
- Mapping to OntoLex: various LexInfo properties
- Role in EDM: CrossReference
This is the version mapped more directly to the OntoLex vocabulary
