Will there be any effort made to improve the situation with wiki text and formatting? The biggest problem I have isn&#39;t the API specifically (which works fine for my needs), but the fact that it is near impossible to implement WYSIWYG editing of wiki text. Also the lack of consistency between display of subject areas and pages in general make display formatting very difficult.<div>
<br></div><div>It would be great if the new API ( or even just addition to the existing API) could return structured XML for the entire page, and also take the XML as input for page changes. </div><br>Also I should add that API versioning is a maintenance nightmare without unit tests and and an API test team, and the deployment strategy for new versions into production for Wikipedia seems sort of cavalier at the moment. I am basing this statement off the idea that versioning means you want to have the flexibility to make large scale changes without braking older clients.<div>
<br></div><div>Anyway I am not opposed to some sort of REST extensions for certain queries that make sense (i.e., lists of categories to which a page belongs), but it seems like you want to start over from scratch when these additions could just be added into the current API. Just provide something in the query that allows us to get a context id that we can pass back in future transactions. Then client apps can adopt RESTful queries where they need it, especially since requiring stateful queries increases the learning curve for API usage. <span></span></div>
<div><br></div><div>Robert</div>