Merge pull request #11 from asteurer/bytes

doc: documenting how byte arrays are handled when converted to JSON

Author: calebschoepp

wit/types.wit

@@ -14,6 +14,10 @@ interface types {
     ///
     /// This corresponds with the `AnyValue` type defined in the [attribute spec](https://opentelemetry.io/docs/specs/otel/common/#anyvalue).
     /// Because WIT doesn't support recursive types, the data needs to be serialized. JSON is used as the encoding format.
+    ///
+    /// Byte arrays require special encoding since JSON cannot distinguish them from number arrays.
+    /// They are base64-encoded with a prefix that follows the Data URI RFC 2397 convention: 
+    /// `data:application/octet-stream;base64,<BASE64_ENCODED_BYTES>`
     type value = string;
 
     /// An immutable representation of the entity producing telemetry as attributes.