Proper documentation for compound datatypes.

[Fak3]

As was discussed in gs-gs/staruml-cefact#62, the staruml plugin now generates Measure, Code and other compound datatypes as nested sub-object. So that proper Measure type declaration in the uml file should be:

The section https://edi3.org/specs/edi3-uml-profile/develop/#example-1 of the documentation should be updated with this example.

Other compound types in the documentation should also be revisited and adjusted accordingly.

• Amount add value: Numeric
• Code add value: String
• Identifier add value: String

The next chapter in the docs - https://edi3.org/specs/edi3-uml-profile/develop/#qualified-types--enumerations should also be updated, will have to spend some more words about qualified enumeration types. As Code type now becomes a compound one (defined by value + scheme) the example of TransportEventType_Code used in the doc should mention that values of the enumeration should be plain strings, ie the same type as the value attr of Code compound type has. And for the comparison, it is worth to add example of numeric Enumeration, for ex StatusCode_Numeric, and mention that values of this enumeration should be interpreted as Numeric type, since Numeric is not a compound, but simple datatype.