Currently the TEI namespace is attached to the <lg> (//body/lg) element wrapping the other stanzes. This <lg> marks the poem. Why not move the namespace up to the root TEI element as such:
<TEI xmlns="http://www.tei-c.org/ns/1.0">
Currently there is no schema in place. As a start, maybe tei-all could be used to check if the files conform to the TEI in the broadest possible sense:
<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml"
schematypens="http://purl.oclc.org/dsdl/schematron"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
Next step would be to create a customization.
If the processing instructions as above are added to a file and validated (I used the Oxygen XML Editor) and validated there are some errors:
Example validated https://github.com/linhd-postdata/averell-docker/blob/main/corpora/TEI/disco2_1/A.%20Calvo/A.%20Calvo_soneto.xml
Apart from the namespace not being present on the root element, the error concerns the custom attribute stanza_typeon <lg>, e.g. <lg n="4" stanza_type="terceto">.
If you use the generic attribute type it would already be a valid file:
<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml" schematypens="http://relaxng.org/ns/structure/1.0"?>
<?xml-model href="http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng" type="application/xml"
schematypens="http://purl.oclc.org/dsdl/schematron"?>
<TEI xmlns="http://www.tei-c.org/ns/1.0">
<teiHeader>
<fileDesc>
<titleStmt>
<title>Soneto</title>
<author>A. Calvo</author>
</titleStmt>
<extent>
<measure unit="stanza">4</measure>
<measure unit="line">14</measure>
</extent>
<publicationStmt>
<publisher>UNED University</publisher>
<idno>A. Calvo_soneto</idno>
<availability status="free">
<p>The text is freely available.</p>
</availability>
</publicationStmt>
<seriesStmt>
<title>Disco V2.1</title>
</seriesStmt>
<sourceDesc>
<bibl>
<title>Soneto</title>
<author>A. Calvo</author>
</bibl>
</sourceDesc>
</fileDesc>
</teiHeader>
<text>
<front>
<head>Soneto</head>
</front>
<body>
<lg type="poem">
<lg n="1" type="cuarteto">
<l n="1" met="+-+-++-+-+-">Un soneto me manda hacer Elvira</l>
<l n="2" met="--+-++-+-+-">sin saber si soy buen o mal poeta,</l>
<l n="3" met="-++-+-+--+-">porque es niña, inter nos, algo coqueta,</l>
<l n="4" met="--+--+-+-+-">y por tal pequeñeces nunca mira.</l>
</lg>
<lg n="2" type="cuarteto">
<l n="5" met="+-+--+-+-+-">Ella sabe que yo, su amigo, lira</l>
<l n="6" met="+-+-+--+++-">taño o rasco, y al punto así le peta,</l>
<l n="7" met="-----++--+-">y en lugar de pedirme una cuarteta</l>
<l n="8" met="+-+-++-+-+-">un soneto me pide. ¡Qué me admira!</l>
</lg>
<lg n="3" type="terceto">
<l n="9" met="+-+-++-+-+-">Un soneto, Dios mío, lance duro.</l>
<l n="10" met="+-+--+---+-">¿Qué diré que me saque del apuro?</l>
<l n="11" met="+-+--+---+-">¿Qué diré que me libre del aprieto?</l>
</lg>
<lg n="4" type="terceto">
<l n="12" met="+-++-+---+-">Le diré que es hermosa y hechicera,</l>
<l n="13" met="--+--+---+-">y divina y graciosa, y... lo que quiera</l>
<l n="14" met="-+++-+-+-+-">que ya no cabe más en un soneto.</l>
</lg>
</lg>
</body>
</text>
</TEI>
Currently the TEI namespace is attached to the
<lg>(//body/lg) element wrapping the other stanzes. This<lg>marks the poem. Why not move the namespace up to the root TEI element as such:<TEI xmlns="http://www.tei-c.org/ns/1.0">Currently there is no schema in place. As a start, maybe tei-all could be used to check if the files conform to the TEI in the broadest possible sense:
Next step would be to create a customization.
If the processing instructions as above are added to a file and validated (I used the Oxygen XML Editor) and validated there are some errors:
Example validated https://github.com/linhd-postdata/averell-docker/blob/main/corpora/TEI/disco2_1/A.%20Calvo/A.%20Calvo_soneto.xml
Apart from the namespace not being present on the root element, the error concerns the custom attribute
stanza_typeon<lg>, e.g.<lg n="4" stanza_type="terceto">.If you use the generic attribute
typeit would already be a valid file: