Apply, as much as possible, our JSON Format to our annotations as well

Use same representation for constant expressions as for primitive values in JSON format, i.e. no object wrapper such as "@some.binary.term" :{ "$Binary" : "..." } Instead use the plain value:  "@some.binary.term" : "..." This puts some burden on clients to "know" or look up the term definition to determine the actual type of a JSON string value, but that has to be done for JSON data responses anyway. Note that no way to distinguish between strings and data exception, datetime, guid values in a collection of Edm.PrimitiveType. In such a case, generic libraries should treat as string and clients must use out of band knowledge to interpret it as some other value. Same argument applies to model element path expressions: here the client knows from the term definition that the value is a model element path or one of its concreter sub-types, so the value can simply be a string containing the path without object wrapper: "NonExpandableProperties" :[ "Customer" , "Country" ] Instance path expressions still need the object wrapper to distinguish them from actual string values: "@Core.Description" :{ "$Path" , "CompanyName" }