TOC PREV NEXT INDEX

CNLPA-Ontology Modelling

1 CNLPA-ONTOLOGY-object

This type of modelling the CNLPA-ontology is focussed on its classes called objects in contrast to a later more process-oriented modelling proposed in the CNLPA-ontology-process. A step further towards a polycontextural modelling is introduced by the CNLPA-ontology-polylogic.

All three approaches are designed along the lines of the SHOE-CS Department-ontology.

<HTML>

<HEAD>

<!-- Here we indicate that this document is conformant with SHOE 1.0 -->

<META HTTP-EQUIV="SHOE" CONTENT="VERSION=1.0">

<TITLE> Our CNLPA Ontology-object </TITLE>

</HEAD>

<BODY>

<!-- Here we declare the ontology's name and version -->

<ONTOLOGY ID=cnlpa-ontology-object" VERSION="1.0">

<!-- Here we declare that we're borrowing from another ontology -->

<USE-ONTOLOGY ID="base-ontology" VERSION="1.0" PREFIX="base"

URL="http://www.cs.umd.edu/projects/plus/SHOE/base.html">

<!-- Here we lay out our category hierarchy -->

<DEF-CATEGORY NAME="Organization" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Person" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Publication" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Seminars" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Cooperations" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Buildings" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="ResearchGroup" ISA="Organization">

<DEF-CATEGORY NAME="Department" ISA="Organization">

<DEF-CATEGORY NAME="Worker" ISA="Person">

<DEF-CATEGORY NAME="Faculty" ISA="Worker">

<DEF-CATEGORY NAME="Trainer" ISA="Worker">

<DEF-CATEGORY NAME="AdministrativeStaff" ISA="Worker">

<DEF-CATEGORY NAME="Teilnehmer" ISA="Person">

<DEF-CATEGORY NAME="Secretary" ISA="AdministrativeStaff">

<DEF-CATEGORY NAME="Chair" ISA="AdministrativeStaff Trainer">

<DEF-CATEGORY NAME="Owner" ISA="CHAIR">

<DEF-CATEGORY NAME="unpublishPublication" ISA="Publication">

<DEF-CATEGORY NAME="publishPublication" ISA="Publication">

<DEF-CATEGORY NAME="printPublication" ISA="Publication">

<DEF-CATEGORY NAME="audioPublication" ISA="Publication">

<DEF-CATEGORY NAME="videoPublication" ISA="Publication">

<DEF-CATEGORY NAME="webPublication" ISA="Publication">

<DEF-CATEGORY NAME="researchPublication" ISA="Publication">

<DEF-CATEGORY NAME="Office" ISA="Building">

<DEF-CATEGORY NAME="Academy" ISA="Building">

RULES:

<!-- And now we lay out our relationships between categories -->

<DEF-RELATION NAME="advisor">

<DEF-ARG POS="1" TYPE="regularTeilnehmer">

<DEF-ARG POS="2" TYPE="Trainer">

</DEF-RELATION>

<DEF-RELATION NAME="ausbilder">

<DEF-ARG POS="1" TYPE="Teilnehmer">

<DEF-ARG POS="2" TYPE="Faculty">

</DEF-RELATION>

<DEF-RELATION NAME="member">

<DEF-ARG POS="1" TYPE="Organization">

<DEF-ARG POS="2" TYPE="Person">

</DEF-RELATION>

<DEF-RELATION NAME="publicationAuthor">

<DEF-ARG POS="1" TYPE="Publication">

<DEF-ARG POS="2" TYPE="Person">

</DEF-RELATION>

<!-- Lastly, we lay out our other relationships -->

<DEF-RELATION NAME="publicationDate">

<DEF-ARG POS="1" TYPE="Publication">

<DEF-ARG POS="2" TYPE=".DATE">

</DEF-RELATION>

<DEF-RELATION NAME="age">

<DEF-ARG POS="1" TYPE="Person">

