Possible property value encondings
Encode everything as string
- Uniform handling
- Can encode everything
- Issue: especially structured JSON values would be dumped into a string inside a JSON structure
- Diffing is easy
- We don’t expect serious performance issues from encoding boolean/integer as string
- Doesn't waste too much space
Use JSON types
- Natural representation for boolean, strings
- Issue: JSON number vs. Integer
- If metamodel says property is of type
int, but JSON contains 42.1
- If
int value is > 53 bit, JSON loses precision
=> Decision: for JSON transport, all primitive types are strings
Might be different for e.g. protobuf transport
Possible property value encondings
Encode everything as string
Use JSON types
int, but JSON contains42.1intvalue is > 53 bit, JSON loses precision=> Decision: for JSON transport, all primitive types are strings
Might be different for e.g. protobuf transport