For those interested, the Internet Encyclopedia of Philosophy, maintained by University of Tennessee at Martin, is also a very nice resource, similar to SEP.

Here is their entry on Gettier cases, for example.

https://iep.utm.edu/gettier/

I'm only a hobbyist in this area, but I wonder why the review wouldn't mention some of the graph databases as, at least, semantic web adjacent. Their relative success seems to lend credence to the overall vision of the semantic web and its supporting technologies. For example, are there really more than surface syntactical differences between SPARQL and Cypher?

Even though it was over-hyped, I like the semantic web because it supports a conception for the future that includes something other than neural network black-boxes. However, whether the ideas deliver remains to be seen.

If anyone is looking for an introduction, then I think the Linked Data book from Manning is worth mentioning--it might be a little dated at this point. The author provides a coherent introduction and helps, especially, in cutting through the confusing proliferation of acronyms that characterizes this field. As others have mentioned, reliable software is a major stumbling block. It's especially unfortunate that there isn't better browser support, of RDFa for example.

Check our SPARQL-driven Knowledge Graph management system :) https://atomgraph.github.io/LinkedDataHub/

I take it that the goal is to list books of general interest for the software engineering student. It is not clear what the author means by classic CS material, so it is hard to know what is excluded. Surely, Mythical Man Month and GoF qualify as classics of software engineering. Or does the author mean classics from the entirety of a CS program?

I've been teaching a software engineering class for a few years. Being conscious of the high cost of textbooks, I find that Applying UML and Patterns by Larman achieves the best balance of practice, design, and process.

For students who want to dig into agile methodologies I would recommend Extreme Programming Explained by Beck and the Poppendiecks on Lean.

In my opinion, a philosophical grounding is helpful for the programmer. Accordingly, I'd want to suggest something like Locke's Essay Concerning Human Understanding or a secondary source on Aristotelian categories. Moreover, a broad knowledge of different types of ethical systems will benefit a developer.

Lastly, as a kind of curve ball, I would recommend any STEM student to work through an LSAT preparation book. Technologies will come and go, but, throughout a career, the problems a developer encounters will likely have dimensions that require general critical thinking.