On 2008 Jan 09, at 14:49, Andrew Miller wrote:
Poul Nielsen wrote:
I think that the best policy is to evolve CellML toward a clean and
simple specification. I don't think that this means that we require a
complete break with previous specifications at each major iteration
if, for example,
I don't think we would need attribute values like public_private or
both, since I think public access should imply private access, similar
to say c++ or Java's use of those terms.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Poul Nielsen
Sent: Sunday, 23 December 2007
Hi all
Another case that illustrates that perhaps the concept of uni-directional
connections may be flawed in a declarative language:
Component A has variables x and y that are both public, but only one
algebraic equation, hence insufficient maths to find values for x and y
(e.g. x+y=5).
Randall Britten wrote:
I don’t think we would need attribute values like “public_private” or
“both”, since I think “public” access should imply “private” access,
similar to say c++ or Java’s use of those terms.
The usage of the words public and private in CellML is conceptually
different
Hi
I am aware of that. I think you may have missed my point though.
This is my suggestion: If we just use public and private, and discard
the concept of directionality, then public variables could be deemed
visible from encapsulated components.
The analogy to c++/Java works for me, since
Randall Britten wrote:
That is a very good point.
Perhaps what is needed is quite different altogether. A component like the
sodium current needs a component to play the role of membrane, and another
component to play the role of m gate and another to play the role of h
gate etc.
I think
-Original Message-
From: [EMAIL PROTECTED] [mailto:cellml-discussion-
[EMAIL PROTECTED] On Behalf Of Andrew Miller
Sent: Thursday, 10 January 2008 4:10 p.m.
I think that this discussion has now forked into two different aspects,
although they are somewhat intermingled.
1)
Hi all
I think the policy depends on the answer to these two questions:
1) In terms of how widely CellML has been adopted worldwide, how does the
current status compare to what we expect in say 6 months, and say a year
from now?
2) How successful have we been in terms of achieving the vision
