atextor
commented
1 year ago You are of course correct in that JSON strings have a different value range than XSD strings. However, this is not a problem because XSD string's value range is a subset of JSON's.
The Payloads section states the following:
[...] the Property is serialized as
${propertyName}: ${value}where${value}is the JSON serialization of the respective Property’s value, details on mapping of the data types are given in Data type mappings.
In other words, if a bamm:Property has an effective data type of xsd:string, then the JSON payload data for the corresponding aspect may only contain values that are also valid xsd:string; you're not allowed to put 0x00 in the JSON payload.
I'll add the to be discussed label, because it might be necessary (at least helpful) if this is explained more explicitly.
mristin
Is your task related to a problem? Please describe. JSON strings can represent arbitrary Unicode strings.
In constrast, XML strings are constrained to the ranges
[\x09\x0A\x0D\x20-\uD7FF\uE000-\uFFFD\u00010000-\u0010FFFF](according to the de facto standard XML 1.0).This means that you can not encode characters such as
\x00or\x01in XML even when escaped. For example, this is invalid XML:For more information, see first https://www.w3.org/TR/xmlschema-2/#string and then follow to https://www.w3.org/TR/2000/WD-xml-2e-20000814#dt-character.
Additional context @atextor You are probably aware of the issue. I don't know if it directly impacts your design. I just wanted to give you a heads-up in case it was not on your radar.
This is related to #175.