The Representation of Reality in Computational Form Nick Rossiter Visiting Fellow with Michael Heather and Dimitrios Sisiaridis Computing, Engineering.

Slides:



Advertisements
Similar presentations
I-ESA'08 Berlin1 Logical Foundations for the Infrastructure of the Information Market Heather, Michael, Livingstone, David, & Rossiter, Nick, CEIS, Northumbria.
Advertisements

Four-level Architecture for Closure in Interoperability EFIS, 17th-18th July 2003 Nick Rossiter & Michael Heather Informatics, Northumbria University
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Lecture 24 MAS 714 Hartmut Klauck
Adjoint Typing: Is it Whitehead’s Category of the Ultimate?
Algorithms + L. Grewe.
Object-Oriented Application Development Using VB.NET 1 Chapter 5 Object-Oriented Analysis and Design.
Basic Structures: Sets, Functions, Sequences, Sums, and Matrices
1 What are Bit Strings? The View from Process Nick Rossiter Northumbria University.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.
Modeling the Data: Conceptual and Logical Data Modeling
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
Chapter 1 Program Design
Chapter 4 Entity Relationship (ER) Modeling
C o n f i d e n t i a l Developed By Nitendra NextHome Subject Name: Data Structure Using C Title: Overview of Data Structure.
Data Modeling Using the Entity-Relationship Model
On Roles of Models in Information Systems (Arne Sølvberg) Gustavo Carvalho 26 de Agosto de 2010.
CSE314 Database Systems Data Modeling Using the Entity- Relationship (ER) Model Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson Ed Slide Set.
Chapter 10 Architectural Design
The Design Discipline.
Chapter 7 Data Modeling with Entity Relationship Diagrams Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition.
Category Theory By: Ashley Reynolds. HISTORY OF CATEGORY THEORY  In 1942–45, Samuel Eilenberg and Saunders Mac Lane introduced categories, functors,
Chapter 4 The Relational Model.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Anticipation in constructing and interrogating Natural Information Systems: From Classical through Nano to Quantum Computing.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
SOFTWARE DESIGN.
Symposium 2: Applied Mathematics, Dynamical Systems, Logics and Category Theory CASYS’11 - International Conference on COMPUTING ANTICIPATORY SYSTEMS HEC.
 FOAL 2010 Modeling Aspects by Category Theory Serge P. Kovalyov Novosibirsk, Russia.
