-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Harmonize reason attributes #2580
Comments
Good point — it is probably better if those five cases of It is worth reviewing (my interpretation of) the semantics of these two datatypes. The teidata.word datatype was originally intended as nothing more than a way to provide a “string without funny characters that are likely to be problematic when parsing” sort of datatype, roughly analogous to (but with not quite the same restrictions as) the Nmtoken of XML 4th edition. Because the words “string”, “text”, and “token” were already taken, it was named (poorly, in retrospect) “word”. However, within a few years the meaning morphed into more of “single token that has its own semantics” sorta thing. In any case, its meaning is quite distinct from teidata.enumeration, which represents the exact same syntax, but which means “there is (or should be) a controlled vocabulary for this”.
In some cases the Guidelines do not actually provide a controlled vocabulary at all. I think the semantics of these cases is “you, the customizer writing the ODD customization for a TEI project, should provide a controlled vocabulary for this (but we’re not going to provide any helpful suggestions)”. Of the 169 cases of teidata.enumerated in the Guidelines,
Given that the But the other question to ponder is whether or not |
@sydb Thanks for sharing your thoughts. Based on your explanation I agree that |
@reason
is available for the elementsgap
,secl
,supplied
,surplus
, andunclear
.Mostly they are based on
teidata.word
, however the first and the last one take the long way usingteidata.enumerated
instead.Is there a reason for this? I do not see any, so maybe it would be good to have all
@reason
attributes modeled in the same way.The text was updated successfully, but these errors were encountered: