Changes between Version 1 and Version 2 of PimoService


Ignore:
Timestamp:
02/13/06 19:05:52 (20 years ago)
Author:
fmittag
Comment:

short summary of the PimoService

Legend:

Unmodified
Added
Removed
Modified

  • PimoService

    v1 v2  
    11= PIMO Service = 
    22 
    3 (NOTE: This part of gnowsis is yet to be not only implemented, but thought up. Most of the things described here might be incorrect and change in the near future, since the Wikitology depends on many aspects maintained by many different developers. This page is intended to help synchronizing our thoughts and to get to a consense quickly. Corrections on this page are WANTED!) 
     3The PimoService is an implementation of the PIMO (see  
     4[http://www.dfki.uni-kl.de/~sauermann/2006/01-pimo-report/pimOntologyLanguageReport.html PIMO Technical Report]), which is an improved manifestation of the Wikitology idea. 
    45 
    5 The PIMO is a combination of four aspects: 
    6  * shared ontology (PIM) - a simple upper ontology for !PersonalInformationManagement 
    7  * MySKOS - my own tags, concepts, etc in a hierachical view 
    8  * MyOntology - my own classes, properties, instances 
    9  * MyWiki - a description of my thoughts using wikitext. each thought has a wiki-page 
     6It allows the user to create things, classes and properties in his personal information model and link them together or to other (external) resources and things. 
    107 
    11  (further description needed) 
    12  
    13 The main idea behind the shared ontology is to have a local copy of a shared ontology that represents the organizational structure, the personal information model (PIM). 
    14  
    15 When the user starts gnowsis for the first time, the public shared ontology is imported as a local copy inside the wikitology, so he doesn't need to start from scratch. All PIM classes become concepts in the local version, and subclasses of the PIM, for example john:IndividualPerson is a subclass of pimUpper:IndividualPerson. After the initialization, adding subclasses to classes does something. 
    16  
    17 The semantics needed for this wikitology are further discussed in the technical report by Leo (soon to appear). 
    18  
    19 = WikitologyGui = 
    20  
    21 All aspects of the !WikitologyService can be managed using the WikitologyGui. This user interface in the domain of Dominik Heim will allow the editing of concepts, etc. 
    22  
    23 = TODO = 
    24  * import the public shared ontology into !MyWikitology for more than one root concept 
    25  * update an existing local ontology 
    26  * import an ontology without conflicts, if there is already one 
    27  * how to manage the needed properties of the PIM concepts 
    28  
    29 = already working = 
    30  
    31  * import the public shared ontology with only one root concept into !MyWikitology 
    32  
    33 = currently under development = 
    34  
    35  * extract the import functionality into a separate class 
    36  * WikitologyGui for an easy handling of the API 
    37  
    38 = Future goals = 
    39  
    40  * synchronize changes in !MyOntology back to the public shared ontology 
     8some useful facts: 
     9 * While the given labels are preserved, the URIs may differ due to syntax restrictions. 
     10 * It is possible to create different things with the same name. 
     11 * It is NOT possible to create different classes with the same name.