Joey Takeda

For our reference, here's a table of the child elements of `` noting whether that option depends on anything and whether it's already mandatory. | Element | Depends | Currently...

I'm going to bump this to blue sky—it's purely an enhancement that could be interesting (but is not at all necessary).

In terms of interdependence, it all comes back to ``. My feeling here is that not creating contexts is going to be fairly rare—I can't imagine many cases where resources...

I agree re: deprecating scrollToTextFragment and linkToFragmentId. If we are deprecating options, I think indentJSON could be deprecated (mea culpa since I know I advocated for it) and verbose could...

Attached to this ticket is a zip archive that contains an ODD, a produced RNG, and some sample configuration files that model the changes proposed based on the above discussion....

I'm going to do the deletions now in a separate branch--I'll open a ticket for that to keep things clean.

Arising from #270—we should make sure the documentation is clear about the mandatory elements and resolve the ambiguous language that params "requires two elements"

Following a very productive meeting today (Oct 18), @martindholmes and I have rethought this quite significantly so that each configuration element describes its purpose with properties specified as attributes —...

I'm going to experiment with this in branch iss239-json

I have now done this in the iss239-json branch, but my tests are so far inconclusive. In my local copy, I've added the `repeat` option and the `-t` option to...