Yeah, I agree with your two points, with one small caveat. There is always a risk that a library you depend on stops being maintained. We just have to be aware of that and make informed decisions. The likelihood that a well established graphing library, like D3.js or similar, stops being maintained any time soon is low. The likelihood that RAWGraph stops being maintained is higher, but the benefit is that it would take us less time to implement a graph builder. We would have to weigh up that risk with the (potential) extra effort required to either reimplement or maintain should it be abandoned.

As of 22nd May 2017, Polestar is no longer maintained (455f0f81). The suggested alternative, Voyager, is also no longer actively maintained according to this GitHub issue. A comment on that GitHub issue claims that "You could probably build your own version of Voyager without too much effort (i.e. a month of work or so) if you only need a specific feature set". I therefore didn't spend any more time looking into Voyager.

Solved in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/1087463

Patches related to this backporting effort can be found with the rest-api-1.43-backports topic

Done as part of T322917: Improve examples in OpenAPI Schema

Noting down the order to do things in as decided by engineers:

Oh, well spotted - that's a super useful revelation!

@Ifrahkhanyaree_WMDE I've created a very large item with lots of statements for you to test the resource-too-large case. Below is a screenshot of me trying to add another statement to the item. You should get the same result for any type of edit that would make the item bigger.

I'm wondering if this task should include other OAS fields, such as summary and decription. I notice there isn't consistent capitalization for them either.