Link to this page
Menelas Project Top-Level Ontology
Acronym | TOP-MENELAS |
Visibility | Public |
Description | The two main goals MENELAS contributes to are to (i) Provide better account of and better access to medical information through natural languages in order to help physicians in their daily practice, and to (ii) Enhance European cooperation by multilingual access to standardised medical nomenclatures. The major achievements of MENELAS are the realisation of its two functional systems: (i) The Document Indexing System encodes free text PDSs into both an internal representation (a set of Conceptual Graphs) and international nomenclature codes (ICD-9-CM). Instances of the Document Indexing System have been realised for French, English and Dutch ; (ii) The Consultation System allows users to access the information contained in PDSs previously indexed by the Document Indexing System. The test domain for the project was coronary diseases. The existing prototype shows promising results for information retrieval from natural language PDSs and for automatically encoding PDSs into an existing classification such as ICD-9-CM. A set of components, tools, knowledge bases and methods has also been produced by the project. These include language-independent ontology and models for the domain of coronary diseases; conceptual description of the relevant ICD-9-CM codes. This ontology includes a top-ontology, a top-domain ontology and a domain ontology (Coronay diseases surgery). The menelas-top ontology here is the part of the whole ontology without any reference to medical domain. |
Status | Beta |
Format | OWL |
Contact | Jean Charlet, jean.charlet@upmc.fr |
Version | Released | Uploaded | Downloads |
---|---|---|---|
1.0 (Parsed, Indexed, Metrics, Annotator) | 01/26/2018 | 01/26/2018 | OWL | CSV | RDF/XML | Diff |
1.0 (Archived) | 01/25/2018 | 01/25/2018 | OWL | Diff |
1.0 (Archived) | 01/25/2018 | 01/24/2018 | OWL | Diff |
1.2 (Archived) | 07/03/2013 | 01/22/2018 | OWL | Diff |
1.1 (Archived) | 07/03/2013 | 07/15/2013 | OWL | Diff |
1.1 (Archived) | 07/03/2013 | 07/04/2013 | OWL |
1.1 (Archived) | 07/03/2013 | 07/04/2013 | OWL |
1 (Archived) | 01/14/2013 | 01/14/2013 | OWL |
more... |
No views of TOP-MENELAS available
Classes | 458 |
Individuals | 0 |
Properties | 298 |
Maximum depth | 11 |
Maximum number of children | 16 |
Average number of children | 3 |
Classes with a single child | 15 |
Classes with more than 25 children | 0 |
Classes with no definition | 264 |
Id | http://www.limics.fr/ontologies/menelastop#PseudoObject
http://www.limics.fr/ontologies/menelastop#PseudoObject
|
---|---|
Preferred Name | pseudo object |
Definitions |
a pseudo_object is like an objet without being a real object. That is, it has most of the characteristics of what is an individuated object, but not all. Namely, pseudo_objects are countable, discrete objects, and most of the time, we want to think of them as objects.
However, pseudo_objects need other objects to exist; they no ontological autonomy. While this fact can be considered as applicable for every object except God (cf. the spinozian definition of s substance), the ontological dependency is unavoidable for the pseudo_objects while it can be neglected for the others, we call then real objects.
For example, a pseudo_object looses its consistency when it is separated of what it depends on. An abdomen is not an abdomen when it is no longer in the body; one cannot do a transplantation of an abdomen. However, a heart, or a liver is a real object because they can be transplanted. A liver, separated of the body is alwase a liver: it is the reason why transplantation is possible.
Finally, every pseudo_object is a collection of physical objects that are related to eachother in such a manner that one can speak of the collection as an object. That is, there is a cohesion principle that provides the collection with the coherence and the unity that make it like an object.
The splitting principle consists in the kind of cohesion principle. One distinguishes first the systemic principle, that relates objects by their functions to build a global system, considered as an object. For example, the sociologic principle relates objects by their social function: this will a subnode of systemic_object. Finally, morphologic principle relates objects by their position in the real space, so that the collection has the form of an object.
Basically, a pseudo object is a system of physical objects in which every physical object plays a role. Kinds of pseudo objects correspond then to the kinds of role and system.
Pseudo-object can have a location, and defines a region. It corresponds to the place where the real objects that participate to the pseudo object have the functionalities between eachother that constitute the pseudo object.
[pseudo_object: _x]-
(component_of)<--[real_object]
%
|
Type | http://www.w3.org/2002/07/owl#Class |
All Properties
definition | a pseudo_object is like an objet without being a real object. That is, it has most of the characteristics of what is an individuated object, but not all. Namely, pseudo_objects are countable, discrete objects, and most of the time, we want to think of them as objects. However, pseudo_objects need other objects to exist; they no ontological autonomy. While this fact can be considered as applicable for every object except God (cf. the spinozian definition of s substance), the ontological dependency is unavoidable for the pseudo_objects while it can be neglected for the others, we call then real objects. For example, a pseudo_object looses its consistency when it is separated of what it depends on. An abdomen is not an abdomen when it is no longer in the body; one cannot do a transplantation of an abdomen. However, a heart, or a liver is a real object because they can be transplanted. A liver, separated of the body is alwase a liver: it is the reason why transplantation is possible. Finally, every pseudo_object is a collection of physical objects that are related to eachother in such a manner that one can speak of the collection as an object. That is, there is a cohesion principle that provides the collection with the coherence and the unity that make it like an object. The splitting principle consists in the kind of cohesion principle. One distinguishes first the systemic principle, that relates objects by their functions to build a global system, considered as an object. For example, the sociologic principle relates objects by their social function: this will a subnode of systemic_object. Finally, morphologic principle relates objects by their position in the real space, so that the collection has the form of an object. Basically, a pseudo object is a system of physical objects in which every physical object plays a role. Kinds of pseudo objects correspond then to the kinds of role and system. Pseudo-object can have a location, and defines a region. It corresponds to the place where the real objects that participate to the pseudo object have the functionalities between eachother that constitute the pseudo object. a pseudo_object is like an objet without being a real object. That is, it has most of the characteristics of what is an individuated object, but not all. Namely, pseudo_objects are countable, discrete objects, and most of the time, we want to think of them as objects. However, pseudo_objects need other objects to exist; they no ontological autonomy. While this fact can be considered as applicable for every object except God (cf. the spinozian definition of s substance), the ontological dependency is unavoidable for the pseudo_objects while it can be neglected for the others, we call then real objects. For example, a pseudo_object looses its consistency when it is separated of what it depends on. An abdomen is not an abdomen when it is no longer in the body; one cannot do a transplantation of an abdomen. However, a heart, or a liver is a real object because they can be transplanted. A liver, separated of the body is alwase a liver: it is the reason why transplantation is possible. Finally, every pseudo_object is a collection of physical objects that are related to eachother in such a manner that one can speak of the collection as an object. That is, there is a cohesion principle that provides the collection with the coherence and the unity that make it like an object. The splitting principle consists in the kind of cohesion principle. One distinguishes first the systemic principle, that relates objects by their functions to build a global system, considered as an object. For example, the sociologic principle relates objects by their social function: this will a subnode of systemic_object. Finally, morphologic principle relates objects by their position in the real space, so that the collection has the form of an object. Basically, a pseudo object is a system of physical objects in which every physical object plays a role. Kinds of pseudo objects correspond then to the kinds of role and system. Pseudo-object can have a location, and defines a region. It corresponds to the place where the real objects that participate to the pseudo object have the functionalities between eachother that constitute the pseudo object. [pseudo_object: _x]- (component_of)<--[real_object] % |
---|---|
prefLabel | pseudo object
|
comment | [pseudo_object: _x]-
(component_of)<--[real_object]
%
|
dws | real object have all properties realized.
|
dwp | some properties a physical object can have cannot be realized -> is not an object in the full meaning.
|
prefixIRI | PseudoObject
|
menelastopCGRepresentation | [pseudo_object: _x]-
(component_of)<--[real_object]
%
|
subClassOf | |
sws | which property is always realized, and which is not.
|
swp | has a localisation: defines a spatial area.
|
type |
Delete | Subject | Author | Type | Created |
---|---|---|---|---|
No notes to display |
- Problem retrieving properties:
Notes
Add NCBO Web Widgets to your site for TOP-MENELAS
Widget type | Widget demonstration |
---|---|
|
Step 2: Follow the Instructions
For more help visit NCBO Widget Wiki |
|
Example 1 (start typing the class name to get its full URI)
Example 2 (get the ID for a class) Example 3 (get the preferred name for a class) Step 2: Follow the Instructions
For more help visit NCBO Widget Wiki |
|
Step 2: Follow the InstructionsCopy the code below and paste it to your HTML page <iframe frameborder="0" src="/widgets/visualization?ontology=TOP-MENELAS&class=http%3A%2F%2Fwww.limics.fr%2Fontologies%2Fmenelastop%23Watt&apikey=YOUR_API_KEY"></iframe> For more help visit NCBO Widget Wiki |
|
Step 2: Follow the InstructionsCopy the code below and paste it to your HTML page <link rel="stylesheet" type="text/css" href="/widgets/jquery.ncbo.tree.css"> <script src="/widgets/jquery.ncbo.tree-2.0.2.js"></script> <div id="widget_tree"></div> var widget_tree = $("#widget_tree").NCBOTree({ apikey: "YOUR_API_KEY", ontology: "TOP-MENELAS" }); You can also view a detailed demonstration For more help visit NCBO Widget Wiki |