> > But it turns out that things like<msItemStruct class="#nrss_type_sermon
> > #nrss_author_ecclesial">  are invalid because of the @class value.
> Are you sure? Looking at the definition of this attribute, I see that it 
> is defined (like other such attributes) in the ODD as
> >  <datatype minOccurs="1" maxOccurs="unbounded">
> >         <ref xmlns=""
> >       </datatype>

Well, our TEI P5 v. clean schema doesn't like it - also :
defined it directly (so, the attribute class does not seem to be in an
attribute class) and without rng:group:

<rng:element name="msItemStruct">
  <rng:attribute name="class">
   <rng:ref name="data.code"/>

> so its value *is* repeatable.
Hmm, only if this was recently changed and the web version is not current.

Thanks for the help as below; I guess we can then safely point to taxonomy,
and I can - for now - fix our schema to allow repeatable data.code.


> > - the example gives the @class without the #, which is dangerously
> > misleading - for a while there we thought, well, data.code for some
> > does not use #, so we here happily writing @class="nrss_type_sermon
> > nrss_author_ecclesial", which does validate, but is probably nonsense.
> > So, would this be an error or two in the Guidelines?
> Yes, this is an error. There should be a # on that value!
> >
> > And a related question: we actually thought to link the @class values to
> > taxonomy, but reading the definition, I see that it is meant only for
> > linking to textClass.
> That is clearly wrong. Well spotted!
> I think this is a fixable bug : obviously @class should point to one or 
> more <category> elements within a <taxonomy>, or to one or more 
> classification entries in some external thesaurus.
> > But
> > defines it
> > <textClass>  (text classification) groups information which describes
> > nature or topic of a text in terms of a standard classification scheme,
> > thesaurus, etc.
> > I would then imagine that each text gets only one textClass; in which
> > how could you have more than one value for @class, and what is the point
> > having @class anyway, given that all msDesc belong to the same<TEI>?
> > except for the borderline case where you would have a teiCorpus of
> > manuscripts).
> >
> > Any illumination would be much appreciated!
> >
> > Best,
> > Tomaž