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

Class names lacking specificity #27

Open
fjmanion opened this issue May 4, 2018 · 1 comment
Open

Class names lacking specificity #27

fjmanion opened this issue May 4, 2018 · 1 comment

Comments

@fjmanion
Copy link
Member

fjmanion commented May 4, 2018

Many of the class names are not specific enough. For instance 'minimal risk' seems like a kind of risk, but it is actually a class of rule. Hence it should be named 'rule about minimal risk' or minimal risk rule'.

Originally submitted by Neil Otte.

@fjmanion
Copy link
Member Author

fjmanion commented May 4, 2018

We need to have further discussion about at least this specific case. The term 'minimal risk' is a term of art that has very precise meaning to IRB members and regulatory subject matter experts. Part of the goal of this ontology is to express terms in language familiar to the user community. Perhaps we should be using aliases or some other "technique" for this reason. Let's discuss.

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

1 participant