Inconsistent use of Child(ren)

[borismarin]

In the current core component definitions, there are ComponentTypes which use Child for optional sub elements (e.g. notes in here, parent here).

As described in the LEMS paper, Child means one and only one sub-component of the appropriate type must be present. So, the correct construct would be Children, with the max attribute specified where appropriate (e.g. segment can only have zero or one parent).

[sanjayankur31]

Hi @borismarin ---I've just run into this while adding some more doc pages. Do you have a list of these perhaps that we can use to fix the files? Also, how does one mention a child element in the XSD file? Do we use minOccurs=1, and maxOccurs=1? Since the libNeuroML python bindings are generated from the XSD file, the XSD file also needs to be corrected. At the moment, a child element like spikeThresh takes a list in libNeuroML, which is confusing.

[borismarin]

Hello @sanjayankur31 . Good to know that someone is looking into these "legacy" issues! Unfortunately, I haven't touched the code for a long time (last time circa 2015, apparently...), so I am afraid there is no up to date list of problematic cases; re lists and number restrictions in XSD, I recall hitting a wall with Jaxb (at least with the version used back then), which seems to be documented here and might be relevant to your question.