-
Notifications
You must be signed in to change notification settings - Fork 24
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
[Question] Schema Definition for ComponentType #173
Comments
It shouldn't. That's why its type is named LEMS_Property. Most of them match obviously, but as far as the schema is concerned it's pointing to diferent complex type for property as used in the lems language. |
Note: the reason we have these lems types here in the nml schema (it would have been best to keep them elsewhere, just in the lems schema), is that we want to be able to validate nml files which have basic new component type definitions embedded, using the one nml schema, e.g. this is valid neuroml: It would have caused problems if we weren't able to validate channel files like that using nml validator, so that's why a subset of LEMS like |
In the NeuroML XSD schema definition for
ComponentType
there is this linewhich represents a potential conflict with the complex type
Property
. Is this problematic?The text was updated successfully, but these errors were encountered: