Another take on the distinction between data and knowledge tailored for
engineers. (01)
Data
Bit arrays, streams that come from sensors and is contained in data
repositories
Information
Data + the who, what, where of the data (metadata)
Knowledge
Information processed by a scheme for classifying and interpreting the
information (an ontology) (02)
-----Original Message-----
From: Matthew West
Sent: Tuesday, January 06, 2015 3:28 PM
To: '[ontolog-forum] '
Subject: Re: [ontolog-forum] knowledge base and DBs (03)
Dear Kingsley, (04)
-----Original Message-----
From: ontolog-forum-bounces@xxxxxxxxxxxxxxxx
[mailto:ontolog-forum-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Kingsley Idehen
Sent: 06 January 2015 20:00
To: ontolog-forum@xxxxxxxxxxxxxxxx
Subject: Re: [ontolog-forum] knowledge base and DBs (05)
On 1/6/15 2:00 PM, Matthew West wrote:
> Dear David and Alexander,
> Hmmm. Well to my mind the biggest difference is not to do with
> operations and logic, SQL is very competent. The key difference is
> that a database has a structure that is defined at database definition
> time, and data that is added at runtime. On the other hand, a
> knowledge base has minimal structure, and is defined by the type of
> knowledge base used. None of this has much to do with what you can do
> with the different approaches, and a lot of things you can do with
> either. A database is likely to be more efficient when there are a lot
> of records with the same structure to be stored and referred to. A
> knowledgebase is likely to be more efficient when flexibility in structure
is what is required.
>
> Regards
>
> Matthew West
> Information Junction
> Mobile: +44 750 3385279
> Skype: dr.matthew.west
> matthew.west@xxxxxxxxxxxxxxxxxxxxxxxxx
> http://www.informationjunction.co.uk/
> https://www.matthew-west.org.uk/
> This email originates from Information Junction Ltd. Registered in
> England and Wales No. 6632177.
> Registered office: 8 Ennismore Close, Letchworth Garden City,
> Hertfordshire,
> SG6 2SU. (06)
Matthew, (07)
How about the following, which distinguishes: (08)
1. Application that provides management services 2. Document comprised of
content (data).
MW: Well I would not call a database a document. It is the database that
contains the content, and the DBMS which provides access and management
services to the data in the database. (09)
Thus, we end up with A DBMS (Database Management System) being an
application that provides Data Management (import, indexing, querying,
export etc..) services (driven by its supported model) scoped to
Document(s) [which may be internal or external] comprised of structured data
-- represented using a variety of notations.
[MW>] Well yes, but I still don't like calling a database a document. A
document suggests a lack of structure, as in a text tract, whereas a
database is highly structured. (010)
Which also implies that a Knowledge Management system just another kind
application with additional capabilities e.g., reasoning and inference.
[MW>] A DBMS has those capabilities as well, certainly a SQL one. (011)
In both cases, if relational in orientation, these applications group tuples
as Relational Tables and/or Relational Predicate/Property Graphs.
[MW>] Well strictly relational tables are a different view of data from a
graph view, though they are isomorphic. Of course you can trivially create a
triple store using a relational database. Some of the differences in
performance can arise from whether the underlying structure is graphical or
relational. (012)
Regards (013)
Matthew West
Information Junction
Mobile: +44 750 3385279
Skype: dr.matthew.west
matthew.west@xxxxxxxxxxxxxxxxxxxxxxxxx
http://www.informationjunction.co.uk/
https://www.matthew-west.org.uk/
This email originates from Information Junction Ltd. Registered in England
and Wales No. 6632177.
Registered office: 8 Ennismore Close, Letchworth Garden City, Hertfordshire,
SG6 2SU. (014)
--
Regards, (015)
Kingsley Idehen
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog 1: http://kidehen.blogspot.com Personal Weblog 2:
http://www.openlinksw.com/blog/~kidehen
Twitter Profile: https://twitter.com/kidehen
Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen
Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this (016)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J (017)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J (018)
|