The Internet is the next closest thing to magic. The sheer transparency of it comes down to the OSI Protocol Stack - a Seven-Layer network model, developed in 1970 - to help computer vendors move towards a common architectural model for network software.

The following diagram represents the 7 layer OSI Model:

Example of Programs supporting each Layer:

Layer	Sub Layer	Protocol Description	Example
5 through 7	All	Application	Browsers, Word Processors, Spreadsheets,  Accounting Software etc
3 and 4	All	TCP/IP	Winsock.dll, SNA
1 and 2	2	Dialup IP	Winsock.dll
		Data base engine	Hierarchical, Relational etc
		Operating system	Windows, Unix,  MacO/S, MVS etc
	1	Circuit boards	Wiring, plugs, Network adapters

Does that mean all that is required now is improved hardware and network performance?

No! Certainly not, according to Charles Richter of Ripose Pty Limited. So far only researchers and software engineers have benefited from the OSI model.

We have only gotten half way - from the ocean floor to sea level so as to speak. We have yet to fly!

The sky is where entrepreneurs usually hang out and they don't operate according to the laws of mechanics.

To paraphrase Peter Drucker, "business has a lot to do with marrying available resources with potential results". In other words, less to do with technology and more to do with sociology.

Richter launches his extension to the OSI model which continues the stack from "sea level" to the stars (the realm of creativity).

Too long has information been held hostage to technology.

This new meta protocol stack frees up the creative genius of the entrepreneur.

Richter's model, for the first time, allows an entrepreneur to model his enterprise (joint enterprise modeling). Then allows  business analysts  to design the business (joint requirements modeling).
And finally  analyst/programmers and software engineers to construct it (rapid application design).

The following 3 dimensional diagram shows the integration between the 7 layer OSI model & The Extended (Ripose 7 layer extension):

Example of program supporting each layer:

Layer	Protocol Description	Example
10 through 13	Joint enterprise model	Ripose compiler
7 and 9	Joint requirements model

(For further details please see Ripose Technique).

The following venn diagram emphasises  the integration point between the OSI model and the proposed Ripose extension as well as who (non IT professional) is supported by whom (IT professional).
 

	Client	Server
	Entrepreneur	Information architect
	User	Analyst/Programmer
	Researcher	Software engineer