Martin Holmes

I like 2 as well. 3 would probably not turn out well. :-)

I agree: deprecate unnecessary elements and make the others mandatory at the same time. Thinking about interdependent config items: could we unify them into single elements with a more sophisticated...

I agree it's blue sky, but when there's time I'd definitely like to try it and see whether it makes any difference. The tricky bit is figuring out whether it'll...

Thanks for this detailed breakdown. I like option 3. I also think that a) we should deprecate scrollToTextFragment and get rid of the related code, because it doesn't show signs...

@joeytakeda Switched this from the 1.1 milestone to the 1.2 milestone, since we still don't have a clear plan for it. Switch it back if you disagree.

@joeytakeda Should we switch this to Blue Sky for now?

Thanks for this; I'm slightly surprised that the ODD-chaining worked, but that's good. :-) I suggest we set everything to version 2 right now, and first do the deletions (deleting...

This is the key deliverable for version 2.0 at this point. Once this is sorted, we can release, assuming no other breaking or blocking things emerge from testing with real...

This should be linked with issue #317; various types of failure (no namespace, not well-formed, etc.) could trigger the suggestion that a pre-processing step be invoked to create well-formed source...

I'll be intrigued to see if this makes any difference. I must admit that I've never really understood what happens when you use method="json" and what the consequences of `@json-node-output-method`...