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

[Question] Schema Definition for ComponentType #173

Open
thorstenhater opened this issue Sep 16, 2021 · 2 comments
Open

[Question] Schema Definition for ComponentType #173

thorstenhater opened this issue Sep 16, 2021 · 2 comments
Assignees
Labels
T: question Type: question

Comments

@thorstenhater
Copy link

In the NeuroML XSD schema definition for ComponentType there is this line

<xs:element name="Property" type="LEMS_Property" minOccurs="0" maxOccurs="unbounded"/>

which represents a potential conflict with the complex type Property. Is this problematic?

@thorstenhater thorstenhater added the T: question Type: question label Sep 16, 2021
@thorstenhater thorstenhater changed the title [Question] Schema [Question] Schema Definition for ComponentType Sep 16, 2021
@pgleeson
Copy link
Member

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.

@pgleeson
Copy link
Member

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:

https://github.com/OpenSourceBrain/SmithEtAl2013-L23DendriticSpikes/blob/master/NeuroML2/kca.channel.nml

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T: question Type: question
Projects
Status: 🔖 Ready
Development

No branches or pull requests

3 participants