The version of the schema or format is also part of the schema location url/name. Could enforce the value with, in this case, default="1.0". For now one language is allowed, the main language this lexicon is about (this denotes the language of the lexical-unit, citation etc.). ISO 639-3 3 letter code is assumed but not enforced (the type is xs:string) A free form textual description of and information on the lexicon. The version of the lexicon itself, not the format version. lexical-unit (LIFT terminology, a lexicon interchange format) instead of lemma / headword etc. Assumes language is the "main" language. If not present, a default value is assumed. This element could/should be linked to a controlled vocabulary (or a "range" in lift). Simple variant field, assumes the same morph-type and language as the lexical-unit Not fully supported yet. Provides a way to add custom fields to the lexicon. An attribute to explicitely set the order for entries with the same lexical-unit (e.g. homonyms). A reference to a "parent" unit. Fields are "inherited" unless redefined. Grammatical category or part of speech (in LIFT part of "grammatical-info"). This element should/could be linked to a controlled vocabulary or "range". The sense number. Glosses can be specified in multiple languages. Definitions can be specfied in multiple languages. Phonetic representations can be specfied in multiple languages or systems. A type consisting of a string value and a language attribute. An example element (not fully implemented yet). A literature reference or similar A reference to an annotation or (fragment of) a media file. This is currently of type string (free form). Alternatives could be a 3 letter code, or xs:language, or a language-id reference (as in EAF). For adding user defined fields to lexical entries. Not supported yet. The type of the name of the fields is at the moment defined as xs:NCName so that in a conversion it can be used as an XML element name. Specification of custom fields. A specification for a single custom field. The name of the field. (The type is NCName so that in a conversion it can become an xml element.) Determines on what level(s) this field can occur. Configuration of fields. Configuration of a single field. The name of one of the standard or custom fields. The preferred display label for the field (a hint for user interfaces). A reference to the identifier or name of a controlled vocabulary or range. It is still to be decided where the ranges are stored and how to link to the definitions.