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

Text archives Help


Re: [[cellml-dev] ] libCellML handling of non-valid CellML - discussion request


Chronological Thread 
  • From: David Nickerson <david.nickerson AT gmail.com>
  • To: cellml-tools-developers AT lists.cellml.org
  • Subject: Re: [[cellml-dev] ] libCellML handling of non-valid CellML - discussion request
  • Date: Fri, 16 Jan 2015 13:02:43 +1300
> Adding my two-cents worth of confusion, is not a `connection` part of a
> valid CellML model and hence they should be exposed in the API? Connections
> are certainly specified in http://www.cellml.org/specifications/cellml_1.1,
> although this document does mix up CellML's abstract model and its XML
> serialisation. Is there a separate CellML Abstract Model document that
> doesn't have connections as part of it?

Thanks Dave. The hope, at least from my point of view, was that the
libCellML object model would be that abstract model description.
Certainly from my own work, I have never seen a need for a connection
object being exposed in external API.

This is exactly why it is important for the core object model and
associated methods to be discussed in an open manner with the
community. The experiences of application developers should be used to
construct a well informed initial object model description that
provides an ideal starting point for implementation rather than trying
to anticipate potential use-cases that might never come up in actual
usage. As per step 1 in milestone 0 of the libCellML Roadmap
(http://libcellml.readthedocs.org/en/latest/roadmap.html).


Cheers,
Andre.

Archive powered by MHonArc 2.6.18.

Top of page