Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataShape serialization #204

Open
kwmsmith opened this issue Dec 16, 2015 · 0 comments
Open

DataShape serialization #204

kwmsmith opened this issue Dec 16, 2015 · 0 comments

Comments

@kwmsmith
Copy link
Member

Quoting from blaze/blaze#1361:

I feel like the string representation of the dshape is the best serialization format. Maybe what we need is a javascript implementation of the datashape parser.

That would be one direction to go in here; when I floated it with our Client-side JS team, there was resistance to having to develop and maintain another parser.

Since datashape objects are intrinsically nested, my desire would be to serialize datashapes in a way that's consistent with that nesting, to remove the need to implement multiple datashape parsers and keep them in sync, etc. The string form of datashapes are great for human consumption, but they're intrinsically flat, and we run into issues with conflating representation with serialization.

My vote is for a serialization format that encodes the nesting, so that we can do datashape parsing in one and only one place. The DataShape.__str__ implementation can handle the human-readable part of the problem.

@llllllllll thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant