Open jonathanrobie opened 2 years ago
One traditional answer to this would be to use namespaces, e.g.
<c c:english="Asahel" c:mandarin="亚撒黑" sil:english="Asahel" />
Should we bite the bullet and use namespaces? So far, we don't do this for anything else, and it does add complexity, e.g. people's path expressions may not match for reasons they do not understand.
If we don't use namespaces, and have a small number of glosses, we can handle it using carefully chosen names. Less clean, but less confusing for some programmers:
<c english="Asahel" mandarin="亚撒黑" sil="Asahel" sdbh="....."/>
Berean glosses could be identified as berean="..."
. For the GNT, we have been using them as a primary gloss. Should we allow ourselves to say gloss="...."
?
We have several sources of glosses, and they have different advantages and purposes. We need simple attribute names that support the glosses we are using:
Obviously, glosses in other languages may also become a factor.
I don't particularly like attribute names like
cherith-english
in the following:So we need a naming convention that gives us flexibility while keeping this simple. I don't think we need the attribute name to attribute the source, we can do that in documentation and copyright / license statements.
Any suggestions?