Re: [ontolog-forum] Watchout Watson: Here comes Amazon Machine Learning

[Ravi Sharma <drravisharma@xxxxxxxxx>]

Mathew

Thanks for articulation, one may also want to relate your temporal database parameters to

1. What Databases (Oracle or Applications) call Valid Values not only for time but other ranges of values etc.
2. SBVR -time and calendar task force or working group from OMG?(EJB - might want to comment as he shaped a lot of that discussion and concepts).
3. Philosophically and historically stories can be found that state like: "First it was told by, then repeated by ....and then... etc. and known today as....X" and how these would be described as concatenated time events in ontologies?

Regards,

On Fri, May 1, 2015 at 1:36 PM, Matthew West <dr.matthew.west@xxxxxxxxx> wrote:

Dear Thomas,

 

John, Matthew:

 

Commercial databases have no explicit ontology beyond the ontological commitments made in their database catalogs. I try to articulate an implicit ontology which I believe they all share, in my book that John alluded to.

 

The current SQL standard recognizes valid time and transaction time, the former being the time in which the things and objects the database is about exist, and the latter being the time in which rows reflecting these things and changes are entered into the database and/or marked as logically deleted.

[MW>] Do you mean by “logically deleted” that the statement is no longer true but once was, or that they were never true (say the record was entered in error or a change of understanding)?

 

I have proposed a third temporal dimension -- that in which the statements made by rows in tables are asserted to be true. For example, a logically deleted row remains in a database as one which no longer represents the assertion of the statement it makes. And just as we can utter/write statements (de-indexicalized declarative sentences) that, starting at some point in time, we are no longer willing to assert represent statements we believe are true, so too we can enter rows into database tables that represent statements that we are not yet, at that time, willing to assert represent true statements. The former rows are tagged with "speech act" time periods (see below) that are entirely in the past, and the latter with time periods that are entirely in the future. Again, this is not in the current SQL standard, nor in the current comp sci literature.

[MW>] I’m still not clear (but interested).

 

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.

 

 

Assertions (and their withdrawals) are speech acts, and so in my book, I attempt to introduce this third temporal dimension as that. So I distinguish (i) rows in tables as physical inscriptions; (ii) statements made by those rows (semantics); (iii) speech acts associated with those semantics such as assertions and withdrawals, also assents, dissents, and the whole panoply of propositional attitudes (pragmatics); and (iv) the propositions expressed by those statements (the Holy Grail of why we manage data in the first place).

 

I think that all of these are managed objects which can be represented as managed objects in relational databases. The only managed objects in today's databases, on the other hand, are the physical tables, rows and columns themselves. Constraints preserve an imperfect mapping to an interpretation, and the understanding of that interpretation is a matter that falls outside the scope of the management of data itself. Or, at least, so I understand a basic assumption underlying the current state of affairs -- an assumption I do not make myself.

 

A bit of a soapbox email here. Apologies, if needed.

 

Tom

 

 

On Wednesday, April 29, 2015 8:13 AM, John F Sowa <sowa@xxxxxxxxxxx> wrote:

 

Dear Matthew,

Possibility and necessity affect the logic, not the ontology:

> Another problematic category is possibilia (things that might be,
> or possibly are in some parallel universe).

They can be treated in the same way as plans for the future.
For example, if you're designing an airplane or a bridge, it's
a possibility until it's actually built.

> The criteria for including possibilia (or not) is utility vs
> the baggage that comes with the extra commitment.

The categories of parts, part numbers, etc., might be empty
in actuality, but they are specified in the ontology by the
same methods before and after the things are built.

There are, of course, issues about storing information about the
future in the database -- orders for future delivery of things
that don't yet exist, reservations for hotels, travel, etc.
The orders and reservations exist in the present (or past),
but they refer to things and events in the future.

Tom Johnston wrote a book about time and temporal issues in
databases.  Perhaps he might care to comment on this point.

Following is an article in which I discuss issues about
modality, possible worlds, and the laws that govern them:

    http://www.jfsowa.com/pubs/worlds.pdf
    Worlds, models, and descriptions

And by the way, possibilities are another area where a strictly
nominalist position (e.g., Quine's or Goodman's) gets into trouble.

Clarence Irving Lewis, who defined the first modern versions
of modal logic, had been the chair of the philosophy department
at Harvard while Quine was a student and later a professor.

But Quine was very strongly opposed to any version of modal
logic and any talk of possibilia.  Hao Wang, who had earned
a PhD under Quine's supervision, was very critical of Quine's
attitude.  He called it *logical negativism*.  See

    Wang, Hao (1986) Beyond Analytic Philosophy: Doing Justice
    to What We Know, MIT Press, Cambridge, MA.

John

_________________________________________________________________
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

 

_________________________________________________________________
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
 

--

Thanks.
Ravi
(Dr. Ravi Sharma)
313 204 1740 Mobile

_________________________________________________________________
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    (01)