This motion proposes the following schema:
Name: dsnp.reply Model Type: Parquet Payload Location: IPFS
Parquet schema:&nbsp;
<a href="https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Reply.md">https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Reply.md</a>
Frequency discussion:&nbsp;
<a href="https://github.com/frequency-chain/frequency/issues/2125">https://github.com/frequency-chain/frequency/issues/2125</a>
TL;DR: Fields containing a content has are changing from BYTE_ARRAY to STRING. While this is compatible at a raw binary level, it is semantic change that developers should be aware of. Note that there is no "legacy" data on mainnet at this time, so the original schema will never be used.

This motion proposes the following schema:

Name: dsnp.reply  
Model Type: Parquet  
Payload Location: IPFS

Parquet schema: 

[https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Reply.md](https://github.com/LibertyDSNP/spec/blob/main/pages/DSNP/Types/Reply.md)

Frequency discussion: 

[https://github.com/frequency-chain/frequency/issues/2125](https://github.com/frequency-chain/frequency/issues/2125)

TL;DR: Fields containing a content has are changing from BYTE\_ARRAY to STRING. While this is compatible at a raw binary level, it is semantic change that developers should be aware of. Note that there is no "legacy" data on mainnet at this time, so the original schema will never be used.

- **Problem Statement:** Developers need to be aware of a change in the Parquet schema from BYTE_ARRAY to STRING for fields containing content.
- **Significance:** Ensuring developers are informed about this semantic change is crucial for maintaining data integrity and compatibility.
- **Proposed Solution:** Update the Parquet schema to reflect the change from BYTE_ARRAY to STRING for content fields.
- **Expected Outcomes:** Improved data handling and compatibility for developers working with the Parquet schema.

#47 Schema proposal: dsnp.reply (update for DSNP 1.3)

No Active Proposals