How is a MO represented and what does it contain?
A MO is represented internally in the MC-API by a Unicode structure, but can be: (i) projected into readable-text or other formats such as binary, uuencoded, 7-bit, 6-bit, etc., by a set of translation rules, (ii) serialized and streamed, (iii) encrypted, (iv) signed, (v) left-linked, right-linked or symmetric-linked to form sequences with other MOs, (vi) nested, (vii) layered, (viii) provided with a validity time range, (ix) provided with an usage limit, (x) restricted or anchored to a location or to a set of locations, etc. A MO thus contains data, methods and binding (like a standard object), plus linking, origin, destiny and usage informations — which are cryptographically secure and self-enforceable.
