Overhaul of advanced features

Origin of:

- composite types
- one of type
- entity definition
- exclusive properties
- examples folder

Syntax update for:

- one of type
- referencing
- templates properties (variable property name)
I feel that this document keeps on context-switching and confusing me. MSON is like JSON such that it can be used for both describing an example object and also describing a valid object with some rules. I think we need to divide this document into those two parts.

When I am writing an example object, I would not use `one of` but will probably use it when I am describing rules for the object. When I am using it to describe rules for an object `(json-schema)`, I will not have example values like `green`.

Now, that I think about it, I have a question. What exactly are we using MSON for? To describe schema? To give examples? Or both?

If we are doing both, we definitely need to seperate the parts in the Specification.