Version 1.0.5
Last Modified: 5 April 2013
This specification was published by the W3C Algorithmic Modelling Community Group. It is not a W3C Standard
nor is it on the W3C Standards Track. Please note that under theW3C Community Contributor License Agreement (CLA) there is a limited opt-out and other conditions apply. Learn more about W3C Community and Business Groups.
Requirements
This specification intends to meet the following requirements
- Any constituent type of element in the model
should be able to be freely and independently
composed with any other type of model element,
without restriction: that is, the semantics
of an element should be unrelated to the
ancestors of that element within a model
document
- Any model element should optionally provide one
or more run-time component interfaces, typed by
by reference to an
XML Schemas element, for "use" (in
some implementation-defined manner) by any
number of similarly typed run-time component
interfaces in, possibly, other element
- A model element should be capable of participating
in one or more "finite state machines", such
machines always being, at any point in time, in some
defined "state" and, whenever a defined condition is
satisfied within the machine, a defined, imperatively
executable, process is triggered, causing a transition
to some other, defined, state
- Model elements should optionally be associated with
imperatively executable elements, the bodies of which
should be formed from that of
State Chart Executable Content or
an XProc
step, each thereby constituting a "method" of
that element, and the element associated with
that method becoming that ,method's "this" object
- Any set of model elements may be (possibly nest-ably)
"partitioned" from any other set of elements, such
that the run-time artefacts in one partition or
sub-partition are "insulated" from those in any other
partition or sub-partition
Use Cases
The use cases listed below were created by the Algorithmic
Computing Community Group to illustrate important
applications of algorithmic models.
- Use Case 1: A "Strong AI" project requires
the possession, by the computational entity in question,
of a "psychological model", acquired from sensory input,
underlying which is an algorithmic model, over which are
layered OWL ontologies, representing the structural
portion of the model, and RIF rule-sets, representing the
model's dynamic behaviour
- Use Case 2: A cloud computing installation
Consists of a set of "nodes", each of which belongs to a
"class" determining the computational content of that node
itself consists of an algorithmic model, the composition
of which dictates the nature of the execution undertaken
on that node
Contribution History
| Version Change | Date | Contributor | Comments
|
| 1.0 | 21 February 2013 | Russell Potter | initial creation
|
| 1.0 | → | 1.0.1 | 7 March 2013 | Russell Potter | modified requirements section
|
| 1.0.1 | → | 1.0.2 | 15 March 2013 | Russell Potter | added second use case
|
| 1.0.2 | → | 1.0.3 | 1 April 2013 | Russell Potter | corrected use case spelling error
|
| 1.0.3 | → | 1.0.4 | 2 April 2013 | Russell Potter | re-corrected spelling error
|
| 1.0.4 | → | 1.0.5 | 5 April 2013 | Russell Potter | added componenting requirement
|