-
Notifications
You must be signed in to change notification settings - Fork 11
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
Suggestion: require definition for schema extension #434
Comments
Some extensions might be apparently clear, e.g. Vehicle/Motorcycle. For an extension containing non-obvious term maybe we can ask people to group it with a Description/ tag. |
@monique2208 We could modify the validator so that the warning message will include an exhortation to please make sure that the overall annotation for this event has a description? |
@IanCa @happy5214 what warning is raised when a tag is extended and what message is output in the respective Python and JavaScript validators? |
Valid extension warning: Invalid extension(reusing term): (Non extension allowed) |
Using the three tag examples above:
|
All terms in the HED schema are defined. When a user extends the schema, a definition should also be required. This could also improve HED validation. Currently the HED validator throws a warning when the schema is extended by the user, to check if this was intended. If a definition is required, it can be checked for and there does not need to be an warning in case there is a definition, and unintended extension can be identified better.
The text was updated successfully, but these errors were encountered: