danbalogh
commented
2 months ago Thanks, I have not heard this before. I'm very happy about lifting the part about using n to identify the repository. As for the filenames, I think it would be better to keep them systematic and use the full prefix all the time, perhaps also the .xml extension. That way there is, I think, a better chance of interpreting the files if someone else comes across them years from now and does not necessarily have access to your processing. If you disagree with that and say that it is technically not a problem, then I accept that, but even then, I would prefer to have just a single "legitimate" way to encode such references. I don't think it's good to have a guide that says "you can do A, B, C or D and it doesn't matter which, so just pick whichever you like at the moment".
So if you are sure that using the full filename (DHARMA_INSPallava00001.xml) is not better practice or more more future-proof in any way than the others, then let's pick the simplest form (INSPallava00001) as the only approved solution; otherwise, let's use the full filename and make the schema flag anything else as an error instead of processing it to make it work.
Whichever is chosen, the schema may need some alterations. At the moment, @n still comes up in Oxygen as a permitted attribute for <ref>, and I think there are no other circumstances in which one would want an n on a ref. So that can be discarded, and the existing instances of n on ref can be deleted from the files. For ref, I also get a suggestion list consisting of the filenames in the same folder as the present file, which I like, since most of my crossreferences are to my own subcorpus. But if we enforce a short reference instead of the full filename, then this needs to be changed.
michaelnmmeyer
arlogriffiths
ekobastiawan
manufrancis
chhomkunthea
salomepichon
ryosukefurui
A minor remark I am not sure I made: when referring to inscriptions with
<ref>(EGD §10.4.6.Referring to inscriptions in the DHARMABase), the use of@nfor indicating a repository is not needed (because all texts share a single namespace), and adding the.xmlextension is also unnecessary.Thus
<ref n="tfa-pallava-epigraphy" target="INSPallava00001.xml">Pallava 1</ref>can be written
<ref target="INSPallava00001">Pallava 1</ref>Internally, all variations
DHARMA_INSPallava00001,DHARMA_INSPallava00001.xml, andINSPallava00001,INSPallava00001.xmlare made to point to https://dharmalekha.info/texts/INSPallava00001.