First login?
Lost password?
 
 
cellml-tools-developers AT lists.cellml.org 
A list for the developers of CellML tools

Text archives Help


[cellml-dev] CellML API - GetAlternateVersion from the Model interface


Chronological Thread 
  • From: alan.garny at dpag.ox.ac.uk (Alan Garny)
  • Subject: [cellml-dev] CellML API - GetAlternateVersion from the Model interface
  • Date: Fri, 25 Sep 2009 11:45:01 +0100
> -----Original Message-----
> From: cellml-tools-developers-bounces at cellml.org [mailto:cellml-tools-
> developers-bounces at cellml.org] On Behalf Of David Nickerson
>
> I know it doesn't help and the bug you see should be fixed, but why
> are you creating CellML 1.0 models in the first place? Doesn't it make
> sense to always create CellML 1.1 models regardless of there being
> imports or not? As Andrew pointed out somewhere recently, technically
> it is invalid CellML 1.1 to import a CellML 1.0 component (something
> I'd never considered and am glad the tools don't actually stop such
> models working), so we really want to be doing everything we can to
> get model authors creating CellML 1.1 models. You'd imagine then that
> OpenCell should have a "Save as..." option that lets you choose to
> flatten the model and export a CellML 1.0 model document (probably
> making use of Johnathan's model flattening code). [perhaps such an
> option already exists?]
>
> Just thinking out loud here...and maybe I have completely missed the
> point of what you are doing...

I clearly overlooked the discussion about CellML 1.1 importing CellML 1.0
components being technically invalid. As you said, it's good that current
tools nonetheless allow such a thing. In fact, I hope it's going to remain
that way, since most models are CellML 1.0 models.

Anyway, regarding what I am trying to do... Well, I took the view that if
the model is truly CellML 1.0, then it should be saved as such, and only
saved as a CellML 1.1 model if there are import statements. My reasoning
behind this is that, as we know, most CellML tools are 'only' CellML 1.0
capable, so if someone creates a pure CellML 1.0 model in OpenCell and end
up with a 'CellML 1.1' model, then this might be a problem with other CellML
tools. This is the reason I would like to stick to what I am trying to do
with my COR-like view. Hope it makes sense...

Alan



Archive powered by MHonArc 2.6.18.

Top of page