You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 <ComponentType> <Dynamics> <DerivedVariable> are in the nml schema...
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: