CellMLUML

_UML_

The Unified Modeling Language (UML) is a framework for describing a set of models that capture the functional and structural semantics of any complex information system. UML defines the following models for representing such systems:

  1. A use case model that states the requirements of the user
  2. A class model that captures the static information structure of objects
  3. A state model that describes the dynamic behavior of objects
  4. An activity implementation model that describes work unit actions
  5. An interaction model that models scenarios and message flows

6. A deployment model that describes how software subsystems are allocated to actual hardware components

This was stolen from an RDF-Schema/UML "document,":http://www.w3.org/TR/1998/NOTE-rdf-uml-19980804/ which is a useful read.

_What are we attempting to do_

Both 1 and 2 are relevant to the current state of our thoughts. I.e. we need to address the use-cases/requirements for the language and we can capture the static model structure.

We want to describe the structure of the language without describing the structures in the current markup language syntax, i.e. not using things such as containment, but instead association relations. As we get closer to particular implementations of the language, then we should resolve the associations into better defined constructs. "This page":http://www.cs.sjsu.edu/faculty/eobaid/cs151/ch2/uml.html gives a nice summary of this thinking.