Lou

If you want to further restrict a TEI datatype, why not just define a new dataSpec? I suspect that the logic of combining a restriction with a predefined TEI datatype...

The spec doesn't actually say you CAN use @restriction with @key, though I agree it doesn't forbid it as firmly as it forbids using a child dataFacet with @key. Since...

If however the intent is that only one altIdent should be permitted, the content model should reflect this. Or there should be a schematron constraint to that effect.

Thanks James. None of these options will make your resulting document valid against TEI All, of course, so this feature also raises a conformance problem; I suppose if you adopt...

Yes, I agree. On conformance, see further thoughts at https://foxglove.hypotheses.org/522 Comments welcome there, or here.

I am comfortable with the idea that any use of altIdent leads to nonconformance, for most definitions of non-conformance that we might come up with. And your use case is...

According to 23.1.2, the renamed elements should be in a different namespace. It also says the TEI "provides a systematic set of renamings....[which] all use a language-specific namespace". So this...

Yes, as noted on issue https://github.com/TEIC/TEI/issues/1613, in an ideal world, multiple altIdents would be cool. But be careful: the current stylesheets need a lot of work to handle that.

We seem to be agreeing that multiple altIdents should be allowed; less convinced that they should result in multiple declarations in the generated schema, i.e. my example above will result...

FWIW, I opened your T2 in oXygen and did the built in odd to html conversion without problem.