Erik Mattheis

See #224 for some discussion about why bridging to/from JsonStructure is insufficient. I missed this issue when I filed the new one, but @jjspiegel's original request is what I'm looking...

Also, note that some work is likely necessary in JSON-P to make this work like JAXB or Jackson: https://github.com/eclipse-ee4j/jsonp/issues/233

This is an intriguing idea. The set of pointers could determine whether or not the parser automatically skips over events. Might be tricky to specify this in a non-ambiguous way,...

I don't think memory consumption is the real concern here. Skipping is implied when `getXXX` is not called. Perhaps the documentation should be clearer in this regard, but it's an...

@rmannibucau A parser can basically tell by the first character what the event is. No need to move any further until asked to. If `getXXX()` is never called, the parser...

There is nothing in the JSON-P API that prevents an implementation from lazily fetching entries, is there? My understanding is that the call to `next()` advances the stream and subsequent...

Does JSON-P even have a published spec? All I can find is the API.

I followed the link from the [JSON-B website](http://json-b.net/download.html) which leads [here](https://jcp.org/aboutJava/communityprocess/pr/jsr367/index.html). Now I realize that is the public review draft. 🙄 Anyway, I found the [final spec](https://jcp.org/aboutJava/communityprocess/final/jsr367/index.html) and I see...

Personally, my interest in Yasson is limited to its role as the JSON-B reference implementation, so I am happy to wait until this becomes specified behavior. If I can't write...

@bravehorsie agreed, but figured I'd get a head start here - not sure what the timeline is for the JSON-B issue