Todd V. Jonker

`SpanProvider` is indeed the correct API. If a resulting `TextSpan` is not providing accurate line numbers, please provide a failing test case, or at least an example. I am skeptical...

BTW the easiest way to get a `TextSpan` is via[`Spans.currentSpan(TextSpan.class, reader)`](https://static.javadoc.io/com.amazon.ion/ion-java/1.4.0/com/amazon/ion/util/Spans.html#currentSpan-java.lang.Class-java.lang.Object-)

Line counting is tricky. The private `_line_count` can't be exposed with any robust semantics, because in some cases the parser/lexer needs to read further ahead than the cursor. For example,...

I isolated the bug you found as #233 so that can be fixed separately from discussion of API additions.

Relevant discussion and spec passage at https://github.com/amazon-ion/ion-docs/pull/308#discussion_r1568992573

@zslayton Can you clarify your intent by the "not include types" part? We still need type declarations to handle primitive and macro encodings. I believe that we are postponing implementation...

OK, gotcha. BTW My working assumption is that we'd keep the spec as-is with respect to features we won't have in preview, or may drop permanently for the final 1.1...

I'm wary of several of these proposals. It's going to be hard to discuss with all of this under one issue.

* We agreed to delay implementation of parameter cardinality, not eliminate it. (As I work on the denotational semantic model, I'm becoming more convinced that we need _more_ strong typing,...

Here are some thing that I think are (some) requirements for "finalizing" the spec. * Merge the denotational semantics document from its home at https://github.com/toddjonker/ion-docs/commits/main/ into the `ion-11-specification` branch with...