DeWitt Clinton

@fulldecent, that looks pretty good, thank you! Want to send it as a PR so we can properly review and merge it? Thanks!

Thanks for the report. I used a [VSCode plugin](https://marketplace.visualstudio.com/items?itemName=yzhang.markdown-all-in-one) to automatically generate the ToC, and it appears like it doesn't handle duplicate heading names well. I'll probably fix it right...

@fulldecent, what are your thoughts on what would be hosted on GitHub Pages if we enabled them?

I don't believe that URL has resolved for years. While not great, it's something we're unlikely to be able to fix since we don't control the domain. Fortunately it's just...

That's a good catch, and we may be able to fix it, too. Though this issue was specifically about updating the specs to use HTTPS. I'll change the title of...

I have no concerns with this proposal, and I'm happy to merge it. But since you're here and interested in this extension, would you also be up for converting it...

The original specs are all available as .wiki files under the /mediawiki/ top-level directory. This one is here, for example: https://github.com/dewitt/opensearch/blob/master/mediawiki/Specifications/OpenSearch/Extensions/Relevance/1.0/Draft%201.wiki I'm happy to merge pull requests to convert them...

I had a minute to go back and clear out some PRs and started reading this myself. I'm definitely supportive of publishing a canonical example of JSON serialization for all...

I [posted](https://groups.google.com/g/opensearch/c/uS89VPuXCT4/m/_s83473nBQAJ) over on the OpenSearch group to get some more eyes on this proposal.

It's in interesting question, and I can't recall whether the use of '+' has been discussed before. The only thing the [spec says](https://github.com/dewitt/opensearch/blob/master/opensearch-1-1-draft-6.md#the-searchterms-parameter) is that "The value must be URL-encoded."...