Lecture2: Database Environment Prepared by L. Nouf Almujally & Aisha AlArfaj 1 Ref. Chapter2 College of Computer and Information Sciences - Information.
Sets Defined A set is an object defined as a collection of other distinct objects, known as elements of the set The elements of a set can be anything:
Systems Analysis and Design in a Changing World, 3rd Edition
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 4 Entity Relationship (ER) Modeling.
1 The Contravariancy of Anticipatory Systems Dimitrios Sisiaridis, Michael Heather & Nick Rossiter Northumbria University, Newcastle NE2 1XE, UK Symposium.
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
21st May 2004Informatics Research Conference, Northumbria University 1 Some Fundamental Questions in Databases Nick Rossiter (with Michael Heather)
© D. Wong Ch. 2 Entity-Relationship Data Model (continue)  Data models  Entity-Relationship diagrams  Design Principles  Modeling of constraints.
Lecture 2: Introduction to Category Theory Nick Rossiter, Computing Science, Newcastle University, England
1Mr.Mohammed Abu Roqyah. Database System Concepts and Architecture 2Mr.Mohammed Abu Roqyah.
Databases Illuminated Chapter 3 The Entity Relationship Model.
Theory of Programming Languages Introduction. What is a Programming Language? John von Neumann (1940’s) –Stored program concept –CPU actions determined.
1 Typing in Information Systems Nick Rossiter, Michael Heather Computer Science and Digital Technologies Northumbria University, Newcastle NE1 8ST, UK.
Entity-Relation Model. E-R Model The Entity-Relationship (ER) model was originally proposed by Peter in 1976 ER model is a conceptual data model that.
Systems Analysis and Design in a Changing World, Fourth Edition
Exam 1 Review Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2008.
1Computer Sciences Department. Book: INTRODUCTION TO THE THEORY OF COMPUTATION, SECOND EDITION, by: MICHAEL SIPSER Reference 3Computer Sciences Department.
Exam 1 Review Dr. Bernard Chen Ph.D. University of Central Arkansas.
AREIN, I-ESA March Higher Order Logic and Interoperability in Global Enterprise Heather, Michael, Livingstone, David, & Rossiter, Nick, CEIS, Northumbria.
Object-Oriented Application Development Using VB.NET 1 Chapter 5 Object-Oriented Analysis and Design.
8.1 8 Algorithms Foundations of Computer Science  Cengage Learning.
Free and Open Systems Theory Nick Rossiter Michael Heather University of Northumbria
Lecture 3: Object Concepts as Categories Nick Rossiter, Computing Science, Newcastle University, England
Copyright © Curt Hill Other Trees Applications of the Tree Structure.
The Natural Metaphysics of Computing Anticipatory Systems Michael Heather Nick Rossiter University of Northumbria
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 6 Modeling the Data: Conceptual and Logical Data Modeling.
Kyung Hee University Class Diagramming Notation OOSD 담당조교 석사과정 이정환.
The Relational Model Lecture #2 Monday 21 st October 2001.
Department of Mathematics Computer and Information Science1 CS 351: Database Management Systems Christopher I. G. Lanclos Chapter 4.
Database Design, Application Development, and Administration, 6 th Edition Copyright © 2015 by Michael V. Mannino. All rights reserved. Chapter 5 Understanding.
Sadegh Aliakbary Sharif University of Technology Fall 2010.
Chapter 2 1. Chapter Summary Sets (This Slide) The Language of Sets - Sec 2.1 – Lecture 8 Set Operations and Set Identities - Sec 2.2 – Lecture 9 Functions.
SOFTWARE DESIGN & SOFTWARE ENGINEERING Software design is a process in which data, program structure, interface and their details are represented by well.
WOSC 2008 Wroclaw1 Problems of Interoperability in Information Systems Nick Rossiter and Michael Heather CEIS, Northumbria University, UK
Knowledge Representation Part I Ontology Jan Pettersen Nytun Knowledge Representation Part I, JPN, UiA1.
Presentation of Flowchart
Review of Week 1 Database DBMS File systems vs. database systems
Conditions for Interoperability
The Process Semantics of Time and Space as Anticipation
Process in the World as a Transaction
Chapter 15 Functional Programming 6/1/2019.
Presentation transcript:

The Representation of Reality in Computational Form Nick Rossiter Visiting Fellow with Michael Heather and Dimitrios Sisiaridis Computing, Engineering and Information Sciences Northumbria University, Newcastle NE2 1XE, UK Presentation at ANPA 33 Cambridge University 9-12 August 2012

Aristotle Aristotle coined the word 'categories' to describe a structure of classes Used as the title of one of the books of his treatise on logic, the Organon. This begun a 2,000 year history for the category to describe the structured level at the foundation of logic.

Symbolic Logic Diversion The study of logic diverted to the symbolic logic of set theory around 1900 So the concept of a category with classes at various levels was no longer easy to represent. For the elements for the set are independent of one another and a set cannot be a member of itself No inherent possibility to represent recursion nor relations other than by external functions.

Indispensable Categories Nevertheless the category has become an indispensable component for many disciplines and the concept is still developing today. It is the primary classification system for Wikipedia which itself has about 500 types of categories defined. With advances in information systems the concept of typing is an aspect of categories that has increased in importance.

Accepted Approaches to Category Theory In many areas work has centred around cartesian closed categories. Such areas include: Compiler design and evaluation Language analysis Database design Metaphysics

Starting Point Reality concerns some area of interest. The Universe of Discourse. Reality is a preorder with cycles, trees and lines

Orders in Set line a b c d tree a bc d preorder a b c d ef Tree is a special case of partial order where each element has only one parent. Preorder can include unrelated fragments. Sets are equipped with an order (as an add-on)

Orders in Categories Ordering is fundamental in category construction. Arrow is overloaded for many tasks Calculation as by function e.g. square Relationship e.g. marriage Ordering e.g. Class list on merit (line) Relationships as in family tree (partial order) Hours on an analogue clock/watch (preorder) – Directed graph, not acyclic – Connection of points in a topological space

