<classDecl> in TEI Lex-0 should not be empty

[daliboris]

We use <classDecl> for classification of available dictionaries (for example period, modern, diachronic, biblingual and others).

In the current version of TEI Lex-0 <classDecl> model is empty, <taxonomy> definition is missing.

And corresponding <profileDesc> element is missing too.

[laurentromary]

Shall we go for the whole group: <taxonomy>, <category>, <catDesc>, <classDecl>? (I keep <profileDesc> for the record, but it is somehow obvious).

[xlhrld]

I'd vote to keep all of teiHeader in place for Lex-0. Pruning the metadata section seems like opening a second can of worms alongside the one comprising the lexicographic inventory within body …

[laurentromary]

I would tend to go in the same direction. Any strong opinion against?

[xlhrld]

FTR: We had complaints about missing metadata elements before (#68, #54). There's also #8 which would become a lot easier if we could basically just point to the relevant section in the guidelines (and maybe provide some dictionary-specific best practice advice).

[daliboris]

Just for the record sharing our classification:

    <encodingDesc>
      <classDecl>
        <taxonomy xml:id="taxonomy">
          <category xml:id="taxonomy-dictionary">
            <catDesc xml:lang="cs-cz">slovník</catDesc>
            <catDesc xml:lang="en">dictionary</catDesc>
            <category xml:id="taxonomy-dictionary-modern">
              <catDesc xml:lang="cs-cz">moderní</catDesc>
              <catDesc xml:lang="en">modern</catDesc>
            </category>
            <category xml:id="taxonomy-dictionary-period">
              <catDesc xml:lang="cs-cz">dobový</catDesc>
              <catDesc xml:lang="en">period</catDesc>
            </category>
          </category>
        </taxonomy>
      </classDecl>
    </encodingDesc>
    <profileDesc>
      <textClass>
        <catRef target="#taxonomy-dictionary-modern" />
      </textClass>
    </profileDesc>

[ttasovac]

I feel we should be a little more conservative and a little more didactic. Before we do anything, we need good examples of dictionary metadata to illustrate and compare best practices.

After we've collected, looked at and analyzed the way people record the dictionary metadata, we can decide whether to open up TEI Lex-0 to all of teiHeader. I am skeptical because I think — in the long term — we will do a better service to the community if we say: this is how dictionaries a, b, c and d do this, we encourage this way of doing things... and hence some of our restrictions, than simply referring to the Guidelines.

We can talk about this on Monday during one of the breaks and try to proceed quickly and efficiently.

[ttasovac]

@daliboris This hasn't made it to v0.9.0 but we'll address it in the next release. Also, Boris, I have finally added you to the list of contributors :)