Dear Ontolog Forum members and Ontology Summit 2015 planners,
Given my apparent tardiness and the urgency from the Summit planning schedule point of view, here is a quick but enthusiastic interlude from me. It is a mere interjection into the planned multi-part series of which this is Part II. (Part I is appended below.)
As a merely interim survey of key features, this series interlude is necessarily incomplete and therefore inconclusive. But it does touch on many of the vital aspects of the long-running project whose pursuance I am putting forward as at least a strawman Summit theme. It is also consistent with the various eventually abandoned series of posts on the Ontolog Forum by me over the years, as well as with my posts to the earlier SUO or Standard Upper Ontology list. The opening of Point 2 in Part I below referred you to one of those series from 2008, still highly pertinent here. So I do hope that I am beginning to convey the vast coherence of the full picture to at least some of you.
In advance, please try to forgive the element of breathlessness here, but I do sense that both the Ontology and the Trusted Identity worlds are right now particularly in need of some encouragement, some backbone and some muscle, some centrally meaningful impetus... Users deserve better from system architecture, and it is clear to me that to a significant degree there is a silver bullet of a kind, ready - with your inputs and even perhaps participation - to burst forth from the nicely-coherent set of mutually consistent features already evidently present here.
(I don’t think you need be unduly concerned by that apparently way-out claim, for as I shall indicate in the original Point 9 promised in Part I of this series (See below), a powerful awareness of the silver bullet anti-pattern in applied conceptualization was in fact the trigger to this project at its 1963 inception. Then in 1966 I characterized it as the Scylla syndrome, the many ways of falling victim to Scylla, the monster of tragic oversimplification in Homer’s Odyssey. And, incidentally, I thank the full and extensive Homeric perspective for the framework of the silver bullet claim, and the gradually accumulated confidence to assert it. But that’s for Point 4 in a later Part of this series.)
The claim to the requisite architectural qualities also for the Ontology and Trusted Identity worlds is nothing new to this project: since 1990 the existence of ever-new domains of applicability has been implicit in the project slogan, “Ride The Mainstream!” So it is highly significant, in a Karl Popper refutability kind of way, that the project was built on the right kind of foundation for addressing such modern problems too. For Trusted Identity (with privacy) has become perhaps the single most burning problem area for the real burgeoning of Social Apps, while IS Ontology is increasingly seen as disappointing the early expectations of a central rather than peripheral role in the information society. (For example, here I regard schema.org as playing a merely peripheral role.)
So, here are some of the uniquely key features or USPs of this alleged silver bullet. (Some of the many remaining gaps get some bare mention.) Though not evident here, the definitions are all interdependent, as is usual in axiomatic constructions (though to elaborate that aspect “fully” some metaphysical axioms have to be added).
1. A single top-level objective: to help people simplify complexity together. It is put forward as at least a high-level and sharable component of all self-critical ideologies.
2. Note, however, that the complex reality addressed includes the conceptualizing human mind itself, or themselves, each one with its own unique identity. I regard it as essential to include that full notion of identity in the technical picture, and regrettable though understandable that the IDESG explicitly limits its scope to a more modest notion of “digital identity”. So the picture here in TMA is of minds that can be supported in the expansion of their own self-awareness and self-identity through sharable though ever-evolving ontologies. There have to be important consequences here for education and the individual’s ability to co-evolve with own unique employment situations and possibilities.
3. An across-the-board recognition and exploitation of the notion of conceptualization as abstraction from reality, in a simplifying process.
4. A precise notion of the internal structure of ontologies, usually with fine layers of abstraction (or ignoring of deemed irrelevancies), each resulting ontology or inner-context applicable to a particular kind of situation or outer-context.
5. Hence a clear and precise handling of commonality and difference, whether between parties or between different times for the same party.
6. An extended (or “tweaked”) notion of the ontology as reusable component, with strictly-disciplined functions enabling the expressivity required for realworld apps, while yet enabling the arbitrarily-refined (or alternatively coarse-grained too) Principle of Least Privilege.
7. The outcome is an inversion of the usual roles: instead of large and undisciplined programs (or people) trying to deal with ontologies, we have ontologies delimiting and driving usually smaller and always well-delimited programs. (Beware my Humpty-Dumpty use of words there! But they are consistent with the other terms here.)
8. Hence we have a completely novel notion (as far as I am aware...) and implementation of the Generalized Object Model for object-orientation, recognizing the necessarily multi-type or ontology-level nature of most interesting component functionality.
9. To address the “cross-cutting concerns” that do not naturally fit the usual procedural OO mold and have led to Aspect-Oriented Programming or AOP, the functionality addressed by AOP’s ‘aspect weaver’ is covered naturally by the intrinsic structure and functioning of the TMA-canonical AOS introduced below.
10. Almost self-configuring composition of functionality, leading to the metaphorical notion of “Ontology Chemistry”, with entities as atoms but with stable semantics only in terms of ontologically-defined molecules.
11. And yet, the “is-ought problem” prevailing, human intentions or autonomous “speech acts” are recognized and choice promoted.
12. Together, the above invites the discovery and provision of variable levels of Standard Upper Ontology of an operational kind, concretized in a TMA-canonical AOS or Application Operating System (whose programming, at present in C, is still my Work-In-Progress for which I am seeking collaboration or takeover. (An IDESG colleague and I applied for one of the 2014 round of NSTIC Pilot grants to help bring the AOS to an alpha-test stage, ready for its own bootstrapping and further free market-based evolution for fuller scalability and the usual other qualities. We foresaw a 1-year project. But our application did not succeed this time.))
13. Time is integrated as a dimension much as it is in Special Relativity, for ontology-defined states are always transient, defined as event-triggered transformations from one ontology-defined viewpoint-state to another. (But these transformations are typically creative, with the interesting ones usually adding or losing meaning, so it is unclear to me whether Category Theory is usefully applicable here. And there’s Sub-challenge #1 to you!))
14. Since that conception threatens unmanageable complication, it is important to realize that there are often equivalents with very conventional data-processing operations, and patterns have long been evolved there. Their application is a meta-task, with reflective ontologies being very applicable. So of course their evolution is Sub-challenge #2 to you.
15. But what does ontology the philosophical discipline and product contribute? (A recent popular thread on the Ontolog Forum, “Ontology vs KR”, raised a related question.) Some of you may note that I have revised my earlier decision to avoid the very use of the word “ontology”, seeing how its imagined or supposed profundity can be abused by product marketeers. But I have realized that the reality of Being itself is an important issue, difficult though it is to narrow down what that wording actually means. For there is a very fundamentally important issue at stake, and it is implicit in the mention above of transformations between states. In any interaction or change there will be an invariant or at least covariant element as described by the concerned individuals’ most refined yet sharable ontology for the changing situation. This results in a very special definition of philosophical realism that perfectly integrates Being with Becoming. And growing the thus-discovered and hence usable commonality is promoted by the orthogonality or mutual independence of the dimensions or attributed involved. All that is rather crucial to the enormous extensibility of the picture in its foreseeably beneficial practice. And that loops us back to point 2 above.
But that is enough for this “interlude” if you are to read it at all before today’s brainstorming session. If you perhaps have the stomach for it still, we can during the session also consider some of the many practical issues involved in any Summit exercise involving this “strawman”. If not, I still hope to take the 9 planned points further, as set out in Part I reproduced below.
Thank you further...
From: ontolog-forum-bounces@xxxxxxxxxxxxxxxx [mailto:ontolog-forum-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Christopher Spottiswoode
Sent: 16 October 2014 16:45
To: '[ontolog-forum] '; 'Ontology Summit 2010 Organizing Committee'
Cc: 'Charles Palmer'
Subject: [ontolog-forum] A Summit 2015 strawman: Ontology as the basis of The Mainstream of Software Engineering and Social Apps (Part 1)
During the Ontology Summit 2015 brainstorming session last Thursday, and as you noted briefly at 10:05 in the chat extract below, I verbally made a proposal for a Summit topic addressing what I see as the opportunities for ontology in the elaboration of the White House’s NSTIC strategy. Ontology could be the key to a grand NSTIC success, while NSTIC opens enormous scope for applied ontology. I promised to set out the case more systematically to this list, so here is a first instalment, starting to build up to a motivation for inclusion of the topic in Summit 2015. As the subject-line above implies, there is a lot more to the proposal than “mere” NSTIC. So the practicality of the proposal is a major theme in what follows.
The immediate context is the unsnipped remainder below of the brainstorming session chat that you sent out, with some postscripta from me:
Chat transcript from room: summit_20141009
[09:27] MichaelGruninger: Welcome everyone to the Ontology Summit 2015 Community Brainstorming Session!
[10:05] MichaelGruninger: ChristopherSpottiswoode: Possible topic related to the activities of the National Strategy for Trusted Identities in Cyberspace
[10:06] Mark Underwood1: http://www.nist.gov/nstic/
[10:10] Ram D. Sriram1: Here is a link to an animated video of NSTIC: http://www.nist.gov/nstic/animation.html
[10:10] Mark Underwood1: https://www.idecosystem.org/
[CS postscript:] Some further links:
The original NSTIC founding document of 2011: http://www.whitehouse.gov/sites/default/files/rss_viewer/NSTICstrategy_041511.pdf
A recent introduction: http://www.c-span.org/video/?321145-1/communicators-jeremy-grant
[10:11] Ram D. Sriram1: Regarding NSTIC, I think you might want a more general topic about the role of ontologies in privacy and cybersecurity. Not clear whether we can get enough people to take about this.
[CS postscript:] Ram, yes indeed, I agree on the more general topic, as you will see throughout what follows. I may however assert once again that NSTIC/IDESG would stand to gain to a critical degree from a Summit deliverable as proposed here. The opening paragraph above qualified the anticipated effect as “key”. But the present proposal does not yet have the kind of maturity they and the market are looking for right now. Moreover, they are at present too preoccupied with short-term objectives for me to want to disturb them to the degree needed, though the ball is in my court at the moment. However, after several interactions and collaborations with them, at least some of them are well aware of my work and its potential value in an identity ecosystem. Hence my initiative here, working towards better preparedness and communicability later.
[10:40] MichaelGruninger: There seem to be four possible topics that have emerged from the discussion so far: 1) Applied Ontology Body of Knowledge; 2) Internet of Things; 3) Sociotechnical Aspects of Applied Ontology; 4) Artefacts
[10:43] MichaelGruninger: Decision: Identify one or two champions for each of the above potential topics. We will have a follow-up meeting sometime in November to select the topic
[10:44] MichaelGruninger: so that the Org Committee has time to prepare for the Pre-launch in december
[10:44] MichaelGruninger: 1) Applied Ontology Body of Knowledge. Champions: MatthewWest and KenBaclwaski
[10:45] MichaelGruninger: 2) Internet of Things. Champions: MarkUnderwood and RamSriram and JoelBender
[10:47] MichaelGruninger: 3) Sociotechnical Aspects of Applied Ontology. Champions: TerryLongstreth, ChristopherSpottiswoode
[10:48] MichaelGruninger: 4) Artefacts. Champions: LeoObrst
[10:50] LeoObrst: I'm also interested in topic (1)and (2).
[10:53] MichaelGruninger: Next meeting on November 6, 2014. Objective of this meeting will be the final selection of the Ontology Summit 2015 theme
[10:53] MichaelGruninger: We will also identify the Organizing Committee at that time
[CS postscript:] The entire NSTIC-related proposal fits comfortably within topic 3. Almost any other subject within topic 3 would benefit from this proposal’s perspectives, as I look forward to being able to show. Further, and as I mentioned during the session, topic 2 on IoT has core needs on the identity and access control fronts that this proposal addresses too. And this proposal has many fascinating implications re abstract artefacts, their emergence, use and supersession, including relevant archiving, which could be of interest to topic 4. Finally, the archiving-with-context facilities, which as you will see are rather core to the envisioned platform, could be of great help to any designer and deployer of topic 1’s BoK deliverables.
Brief introduction to the main points, with only points 1 and 2 started in this post (more instalments to follow):
1. If the NSTIC is to achieve its goals, Information System (IS) security urgently needs a revamp. It would follow from an appropriate conception of ontology, presented as a “minor tweak” of it in the NSTIC Security Working Group chat quoted below.
2. But such a revamp would also imply an ontology-based revamp of Software Engineering (SE). Hence the subject-line of this post. The point of departure here is a Pat Hayes talk from 2011, most relevantly on identity, asking why something so simple as “same as” is so hard.
3. The resolution of that hard issue (and enabler of Trusted Identities with privacy) lies in the socially-evolving hence always imperfect nature of knowledge. Hence the relevance to Social Apps, as also noted in the subject-line. The NSTIC-envisioned Identity Ecosystem (in its more evolved future form) will be a core aspect of that social scene. This is our inescapable world of the “bounded rationality” or situation- and context-dependence of economic and social actors.
4. Fortunately, there is a nicely-coherent collection of patterns and anti-patterns for our addressing and stepwise transcending of such imperfections. Bizarrely though understandably and usefully, they were collected millennia ago by Homer in the form of his Odyssey as a whole, as appropriate demythologization shows so accessibly. The epic poem’s venerable origins underscore the enduring quality and ubiquitous applicability of The (Homeric) Mainstream of our never-ending but ever-enticing joint conceptual simplification of our given complexity. (Hint: Homer is a fresher read on Being and Logos than all later philosophy!)
5. Those patterns’ modern realization will I expect be something not very unlike “Ontology Chemistry”, a proposed Software Engineering mechanism for architecting ontological components and fluently composing applications. The design of architecture and mechanism is naturally suited to the people-driven openness, scale and complexity of cyberspace and our lives in it. There are however a number of areas in the architecture and its fully scalable realization that call for the contributions of logicians and formal analysts. (The market bootstrapping product I have been working on is very much a product of a plain IS developer!)
6. The mechanism’s deployment would impressively facilitate identity management, privacy, access control, system resilience and other qualities core to NSTIC, so its credible prospect could soon put all NSTIC-related work on the right track for qualitatively better deliverables.
7. There is a practical, stepwise, migration path from the present towards the new dispensation envisioned. The free market may be expected to embark on it enthusiastically, as it will be more effective, practical, attractive and yet clearer than presently available alternatives.
8. I suggest that the Summit could usefully analyze the above plan, refine and elaborate it, and quite possibly be the catalyst in its eventual realization in the wild. A formal or informal Grand Challenge, for example, from the Summit could be the requisite impetus for such a transformation of Software Engineering, Information Systems and much future social activity. I reassure that I claim no IPR in any of this work. It will all be seen to be very Mainstream, in due course at least. The market will gradually either reject or reform and absorb all presently dominant “mainstreams”, for an inclusive and attractive, genuinely democratic future.
9. But if it is all so Mainstream, why has all the above not already taken place? Is the picture not a mere gleam in my seriously deluded eye? Some largely ad hominen SWOT analysis is offered in respect of myself. But at this stage, for this programmer on the ground, working in a bottom-up way, the top-down applicability of the Homeric epistemology and ontology is already proof enough of its well-foundedness and guarantee of its wide practicality. That will I hope become clear from point 4, on the usefully coherent unity of The (Homeric) Mainstream.
1. Information System (IS) security urgently needing a revamp
To set the scene, here is an extract from the chat at the Security Working Group meeting at the IDESG’s 3rd Plenary meeting held in Phoenix in February 2013 (at which I was one of the remote attendees, hence the UTC+2 times shown). It was my first non-trivial contribution to IDESG activities.
[18:09] ChristopherSpottiswoode: Here is a slightly amplified version of the proposal I have submitted for a Birds of a Feather session tomorrow:
[18:09] ChristopherSpottiswoode: Are the highly admirable NSTIC plans for identity not ignoring an elephant in the room?
The monstrous lack of reliable security in systems- and application-programming maybe needs to be sorted out before identity and privacy can be tackled on a comprehensive basis? For example, do present software architectures make it practical on the Internet to deeply implement the principle of least privilege? Or, how manageable and reliable are ACLs in the dynamic Internet environment? To summarize, there would still be plenty dangers after a malicious user, such as a man-in-the-middle or a spearphisher, or a dumb bona fide user, with an IDESG credential has stepped through the authentication door.
My take on that whole scene is that some quite easy but key tweaks to the notion of IS ontologies can enable a comprehensive component, system and application architecture that is at once epistemologically appropriate, industrial-strength RAD, and practically deployable. A surprisingly small project of the right kind could soon have that elephant fade away and make way for the realization of the NSTIC ideals. I am busy setting up a new website arguing for just such a project. I'll keep this list posted. But does the above, as it stands, make any sense to you?
[18:15] Charles Palmer (IBM): I agree with your thesis Christopher. However, some of us have been saying similar things for years ... start with a secure foundation, a "secure place to stand", before investing in all the higher level security capabilities. Perhaps due to market forces (which will work against a thorough certification regime like CC) and the vast existing base, these ideas have gone mostly unheeded.
[18:19] Charles Palmer (IBM): But I do agree with the "reliable systems" first approach, since improved reliability enables improved security.
[18:19] ChristopherSpottiswoode: Sure, Charles, legacy apps, data and mindsets would seem a problem. So maybe I should open on that subject by commenting that "Ride The Mainstream!" has been the slogan of this project since its outset.
[18:21] Charles Palmer (IBM): Indeed, and it is that same tide that will work against anything like CC for identity, which impacts time to market, product cycles, etc.
[18:21] ChristopherSpottiswoode: It's not just "reliable systems", it's more fundamental: it's a matter of the appropriate component and system architecture first.
[18:24] Charles Palmer (IBM): agreed
[End of chat extract].
As you can see on http://researcher.watson.ibm.com/researcher/view.php?person=us-ccpalmer, Charles Palmer seems outstandingly well qualified to comment on such matters.
2. The ontology-based revamp of Software Engineering
Pat Hayes in 2011 gave a talk entitled “On being the same as.” See http://www.udcds.com/seminar/2011/media/slides/UDCSeminar2011_PatrickHayes.pdf. (Thank you, Simon Spero, for pointing us to it, and to the recording of the talk itself, in an Ontolog Forum post now archived at http://ontolog.cim3.net/forum/ontolog-forum/2013-02/msg00050.html). The talk is subtitled “why something so simple is so hard.” And indeed, Pat does put his finger on a serious problem for machine inference in a variegated world with supposed equivalences between frames of reference.
Such a question might at first seem too abstruse to be relevant to software engineering. But here it represents the key opportunity for “The Mainstream Architecture for Common Knowledge” (TMA), that is the framework of this proposal. At the end of the talk Pat himself makes a good move in the right direction: the many non-SameAs identities for the “same thing” correspond to respective contexts.
But Pat has long chided those who try to exploit that concept for the inadequate definitions of context that they come up with. For example, in July 2013 on the Ontolog Forum, now archived at http://ontolog.cim3.net/forum/ontolog-forum/2013-07/msg00108.html, Hans Polzer put in one of his usual good pleas for building more on context. Its final sentence was:
[HP:] So the first order of business should be an ontology for describing context and scope assumptions.
Pat responded with characteristic brevity:
[PH:] And the trouble with *that* idea is, there are as many distinct notions of
"context" as there are people saying that we need to describe contexts.
The TMA notion of context was briefly introduced in my incomplete “MACK Basics” series of posts to the Ontolog Forum in Feb-April 2008 (“MACK” being the old name for TMA), in the 4th instalment now archived at http://ontolog.cim3.net/forum/ontolog-forum/2008-04/msg00109.html, with links to the prior instalments.
The 2nd instalment elicited discussion with Pat Hayes very much reminiscent of his 2011 talk re SameAs, and per-context identity - or personas! - is the gist of the resolution. Hence also great relevance to NSTIC issues, including basic prerequisites such as privacy and The Principle of Least Privilege that are at present so neglected by current architectures.
That final point coincidentally fits in nicely with Ram Sriram’s suggestion, at 10:11 in the chat transcript that made up my preface above, for a topic on “the role of ontologies in privacy and cybersecurity.” And indeed, the 2nd instalment was already in 2008, long prior to the 2011 launch of NSTIC, building up explicitly to the requisite qualities, promising:
“to address all aspects of application development within the business and general administrative world, and in an industrial-strength way despite vexed issues such as identity, privacy, security, data integrity, processing correctness and application resilience and evolvability in general.”
The above is already too much for a single post, so I’ll drop this in your laps while I prepare some more material, including on how developments after those 2008 posts have greatly confirmed their direction, from both theoretical and practical points of view. My plan is set out in the 9 points listed above, but I would be delighted to alter it in response to any feedback from you at this point. (Meanwhile please do remember that I will be addressing the issues of point 9!)