Reality A general intensional category of type preorder A subcategory (not a partition) of the Universe Sometimes termed the Universe of Discourse With just one universe of discourse, will have an upper bound – The terminal object ┬ And a lower bound – The initial object ┴ Everything must be connected Fragments not permitted as outside bounds

Example Reality Category RLT T Terminal Object T Unique upper bound on category ┴ Initial Object ┴ Unique lower bound on category RLT

Properties of RLT  Rich enough to represent reality with all types of order inter-mingled  Provides an upper bound T, lower bound ┴ and connectivity  An entry point ┴ exists, so that it could potentially be addressed by an identity functor But  Not cartesian closed (no products)

Handling RLT computationally (best industry practice) In relational database, model cannot handle the great variety of orders directly Need to map to a collection of relations, maintaining the arrow dependencies Object-oriented database model is more versatile, with less adaption required Principle is that a single large cumbersome structure is unwieldy for updating, because not all the data may be available at the same time So the structure is fragmented

Fragmentation Take a simpler example: b c e a Initial object a Terminal object e Preorder on b,c,d d RLT

Universal Relation U Construct the universal relation U including all the objects a,b,c,d,e in RLT U contains all possible subsets of the objects in RLT Plus the dependency arrows from RLT

Example of Dependency Diagram – all possible projected subsets a,b,c a,bb,ca,c b a c Ø Ø Empty set This is example for 3 elements, requires a lot more space for 5 (32 to be precise!). For 10 elements would require 1024 members. RLT' ab c Relation a,b,c

a,b,c,d,e a,b b,cc,d d,bc,d,e b e a c d Arrows are projections Underlined are keys D (in U) RLT For earlier example RLT, project out a dependency diagram D in U, including all the arrows in RLT Relations are: a,b b,c c,d d,b c,d,e So you're now a database designer!

Keys as Entry Point For relations can introduce Keys (K) as initial entry point: K a b c d c,d K is lower bound NK is non-key NK collectively is upper bound b c d b e NK Could be tidied up, could replace d,b and c,d,e with d,b,e This is done through database normalisation

So what is being done by database designer RLT is not cartesian closed But U is cartesian closed: Has terminal object of Ø null Has products (replace ',' by 'x' e.g. 'a,b' is 'a x b') Has connectivity (exponentials) The initial object a,b,c,d,e, that is a x b x c x d x e, can be used as a unique entry point 1 U, the identity functor

D is also Cartesian Closed D is derived from U Containing some of its objects and some of its arrows So D is a subcategory of U D is also cartesian closed as it preserves limits and colimits with Initial object K (the product of the keys) Terminal object NK (the sum of the non-keys) The dual of any cartesian closed preorder, the cocartesian, is also closed, trivially.

LCCC In practice we use a variant of cartesian closed categories for detailed representation Locally cartesian closed category  Product is replaced by a relationship Product is all possible pairs  e.g. account number X borrower name (A X B) Relationship is those pairs that satisfy a particular context  e.g. account number X borrower name in the context of cash owed (A X C B) In category theory this is a pullback (with adjointness properties)

Pullback A B C A X C B πlπl πrπr ιlιl ιrιr C is A+B+C

Other areas of computation Machine architecture and processing Reality for architecture is very simple: Von Neumann – Serial (line ordering) Parallel – partial order Recursive – preorder

Trends in Computation Von Neumann approach still very popular. But used without refinement is very primitive. Parallel/recursive methods used to some extent now, for instance quad/dual processors. Good for heavy simple tasks e.g. video processing. Why does von Neumann continue?

Processing Languages A programming language provides facilities for looping and recursion on serial architecture. All languages now provide iteration and recursion except assemblers and machine code. Language compilation and processing is very complex, involving many preorders and partial orders, giving complex RLT categories. Theoretical work underpinning the languages is being done using locally cartesian closed categories (LCCC) at Cambridge and elsewhere.

Summary Real-world structures employed in computation are very complex, whether for handling the outside world or for internal purposes. Cartesian closed categories underpin the handling of such complexity. A particular variant, locally cartesian closed categories, has been found to be effective in detailed work.