....

> - "Neither <msItem> nor <msItemStruct> may contain untagged running 
> text, although <msItem> may contain one or more <p> elements as an 
> unstructured alternative to the possible components listed above."
> 
> but also <msItemStruct> can contain, alternatively, one or more model.pLike.

This is not the least weird thing about it. However, I've not changed it but
simply expanded the discussion of its model to specify this possibility.


> 
> - the examples with <expan> must be checked to see whether <ex> needs to 
> be used instead.

absolutely: these examples are all Wrong by the new rules. Modified accordingly.

> 
> - "If it is desired to retain the form of the author's name as given in 
> the manuscript, this may be tagged as a distinct <name> element, nested 
> within the <author> element with the normalized form of the name on its 
> reg attribute. Alternatively, the normalized form of the name may be 
> supplied as the value of a reg attribute on the <author> element."
> 
> The last sentence should be taken out.
> 

... and shot. There is no @reg attribute on author, nor should there be since it
is defined as containing a regularized form of the name. And there is no @reg
attribute on <name> either! 


> - Specs for <textLang>: in the description for the attribute 
> @mainLang/@otherLangs a link to the IANA Language Subtag registry could 
> be added (http://www.iana.org/assignments/language-subtag-registry).
> 
The whole discussion of textLang attribute values is Wrong. I have tidied it up
considerably. I have not however checked to see if the reference you give is the
same thing as BCP47, which is what we seem to have decided we should be citing.


> - if the work on stemmata will be included in the guidelines, a 
> reference to that could be included under the 'Filiation' section in 
> this chapter.

Duly noted. 

> 
> - I am not sure the example with the Old Church Slavonic language is 
> appropriate since there is already a IANA subtag - Cyrs - for Old Church 
> Slavonic written in Cyrillic. Same is valid for Russian and Greek.


see above!

> 
> - "<measure type="leaves" unit="count" quantity="10">10 Bl.</measure>"
> 
> I think this is wrong. 'count' cannot be a unit. The leaf is the unit here.
> 

yes. this looks silly. I have changed to type=composition and unit=leaf
Don't ask me what "Bl." means though.

> - I understand why the attribute @scribe for <handNote> has as value 
> data.name, since most of the times we don't know much about scribes 
> besides what their hand witnesses, but when we do, I think this 
> attribute could be used as pointer to a person element. How could we 
> allow for this second use?
> The same attribute name (@scribe) has data type data.code for <hand>. 
> [but see below]
> 
> 

Changes to hand/List etc. and also the new class objEventLike I will discuss in
a separate message. When I've had a chance to try implementing your seductive
notions...

> 
> - under the surrogates section a reference could be added to the new 
> digital facsimile material.
> 

Added.