<DEF-ARG POS="2" TYPE=".NUMBER">

</DEF-RELATION>

<DEF-RELATION NAME="name">

<DEF-ARG POS="1" TYPE="base.SHOEEntity">

<DEF-ARG POS="2" TYPE=".STRING">

</DEF-RELATION>

addressStreet(Address, .STRING)

addressCity(Address, .STRING)

addressState(Address, .STRING)

addressZip(Address, .STRING)

</ONTOLOGY>

</BODY>

</HTML>

Constants

Constants are used to identify instances that may be commonly used with an ontology. In this section, each constant is grouped under its category.

Gender:

Male

Female

FACTS:

PERSONS: {Klaus, Susanne, Irmi, Robert, Egbert, ...}

Publication-TITLES

Publication-Dates

Seminar-Titles

Seminar-Dates

Seminar-Locations

Name-of-Cooperations-Partners

etc.

CNLPA-ontology as a Mindmap (Grochowiak, Stein)



2 CNLPA-ONTOLOGY-process

This modelling approach is focussing on the activities, behaviors, short processes of the organization CNLPA. Therefore, the base-ontology of SHOE has to be changed and augmented with processual categories allowing categoreis like Activity, Duration, Location and Personship as processes.

<HTML>

<HEAD>

Main Classes of Mindmap:

<DEF-CATEGORY NAME="Organization" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Person" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Publication" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Seminars" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Cooperations" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Buildings" ISA="base.SHOEEntity">

The Mindmap modelling is presupposing facts and relations about chronological dates, linguistic strings and numbers etc. which are modelled in the base-ontology

<USE-ONTOLOGY ID="base-ontology" VERSION="1.0" PREFIX="base"

URL="http://www.cs.umd.edu/projects/plus/SHOE/base.html">

<!-- Here we indicate that this document is conformant with SHOE 1.0 -->

<META HTTP-EQUIV="SHOE" CONTENT="VERSION=1.0">

<TITLE> Our CNLPA Ontology-process </TITLE>

</HEAD>

<BODY>

<!-- Here we declare the ontology's name and version -->

<ONTOLOGY ID=cnlpa-ontology-process" VERSION="1.0">

<!-- Here we declare that we're borrowing from another ontology -->

<USE-ONTOLOGY ID="base-ontology" VERSION="1.0" PREFIX="base"

URL="http://www.cs.umd.edu/projects/plus/SHOE/base.html">

<!-- Here we lay out our category hierarchy -->

<DEF-CATEGORY NAME="Activity" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Duration" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Locating" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Personship" ISA="base.SHOEEntity">

<DEF-CATEGORY NAME="Publishing" ISA="Activity">

<DEF-CATEGORY NAME="Teaching" ISA="Activity">

<DEF-CATEGORY NAME="Cooperating" ISA="Activity">

<DEF-CATEGORY NAME="Advising" ISA="Activity">

<DEF-CATEGORY NAME="Coaching" ISA="Activity">

<DEF-CATEGORY NAME="Administrating" ISA="Activity">

<DEF-CATEGORY NAME="Ownership" ISA="Activity">

<DEF-CATEGORY NAME="Membership" ISA="Activity">

<DEF-CATEGORY NAME="Person" ISA="Personship">

<DEF-CATEGORY NAME="Housing" ISA="Location">

<DEF-CATEGORY NAME="permanent" ISA="Duration">

<DEF-CATEGORY NAME="temporary" ISA="Duration">

<DEF-CATEGORY NAME="weekend" ISA="Duration">

<DEF-CATEGORY NAME="term" ISA="Duration">

<DEF-CATEGORY NAME="Cooperation" ISA="Activity">

<DEF-CATEGORY NAME="Zertificating" ISA="Advising">

<DEF-CATEGORY NAME="Publishing" ISA="Person">

<DEF-CATEGORY NAME="unpublishedPublication" ISA="Publishing">

<DEF-CATEGORY NAME="publishPublication" ISA="Publishing">

