P2P Computing - Architecture

This is meant to illustrate  concept that users should be able to choose nodes that will perform peer to peer computing. These nodes may be participants in a project. In reality, this choice may be a bit more difficult, and may depend on what is available at the best price. In addition, this illustration shows a geographical distribution of nodes. In addition, it may be useful to specify HPC variables of the compute architecture.

REA model applied to part-whole relation (try 2)

REA model applied to part-whole relation

Simple Part Whole Class Diagram (checking with Protege)

I guess I made the mistake of not putting Faults for the wheel, motor, headlight, and  Car as subclasses of fault. In addition note that wheel points to wheel_of_car, motor points to motor_of_car,  and headlight points to headlight of car.

Simple Part Whole Relations Diagram

A class diagram above, and a property diagram below of simple-part-whole relations v1.3 (with personal extensions guessed from the document).
http://www.w3.org/2001/sw/BestPractices/OEP/SimplePartWhole/simple-part-whole-relations-v1.3.html

Yes, REA with prov and wn namespaces!

Figuring out REA

Presently I am looking at how to fill the empty box in the top figure with the word contribute. It's meaning defined by WordNet.
http://www.w3.org/TR/wordnet-rdf/

The rea namespace rea: is defined by the diagrams below.