Matt wrote:
> Sure. I replied to that earlier thread last night.
>
I haven't seen your post on the list, so I guess it got lost somewhere
(the mailman has been delaying my messages for rather random periods of
time recently, so I am guessing there is some bottleneck that could also
be timing
Issue: #2: Graph API: Expand set of glpyhs, and fix naming, Topic: UI, Status:
pending, Importance: Medium, Classification: Bug
Issue URL: http://cellml.org/specifications/specissues/2
---
Description:
---
Hi all,
There have been a number of issues relating to various CellML
specifications which have been discussed recently, and many of them
cannot be immediately acted upon (due to the need to get community
consensus, or lack of time in the short term). To ensure that such
issues are not forgott
Hi all,
The second release candidate for CellML API, version 1.0, has been
released. If you would like to ensure that your application works with
the CellML API 1.0 release, please test against the release candidate.
Once a reasonable amount of time has elapsed, and no problems with the
releas
Hi all,
The second release candidate for PCEnv, version 0.1, has been
released. Information about the released files is available at:
http://www.cellml.org/tools/pcenv/pcenv-releases/physiome-cellml-environment/releases/0.1rc2
This release candidate has been designed so it will work with the
r
David Nickerson wrote:
> Andrew Miller wrote:
>
>> David Nickerson wrote:
>>
>>> I just grabbed the CellML API 1.0rc1 and found that it does not have a
>>> configure file. The README that comes with the distribution says to
>>> follow the instructions in the INSTALL which talk about the s
>From the meeting minutes <<
http://www.cellml.org/meeting_minutes/13.11.2006/>> we have:
"There was discussion about what should be on the CellML roadmap.
Peter noted that Matt was also keen on seeing a roadmap get created.
Alan thought that curation information should be a high priority on
the r