<DEF-CATEGORY NAME="printPublication" ISA="Publishing">

<DEF-CATEGORY NAME="audioPublication" ISA="Publishing">

<DEF-CATEGORY NAME="videoPublication" ISA="Publishing">

<DEF-CATEGORY NAME="webPublication" ISA="Publishing">

<DEF-CATEGORY NAME="researchPublication" ISA="Publishing">

<DEF-CATEGORY NAME="webPublication" ISA="Publishing">

<DEF-CATEGORY NAME="Books" ISA="printPublication">

<DEF-CATEGORY NAME="Article" ISA="printPublication">

<DEF-CATEGORY NAME="Video" ISA="videoPublication">

<DEF-CATEGORY NAME="Audio" ISA="audioPublication">

<DEF-CATEGORY NAME="Webpage" ISA="webPublication">

<DEF-CATEGORY NAME="Seminars" ISA="Teaching">

<DEF-CATEGORY NAME="Busines-Seminar" ISA="Seminar">

<DEF-CATEGORY NAME="Hypnosis-Seminar" ISA="Seminar">

<DEF-CATEGORY NAME="NLP-Seminar" ISA="Seminar">

<DEF-CATEGORY NAME="Family-Seminar" ISA="Seminar">

<DEF-CATEGORY NAME="In-House-Seminar" ISA="Seminar">

<DEF-CATEGORY NAME="Office" ISA="Housing">

<DEF-CATEGORY NAME="Office" ISA="permanent">

<DEF-CATEGORY NAME="Academy" ISA="Housing">

<DEF-CATEGORY NAME="Academy" ISA="permanent">

<DEF-CATEGORY NAME="Seminar-House" ISA="Housing">

<DEF-CATEGORY NAME="Seminar-House" ISA="temporary">

<DEF-CATEGORY NAME="Client" ISA="Coaching">

<DEF-CATEGORY NAME="Student" ISA="Teaching">

<DEF-CATEGORY NAME="gradStudent" ISA="Zertificating">

<DEF-CATEGORY NAME="Trainer" ISA="Teaching">

<DEF-CATEGORY NAME="Office-Worker" ISA="Administrating">

RULES:

<DEF-RELATION NAME="publicationAuthor">

<DEF-ARG POS="1" TYPE="Publishing">

<DEF-ARG POS="2" TYPE="Person">

</DEF-RELATION>

<DEF-RELATION NAME="advisor">

<DEF-ARG POS="1" TYPE="gradStudent">

<DEF-ARG POS="2" TYPE="Trainer">

</DEF-RELATION>

<DEF-RELATION NAME="member">

<DEF-ARG POS="1" TYPE="Membership">

<DEF-ARG POS="2" TYPE="Person">

</DEF-RELATION>

<DEF-RELATION NAME="age">

<DEF-ARG POS="1" TYPE="Person">

<DEF-ARG POS="2" TYPE=".NUMBER">

</DEF-RELATION>

<DEF-RELATION NAME="name">

<DEF-ARG POS="1" TYPE="base.SHOEEntity">

<DEF-ARG POS="2" TYPE=".STRING">

</DEF-RELATION>

</ONTOLOGY>

</BODY>

</HTML>

FACTS:

PERSON: {Klaus, Susanne, Irmi, Robert, Egbert, ...}

Publication-TITLES

Publication-Dates

Seminar-Titles

Seminar-Dates

Seminar-Locations

Name-of-Cooperations-Partners

etc.

3 CNLPA-ONTOLOGY-metapattern

<- The metapattern approach is a intermediary paradigm between the process and the contextural approach. It will be developed later.->

CNLPA:

ownership

personship

publishing

training

cauching

cooperating

administrating

advising

4 CNLPA-ONTOLOGY-polylogic

<HTML>

<HEAD>

<!-- Here we indicate that this document is conformant with SHOE 1.0 ; which surely is not the case at all!!-->

