- a) the human action of painting, digital or not,
- b) the digital artifacts collectively named 'Paint' (software) and 'a Painting' (data) that can be combined and 'activated' to allow a child to paint with a laptop,
- c) the design-level designation of the time intervals in which a child is painting by means of the 'Paint' software as the time in which the child is 'Painting' (on 'a Painting', no less),
- d) the digital states that occur on one or more communicating laptops during the largest connected interval of time containing some fixed time ('now') in which one or more children are Painting.
for Croquet folks: alternately, the versions defined under the possibility of the pseudo-temporal environment governing one session of Painting?
- Usage: In these terms, we might observe two children who are synchronously or asynchronously collaborating in the activity of painting by Painting together on a shared Painting by means of the Activity named Paint, ultimately producing zero or more related paintings.
- Activity instance
- (static sense): a specific Activity of sense (b)
- (dynamic sense): A sited collection of objects, represented by one DBus object but in reality a heterogenous collection, with which a child interacts. Example: the DBus object, file system resources (see 'island', below), processes (i.e. kernel tasks), network resources, &etc. that together make up the whole of (a running Paint Activity and the Painting that it is manipulating).
- Usage: A specific Painting (static sense) will be manipulated into a new Painting (static sense) during some specific instance of the Activity of Painting. That specific 'program run' is an 'Activity instance' in the dynamic sense.