-
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
tech/@type should not have a closed value set #1662
Comments
While I note that |
Agreed. |
It should be a member of att.typed too. |
the class membership regularization is part of #386 |
Per #1662 change the value list of the type attribute of <tech> to 'semi'.
Can't it just be added to the class? That shouldn't affect anything, surely? |
It’s not hard, @martindholmes, but you have to both add it to the class and then override it and then test that it all went OK. Since (in theory) we are supposed to enter the refrigerator tonight, and I’m working on a couple of other things, I thought it best to keep it simple for now, knowing it would be hit in that other ticket anyway. |
Sorry, didn't realize the freeze as so soon. |
No worries! (Our fault for waiting until the last minute … :-) |
The
<tech>
element has a closed value list for@type
:light|sound|prop|block
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tech.html
This is a very limited list, and working on a current project we're finding other values we need to use, such as "video", "house" and more.
It seems unreasonable for this to be a closed value list, especially as performance norms and technologies are in constant change. Could we make it suggested values instead? This would not invalidate any existing documents.
The text was updated successfully, but these errors were encountered: