In case a community collectively can understand prose like this:
"NFκB was first identified as a regulator of the expression of the kappa light-chain gene in murine B lymphocytes but has subsequently been found in many different cells. Several different NFκB proteins have been characterized. The activated form of NFκB is a heterodimer, which usually consists of two proteins, a p65 (also called relA) subunit and a p50 subunit."
then it is useful to design, for that community, a repository of concepts and an upper ontology for the grammar so that information can be stored and exchanged in a computer-interpretable manner.
The difference between HTML and RDF is that in case of the former the reader of the fetched document does the exegesis. RDF on the other hand must be such that only one interpretation is possible independent of the reader.
All information in this universe is part of one whole, even that bag of chips and its inscriptions.
Op 26 november 2018 om 20:48 schreef Tim Berners-Lee <timbl@w3.org>:
On 2018-11 -21, at 22:40, David Booth < david@dbooth.org> wrote:9. Namespace proliferation. It's hard to manage all the
namespaces involved in using RDF: FOAF, SKOS, DC and all the
hundreds of specialized namespaces that are encountered when
using external RDF. Namespaces can help organize IRIs into
categories (typically based on the IRI's origin), but this
fact is nowhere recognized in official RDF specs.No, the RDF specs don’t explain how that works,and it is perhaps the most important and different features of RDF.- Life is like a bag of chips. Understanding that you are after a mixture of ontologies in your app.Here is where they come froma) Making your own ontology on the fly for speedb) Looking at looking at the solid teams (etc) favorite listc) Looking at places like LOVd) asking around on chate) Getting others to review and help standardize your ontologyf) Making standardswith various levels of investment, interoprativTim