<META HTTP-EQUIV="SHOE" CONTENT="VERSION=1.0">

<TITLE> Our CNLPA Ontology-polylogic </TITLE>

</HEAD>

<BODY>

<!-- Here we declare the ontology's name and version -->

<POLY-ONTOLOGY ID=cnlpa-ontology-polylogic" VERSION="1.0">

<!-- Here we declare that we're borrowing from another ontology -->

<USE-ONTOLOGY ID="contexture00_base-ontology" VERSION="1.0" PREFIX="base"

URL="http://www.cs.umd.edu/projects/plus/SHOE/base.html">

<!-- Here we declare that we're borrowing from another ontology useful for personal data-->

<USE-ONTOLOGY ID="contexture01_personal-ont" VERSION="1.0" PREFIX="personal"

URL="http://www.cs.umd.edu/projects/plus/SHOE/onts/index.html#person">

<!-- Here we we lay out our poly-contextural ontology -->

<USE-ONTOLOGY ID="contexture1_activity-ont" ---> Fictional!!

<USE-ONTOLOGY ID="contexture2_duration-ont" ---> Fictional!!

<USE-ONTOLOGY ID="contexture3_location-ont" ---> Fictional!!

<USE-ONTOLOGY ID="contexture4_personship-ont" ---> Fictional!!

< From object to process modelling, the poly-contextural modelling introduces a new step which goes beyond the process model. The used ontologies are not further organized vertically, but horizontally, building a heterarchic organization. This can only be considered as an analogy to what has to be done and not as polycontextural modelling as such. ->.

< As a consequence the SHOE's base-ontology, contexture00, is no longer in the functionality as a root, but put in parallel together with other neighboring ontologies, called contextures. The terminology <contexture1_base.SHOEEntity> is therefore quite fictional. >

<Mediate-Contextures Contexture00,....,Contexture 4>

!!! <!-- Here we lay out our poly-contextural-category HETERARHY --> !!!

<DEF-CONTEXTURE NAME="Activity" ISA="contexture1_base.SHOEEntity">

<DEF-CONTEXTURE NAME="Duration" ISA="contexture2_base.SHOEEntity">

<DEF-CONTEXTURE NAME="Locating" ISA="contexture3_base.SHOEEntity">

<DEF-CONTEXTURE NAME="Personship" ISA="contexture4_base.SHOEEntity">

<!-- Here we lay out our mono-contextural-category HIERARCHY of each contexture-->

<DEF-CATEGORY NAME="Publishing" ISA="contexture1_base.SHOEEntity">

<DEF-CATEGORY NAME="Teaching" ISA="contexture1_base.SHOEEntity">

<DEF-CATEGORY NAME="Cooperating" ISA="contexture1_base.SHOEEntity">

<DEF-CATEGORY NAME="Advising" ISA="contexture1_base.SHOEEntity">

<DEF-CATEGORY NAME="Coaching" ISA="contexture1_base.SHOEEntity">

<DEF-CATEGORY NAME="Administrating" ISA="contexture1_base.SHOEEntity">

<DEF-CATEGORY NAME="Ownership" ISA="contexture1_base.SHOEEntity">

<DEF-CATEGORY NAME="Membership" ISA="contexture1_base.SHOEEntity">

<DEF-CATEGORY NAME="Timing" ISA="contexture2_base.SHOEEntity">

<DEF-CATEGORY NAME="Housing" ISA="contexture3_base.SHOEEntity">

<DEF-CATEGORY NAME="Person" ISA="contexture4_base.SHOEEntity">

<DEF-CATEGORY NAME="male" ISA="Person">

<DEF-CATEGORY NAME="female" ISA="Person">

<DEF-CATEGORY NAME="permanent" ISA="Timing">

<DEF-CATEGORY NAME="temporary" ISA="Timing">

<DEF-CATEGORY NAME="weekend" ISA="Timing">

<DEF-CATEGORY NAME="term" ISA="Timing">

< Chair belongs at once to 3 different contoxtures and their ontologies!!

<DEF-CATEGORY NAME="CHAIR" ISA="Ownership">

<DEF-CATEGORY NAME="CHAIR" ISA="Person">

<DEF-CATEGORY NAME="CHAIR" ISA="Administrating">

<DEF-CATEGORY NAME="Zertificating" ISA="Advising">

<DEF-CATEGORY NAME="Practionar" ISA="Zertificating">

<DEF-CATEGORY NAME="Master" ISA="Zertificating">

<DEF-CATEGORY NAME="Trainer" ISA="Zertificating">

<DEF-CATEGORY NAME="MasterTrainer" ISA="Zertificating">

<DEF-CATEGORY NAME="Guest-Trainer" ISA="Teaching">

<DEF-CATEGORY NAME="Publishing" ISA="Person">

<DEF-CATEGORY NAME="unpublishedPublication" ISA="Publishing">

<DEF-CATEGORY NAME="publishedPublication" ISA="Publishing">

<DEF-CATEGORY NAME="Advertising" ISA="Publishing">

<DEF-CATEGORY NAME="printPublication" ISA="Publishing">

<DEF-CATEGORY NAME="audioPublication" ISA="Publishing">

<DEF-CATEGORY NAME="videoPublication" ISA="Publishing">

<DEF-CATEGORY NAME="webPublication" ISA="Publishing">

<DEF-CATEGORY NAME="researchPublication" ISA="Publishing">

<DEF-CATEGORY NAME="webPublication" ISA="Publishing">

<DEF-CATEGORY NAME="Books" ISA="printPublication">

<DEF-CATEGORY NAME="Article" ISA="printPublication">

<DEF-CATEGORY NAME="Video" ISA="videoPublication">

<DEF-CATEGORY NAME="Audio" ISA="audioPublication">

<DEF-CATEGORY NAME="CNLPA-Web Site" ISA="webPublication">

<DEF-CATEGORY NAME="NLP Wissen" ISA="webPublication">

<DEF-CATEGORY NAME="Innernet" ISA="webPublication">

<DEF-CATEGORY NAME="Techno.net" ISA="webPublication">

<DEF-CATEGORY NAME="Seminars" ISA="Teaching">

<DEF-CATEGORY NAME="Busines-Seminar" ISA="Seminar">

<DEF-CATEGORY NAME="Managment-Seminar" ISA="Seminar">

<DEF-CATEGORY NAME="Hypnosis-Seminar" ISA="Seminar">

<DEF-CATEGORY NAME="NLP-Seminar" ISA="Seminar">

<DEF-CATEGORY NAME="Family-Seminar" ISA="Seminar">

<DEF-CATEGORY NAME="In-House-Seminar" ISA="Seminar">

<DEF-CATEGORY NAME="Office" ISA="Housing">

<DEF-CATEGORY NAME="Academy" ISA="Housing">

<DEF-CATEGORY NAME="Seminar-House" ISA="Housing">

<DEF-CATEGORY NAME="Furniture" ISA="Housing">

<DEF-CATEGORY NAME="Chair" ISA="Furniture">

<DEF-CATEGORY NAME="Table" ISA="Furniture">

<DEF-CATEGORY NAME="Client" ISA="Coaching">

<DEF-CATEGORY NAME="Student" ISA="Teaching">

<DEF-CATEGORY NAME="gradStudent" ISA="Zertificating">

<DEF-CATEGORY NAME="Trainer" ISA="Teaching">

<DEF-CATEGORY NAME="Office-Worker" ISA="Administrating">

<DEF-CATEGORY NAME="Cleaner" ISA="Administrating">

<DEF-RENAME >

< specifies a local name for a concept from any extended ontology. >

<DEF-RENAME > CHAIR to Seat

<DEF-RENAME > CHAIR to AcademyHead

<DEF-RENAME > CHAIR to CoffeBar

RELATIONS:

