this is for holding javascript data
Deborah L. McGuinness edited section_Future_Potential_Currently_knowledge__.tex
about 8 years ago
Commit id: e4f0258e10fe4ff66f7f4dae69a5d679c5f3e7ae
deletions | additions
diff --git a/section_Future_Potential_Currently_knowledge__.tex b/section_Future_Potential_Currently_knowledge__.tex
index 95a59ed..a3819a2 100644
--- a/section_Future_Potential_Currently_knowledge__.tex
+++ b/section_Future_Potential_Currently_knowledge__.tex
...
There is an interesting overlap between what is considered a ``knowledge graph'' and what is an ontology.
The most commonly accepted definition of an ontology is a ``an explicit specification of a conceptualization'' \cite{Gruber_1993}.
To a large degree, knowledge graphs conform to this definition, but generally ontologies tend to talk about generalities (classes, properties, and roles)
instead with less focus on inclusion of
content about specific instances.
Few For example, most ontologies
that include content related to descriptions of world landmarks would have descriptions of the landmark class and its related properties but would
typically not include a mention
of the Eiffel Tower, but a knowledge graph that covers the domain of Parisian landmarks would.
Conversely, knowledge graph approaches can be used to improve the credibility of ontologies by encoding the epistemology of the statements in the ontology.