Separate Dynamics and ConnectionRule Components into different root tags
NineML-Committee opened this issue · comments
The committee agreed that the different types of components should use different root tags.
In splitting the spec into Structure and Property layers (see #41) I have found that we could probably do without the old Component elements, so how do you guys feel if we drop the "Class" suffix and split ComponentClass into Dynamics, ConnectionRule, etc...
ok with me
Fine with me too
On 16 April 2015 at 13:55, Andrew Davison notifications@github.com wrote:
ok with me
—
Reply to this email directly or view it on GitHub
#94 (comment).
Alex Cope
Research Associate
Behavioural and Evolutionary Theory Lab
Department of Computer Science, University of Sheffield
www.alexcope.co.uk
No objection to this.
P
On 16 April 2015 at 13:58, Alex Cope notifications@github.com wrote:
Fine with me too
On 16 April 2015 at 13:55, Andrew Davison notifications@github.com
wrote:ok with me
—
Reply to this email directly or view it on GitHub
#94 (comment).Alex Cope
Research Associate
Behavioural and Evolutionary Theory Lab
Department of Computer Science, University of Sheffield
www.alexcope.co.uk—
Reply to this email directly or view it on GitHub
#94 (comment).
Dr Paul Richmond (Research Fellow) - University of Sheffield
http://www.paulrichmond.staff.shef.ac.uk
p.richmond@sheffield.ac.uk
Department of Computer Science http://www.sheffield.ac.uk/dcs
Sheffield NVIDIA CUDA Research Centre
http://gpucomputing.sites.sheffield.ac.uk/
Advanced Computing Research Centre http://www.acrc.com
Sounds good to me.