Skip to content
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

examples and suggested values of unit= don’t match #1630

Closed
sydb opened this issue Apr 12, 2017 · 6 comments
Closed

examples and suggested values of unit= don’t match #1630

sydb opened this issue Apr 12, 2017 · 6 comments

Comments

@sydb
Copy link
Member

sydb commented Apr 12, 2017

The “suggested values include” for @unit of att.citing includes the values volume and page. But I just found that there are 11 instances of unit="pp" and 11 instances of unit="vol" on //egXML//biblScope | //egXML//citedRange.

My instinct is that the examples are wrong, the “suggested values include” list is correct, and the examples should just be fixed without further ado.

@lb42
Copy link
Member

lb42 commented Apr 12, 2017

my instinct otoh is that pp and vol.are pretty widely used and recognised in the world of bibliography and that "suggested" shouldnot ean "compulsory"

@sydb
Copy link
Member Author

sydb commented Apr 12, 2017

So your suggestion, then (I hope) is to change the suggested values list to have "pp" and "vol". While I mildly prefer "page" and "volume", I really don’t care much. But I think it is a very bad idea to suggest A and exemplify B. (While TEI is specifically not asserting that use of "page" as opposed to "pp" is cumpulsory for TEI conformance, we are suggesting that “if you want to express that a cited range is measured in pages, you should use "page" so that everyone (pardon the pun) is on the same page”.)

@martindholmes
Copy link
Contributor

I think that once we have propagated a suggested values list, we should think very carefully before undermining it. We should fix the examples to be consistent with our suggested list, unless we can find in the history that our intention was in fact the reverse. There could be Stylesheet implications for changing a suggested valList too.

@lb42
Copy link
Member

lb42 commented Jul 13, 2017

I stand by the assertion that "vol" and "pp" are widely used and appropriate. Is it not possible that they were mistakenly removed from the valList when it was closed ?

@hcayless
Copy link
Member

Council subgroup agrees with @sydb. Nothing prevents TEI users from using 'vol' or 'pp', but we should keep the suggested values simple, and make our examples consistent where practical.

@ebeshero
Copy link
Member

closing with this commit: 9581121

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants