linkeddata | rb including all parsing/serialization plugins | JSON Processing library

You can use solid-file-client for that

https://github.com/jeff-zucker/solid-file-client

You can use multiple vocabularies/ontologies to describe the same entity.

If a consumer (like a search engine) only recognizes terms from a specific vocabulary (like Schema.org), it will simply ignore the terms from the other vocabularies (like FOAF).

So, for an entity that represents a person, you could use the types schema:Person, foaf:Person and/or dcterms:Agent. And for a book this person wrote, you could use the properties schema:creator, foaf:maker, and/or dcterms:creator.

If your primary motivation is SEO (instead of Linked Data), I would recommend to use the vocabulary Schema.org as far as possible, and other vocabularies in addition (at least where Schema.org is lacking, or, if you prefer, wherever it’s possible).

Just to give you a hint for the entailment owl:Thing EquivalentTo Game:

We have

Reflexive: isSimilarTo

which is equivalent to

owl:Thing SubClassOf isSimilarTo some Self

which in fact means each individual in your ontology is related to itself via the property isSimilarTo, i.e. for each individual x in your ontology we can entail

isSimilarTo(x, x)

In addition, we have

isSimilarTo Range Game

which is semantically equivalent to the axiom

owl:Thing SubClassOf isSimilarTo only Game

This means, if there is such a relation isSimilarTo(x, y), the object y will belong to class Game.

Now, remember that we already said that every individual in the ontology has such a relation, just to itself. Thus, we can infer that each individual belongs to class Game.

How do you know that it's not resolvable? RDF doesn't have a concept of a "relative URI", all the URIs are resolved relative to something (and perhaps to what is an implementation detail in some cases), so you end up with absolute URIs. In the HTML results from that endpoint, I get http://linkeddata.systems:8890/hostncbitaxid/, and that could easily be resolvable.

That said, if you are ending up with results that include non-absolute URIs, and you want to filter those out, you could use some heuristics to do that. For instance, if you only want URIs beginning with http, you can do that. E.g., here's a query that returns two values for ?uri: