The Universe Web (The U Web)

The Universe Web is planned to be a 3D version of the 2D World Wide Web. It thus should share its phenomenal scalability and interoperability.

The Universe Web was introduced here:

Excerpts from that article:

Here's a list of different kinds of Entity:

• Places: buildings, streets, hills, lakes
• Things: trees, books, birds, clocks
• People

---

The Universe Web I've just described is a lot like the World Wide Web:

• An Entity is like a Web Resource
• The State of an Entity is like an HTML Web Representation of a Web Resource
• A Link in an Entity's State is like a Web URL inside an HTML Web Representation
• Laws are like Javascript, Flash, link hover, blink tags and animated GIFs
• Rule sets are like PHP scripts or Java servers
• A State Observation is like a Web Representation Transfer

A crucial difference between the Resource Web and the Entity Web is that, here it's another Entity doing the Observation. One Entity transfers its State to another.

---

So that's my Universe Web. It's basically the same as the World Wide Web and thus as scalable, linkable and interoperable. It comes with added symmetry: Entities, including People as avatars, exchange State in each direction.

---

It's a two-way data Web, not a one-way document Web.

This site is the follow-on from the above article, defining the open standards or specifications for the Protocol and the Notation of the Universe Web, supporting its Entities, States, Links, Laws, Rules and Observers. It also points to an open source reference implementation.

Entity Specifications

There are five specifications. They are named 'N-something' after 'eNtity'. Collectively, they're known as the Entity Specifications or 'NS':

• NI: Entity Interaction - the Observer Pattern
• NP: Entity Protocol - the Distributed Observer Pattern: UDP/Multicast, cacheing
• NN: Entity Notation - JSON plus link notation
• NR: Entity Rules - JSON unification and production rules; schema language
• NT: Entity Types - JSON schemas for various Entity types and their natural behaviours

The specifications are layered: each specification is independent of those following it.

There is a set of examples here.

Implementations

The 'reference implementation' is written in Java and is called 'JJ'.

JJ is intended to be run both client-side (Linux, MacOS, Windows) and server-side (Linux) - and possibly on Android.

Once the specifications and the reference implementation are stable, the intention is to port the JJ code into a previous C implementation, for use in mobile phones and all other platforms.

The Micro Web

The Universe Web has a 2D, Web 2.0 counterpart, called The Micro Web. It's all the same thing, except one renders OpenGL, the other DOM via Javascript; one uses UDP, the other TCP.