< NOTE: In SHOE it is not possible to specify subsuming categories for a category defined in another ontology.

In contrast to the mono-contextural situation, the poly-ontological apprach has to mediate between different ontologies.

Therefore we can define some conditions in one contexture containing its own logic and also in another contexture containing its own other logic.>

< Intra-contextural relations (based on FOL) >

<DEF-RELATION NAME="publicationAuthor">

<DEF-ARG POS="1" TYPE="Publishing">

<DEF-ARG POS="2" TYPE="Person">

</DEF-RELATION>

<trans-contextural relations (based on poly-contextural logics)>

<This rule has to be transformed into a poly-contextural relation>

<DEF-RELATION NAME="publicationAuthor"> between Contexture4 and Contexture1

<DEF-ARG POS="1" TYPE="Publishing"> of Contexture1

<DEF-ARG POS="2" TYPE="Person"> of Contexture4

</DEF-RELATION>

<DEF-RELATION NAME="age">

<DEF-ARG POS="1" TYPE="Person"> of Contexture4

<DEF-ARG POS="2" TYPE=".NUMBER"> of Contexture0

</DEF-RELATION>

<DEF-RELATION NAME="name">

<DEF-ARG POS="1" TYPE="base.SHOEEntity"> of Contexture0

<DEF-ARG POS="2" TYPE=".STRING"> of Contexture0

</DEF-RELATION>

<DEF-RELATION NAME="tenured">

<DEF-ARG POS="1" TYPE="Trainer">

<DEF-ARG POS="2" TYPE=".TRUTH">

</DEF-RELATION>

<DEF-RELATION NAME="object-age">

<DEF-ARG POS="1" TYPE="Furniture"> of Contexture3

<DEF-ARG POS="2" TYPE=".NUMBER"> of Contexture0

</DEF-RELATION>

</ONTOLOGY>

</BODY>

</HTML>

FACTS in Contextures

person(Grochowiak)

male, female

permanent, temporary

weekend, term

Inference-RULES:

< -Inference rules have to be distributed over different contextures. There is not a single dominating inferenz rule ruling all contextures in the same sense. Distributed inferenz rules can even be differently defined, depending on the intra-contextural structure of the distributed ontology. ->

< - Mono-contextural case:>

<DEF-INFERENCE DESCRIPTION="Transitivity of Suborganizations">

<INF-IF>

<RELATION NAME="subOrganization">

<ARG POS="FROM" VALUE="x" USAGE="VAR">

<ARG POS="TO" VALUE="y" USAGE="VAR">

</RELATION>

and

<RELATION NAME="subOrganization">

<ARG POS="FROM" VALUE="y" USAGE="VAR">

<ARG POS="TO" VALUE="z" USAGE="VAR">

</RELATION>

</INF-IF>

< - Poly-contextural case as an example ->

poly-<DEF-INFERENCE DESCRIPTION="Transitivity of -sub-----">

poly-<INF-IF>

poly-<RELATION NAME=" sub-------">

Contexture1: <ARG POS="FROM" VALUE="x" USAGE="VAR">

Contexture1 and contexture2: <ARG POS="TO" VALUE="y" USAGE="VAR">

</RELATION>

et.et.et

poly-<RELATION NAME=" sub-----">

Contexture2: <ARG POS="FROM" VALUE="y" USAGE="VAR">

Contexture3: <ARG POS="TO" VALUE="z" USAGE="VAR">

</RELATION>

</INF-IF>

<- But without contradiction it could also be an intransitivity relation- >

<RELATION NAME=" sub-----">

Contexture2: <ARG POS="FROM" VALUE="z" USAGE="VAR">

Contexture3: <ARG POS="TO" VALUE="y" USAGE="VAR">

</RELATION>

QUERIES

Query-types

"mono-contextural search"

polycontextural parallel search

polycontextural multiple parallel search

Cluster questions and question clusters


ThinkArt Lab
TOC PREV NEXT INDEX