Chronological Thread 

< Chronological >      < Thread >

---

from http://www.cellml.org/public/specification/grouping.html we have :


section 6.2.2 paragraph 2

A model may contain any number of encapsulation hierarchies, as long as
these do not overlap. If more than one hierarchy is explicitly defined,
it may be useful to combine these into a single hierarchy by assigning
all unencapsulated components an anonymous parent component. This
anonymous component could make it easier to check that the hierarchies
do not overlap and do not define any circular relationships between
components.

section 6.4.2 The <relationship_ref> element

4. Proper use of the name attribute

A name attribute must not be defined on a <relationship_ref>
element with a relationship attribute value of "encapsulation". [ A
model must define at most one unnamed encapsulation hierarchy. ]


This latter part - [ A model must define at most one unnamed
encapsulation hierarchy. ] - seems wrong. Encapsulation hierarchies
cannot be named anyway, so mentioning 'unnamed' is redundant, but
according to 6.2.2 we can define as many non-overlapping hierarchies as
we want.

Perhaps it was meant to read - unnamed containment hierarchies - but
section 6.2.4 would suggest you can have as many as you want of either
a particular named group or unnamed group.


cheers
Matt

---

• [cellml-discussion] problem in spec on grouping, Matt Halstead, 08/05/2004
  • [cellml-discussion] problem in spec on grouping, Warren Hedley, 08/05/2004
    • [cellml-discussion] Abacus a Mozilla based mathml editor, Carey Stevens, 08/05/2004

---

Archive powered by MHonArc 2.6.18.