# \#serialization

**URL:** https://forum.snap.berkeley.edu/tag/serialization/459.md

[Latest](https://forum.snap.berkeley.edu/latest.md) · [Categories](https://forum.snap.berkeley.edu/categories.md) · [Tags](https://forum.snap.berkeley.edu/tags.md)

---

## [New data serialization format?](https://forum.snap.berkeley.edu/t/new-data-serialization-format/21434)

<div class="topic-metadata">

**Author:** [@mobility212](https://forum.snap.berkeley.edu/u/mobility212)\
**Replies:** 12\
**Last updated:** [February 25, 2026, 9:21pm UTC](https://forum.snap.berkeley.edu/t/new-data-serialization-format/21434 "2026-02-25T21:21:35Z")

</div>

Ditch (printable @list ::lists) and forget about (\[json V\] of @list). I have devised a data serialization format oriented for Snap!. Thoughts on this? https://snap.berkeley.edu/snap/snap.html#present:Username=mobility21…

---

## [Snap! XML schema?](https://forum.snap.berkeley.edu/t/snap-xml-schema/9724)

<div class="topic-metadata">

**Author:** [@rubenverg](https://forum.snap.berkeley.edu/u/rubenverg)\
**Replies:** 5\
**Last updated:** [January 8, 2022, 3:28pm UTC](https://forum.snap.berkeley.edu/t/snap-xml-schema/9724 "2022-01-08T15:28:27Z")

</div>

I've been working on an external tool that needs to parse the XML file exported by a Snap! save, but I can't find any documentation on how the file is structured. Is there something like that, or do I need to read the wh…