Skip to main content
About Us
Funding Sources
Personnel
Projects
Services
Publications
Old Site
You are here
Home
»
Foundational Model of Anatomy
»
Current Status
» Current Status
Node export of Current Status
Primary tabs
View
Node export
(active tab)
Node export code
[{"vid":"301","uid":"1","title":"Current Status","log":"","status":"1","comment":"0","promote":"0","sticky":"0","vuuid":"9c10dedc-822c-4adf-b081-35191b476235","nid":"127","type":"book","language":"und","created":"1415428249","changed":"1415428249","tnid":"0","translate":"0","uuid":"606973fe-e760-420c-bc71-655415133aa7","revision_timestamp":"1415428249","revision_uid":"1","body":{"und":[{"value":"Class or type population of the At is a prerequisite for data entry in the ASA and ATA components of the Foundational Model of Anatomy ontology. The classes of At are defined in narrative text in accord with explicitly stated foundational principles (Principles and Definitions). These classes have been populated for macroscopic and microscopic anatomy, as well as for prototypic examples of biological macromolecules.\r\n\r\nCanonical types (e.g., head, heart, right ventricle, left inguinal canal) are the leaf classes of At. These canonical types may, in turn, serve as classes when application developers wish to associate with the FMA the anatomy of instances or individual subjects (e.g., heart of John Doe). All canonical types must be assigned to a semantic class through the -is a- relationship before ASA and ATA relations of the class can be entered in the model.\r\n\r\nWe are currently developing the Anatomical Structural Abstraction (ASA) Components of the FMA. These components include a Dimensional Ontology (Do), Boundary Network (Bn), Part-of Network (Pn), and Spatial Association Network (SAn).\r\n\r\nThus, the ASA may be represented by the equation:\r\n\r\nASA = (Do, Bn, Pn, SAn)\r\n\r\nPart\/whole relations have been populated extensively, though not comprehensively for microscopic entities. We have defined different types of part-of relations (regional, constitutional, systemic, membership), which are described elsewhere. Such attributed part-of relationships have been entered for a substantial number of organs. Similarly, branch-of and tributary-of relationships have been entered for the majority of nerves, arteries, veins and lymphatic vessels. We are in the process of entering various spatial association relationships such as location, containment, and orientation (see for example \u2018Esophagus\u2019). We are developing a tool that will provide semi-automatic entry of the numerous adjacency relationships of organs and organ parts (see for example \u2018T8 part of esophagus\u2019 in Foundational Model Explorer), thus speed up the population of this relationship.\r\n\r\nEssentially very little data have been entered as yet for the Anatomical Transformation Abstraction (ATA), which is designed to model embryonic as well as postnatal development. We have proposed a representation scheme for the ATA in a research grant application.","summary":"","format":"filtered_html","safe_value":"\u003Cp\u003EClass or type population of the At is a prerequisite for data entry in the ASA and ATA components of the Foundational Model of Anatomy ontology. The classes of At are defined in narrative text in accord with explicitly stated foundational principles (Principles and Definitions). These classes have been populated for macroscopic and microscopic anatomy, as well as for prototypic examples of biological macromolecules.\u003C\/p\u003E\n\u003Cp\u003ECanonical types (e.g., head, heart, right ventricle, left inguinal canal) are the leaf classes of At. These canonical types may, in turn, serve as classes when application developers wish to associate with the FMA the anatomy of instances or individual subjects (e.g., heart of John Doe). All canonical types must be assigned to a semantic class through the -is a- relationship before ASA and ATA relations of the class can be entered in the model.\u003C\/p\u003E\n\u003Cp\u003EWe are currently developing the Anatomical Structural Abstraction (ASA) Components of the FMA. These components include a Dimensional Ontology (Do), Boundary Network (Bn), Part-of Network (Pn), and Spatial Association Network (SAn).\u003C\/p\u003E\n\u003Cp\u003EThus, the ASA may be represented by the equation:\u003C\/p\u003E\n\u003Cp\u003EASA = (Do, Bn, Pn, SAn)\u003C\/p\u003E\n\u003Cp\u003EPart\/whole relations have been populated extensively, though not comprehensively for microscopic entities. We have defined different types of part-of relations (regional, constitutional, systemic, membership), which are described elsewhere. Such attributed part-of relationships have been entered for a substantial number of organs. Similarly, branch-of and tributary-of relationships have been entered for the majority of nerves, arteries, veins and lymphatic vessels. We are in the process of entering various spatial association relationships such as location, containment, and orientation (see for example \u2018Esophagus\u2019). We are developing a tool that will provide semi-automatic entry of the numerous adjacency relationships of organs and organ parts (see for example \u2018T8 part of esophagus\u2019 in Foundational Model Explorer), thus speed up the population of this relationship.\u003C\/p\u003E\n\u003Cp\u003EEssentially very little data have been entered as yet for the Anatomical Transformation Abstraction (ATA), which is designed to model embryonic as well as postnatal development. We have proposed a representation scheme for the ATA in a research grant application.\u003C\/p\u003E\n","safe_summary":""}]},"cid":0,"last_comment_timestamp":"1415428249","last_comment_name":"","last_comment_uid":"1","comment_count":0,"name":"drupal","picture":"0","data":"b:0;","path":{"pid":"154","source":"node\/127","alias":"content\/current-status","language":"und"},"menu":null,"node_export_drupal_version":"7","node_export_book":{"#parent_uuid":"4161c11e-3f3e-4c92-960c-8081c20e31ad","#book_uuid":"4161c11e-3f3e-4c92-960c-8081c20e31ad","weight":-8,"#is_root":false},"#node_export_object":"1"}]
Copy this code and then on the site you want to import to, go to the
Node export: import
link under
Add content
, and paste it in there.