Tyler Gregg

@davidglavas You may find the [cookbook](http://amzn.github.io/ion-docs/guides/cookbook.html) useful. For straight conversion between formats, see also [`ion_writer_write_all_values`](https://github.com/amzn/ion-c/blob/master/ionc/include/ionc/ion_writer.h#L253), which re-writes the document the reader is configured to parse using the writer's configuration.

@davidglavas There is no example in the "Migrating JSON data to Ion" section because Ion readers can parse JSON natively with no extra configuration (Ion's text format is a superset...

@davidglavas You didn't miss anything. I didn't realize that your use case involved reading the same data multiple times. Convert JSON data to binary Ion like this. I stitched together...

@davidglavas Yes, the path extractor API. See [ion_extractor.h](https://github.com/amzn/ion-c/blob/master/ionc/include/ionc/ion_extractor.h). The best place to find some quick examples at this point is probably the tests: [test_ion_extractor.cpp](https://github.com/amzn/ion-c/blob/master/test/test_ion_extractor.cpp).

@davidglavas I agree. Relevant issues: https://github.com/amzn/ion-docs/issues/98 https://github.com/amzn/ion-docs/issues/99

Sounds like a good idea to me.

Other thread-safety concerns: * ion_int_init * system symbol table initialization

(Note: my usage of the term _unambiguous local offset_ below is not defined in the spec; I'm introducing it for the purposes of this comment to mean that we know...

I don't think the spec intends to prohibit repeated fields in ordered structs. I believe the second passage you quoted can be summarized as "Repeated fields must not be discarded,...

Thanks for the detailed issue. I agree that the spec can use clarification here, and we should have done that when the test cases were added that prohibit repeated field...