ผลต่างระหว่างรุ่นของ "หน้าหลัก"
ล |
ล |
||
แถว 1: | แถว 1: | ||
− | + | Given this anatomical framework we are building the OCDM | |
+ | Personal ontologies. Offered this anatomical framework we're creating the OCDM by 1st enhancing the FMA to provide detail on both adult and developmental craniofacial anatomy as required by a series of use situations (described within the next section) that we've elicited from craniofacial researchers. We then extract a view (or "slim" in GO terms) [Gene Ontology Consortium, 2013] of just the craniofacial elements on the FMA required to make the canonical craniofacial human sub-ontology (CHO), and make use of this view as a template for developing other OCDM elements (or sub-ontologies) coping with human malformations, typical and abnormal mouse improvement and malformations, and mappings amongst homologous anatomical structures in human and mouse. Our present concentrate is on human and mouse, and a equivalent strategy of mapping to canonical human anatomy as the fundamental organizing principle may be used with other relevant model organisms. Content [https://www.medchemexpress.com/Asciminib.html Asciminib Bcr-Abl] creation for the OCDM is accomplished in the Prot ?ontology authoring tool [Gennari et al., 2003], and is produced obtainable as a semantic internet service [McIlraith et al., 2001], which makes it possible for the ontology to become queried by end-user applications. Whereas the OCDM content material as well as the net solutions are "under-the-hood", of interest mainly to ontology authors, it can be the enduser applications that will offer the functionality and graphical interfaces that allow craniofacial researchers to make use of the OCDM in their own operate. In the following sections we offer a lot more detail around the use instances, the current OCDM content, instance queries that can presently be answered by the OCDM, as well as a prototype application that accesses the OCDM via the net service.Use CasesThe improvement of your OCDM is informed by a series of use situations, exactly where for our purposes a "use case" is often a activity or set of tasks that a craniofacial researcher would carry out in their function, and that would make use of the OCDM. Primarily based each on our practical experience in constructing the FaceBase Hub and on input from craniofacial researchers inside the consortium, these use instances describe tasks and scenarios that may possibly use OCDM-based descriptions to assistance data navigation, exploration, and interpretation. Every single use case is characterized by a description, a list of prospective users (e.g. clinician, researcher), a list of tasks that must be achieved to implement the use case, a list of information requirements that really should be met by the ontology, the information or each; as well as a list of userAm J Med Genet C Semin Med Genet. Author manuscript; available in PMC 2014 June 02.Brinkley et al.Pageinterface concerns that have to be addressed so that you can make the implemented use case accessible to craniofacial researchers. Present use situations are organized in 5 categories ?visualization, annotation, searching/browsing, gene expression show, and analytics (Table 1). As one distinct instance Table two describes the use case, Discovering structures associated with syndromes, that is classified beneath "Searching/Browsing". In this scenario, a user is thinking about locating relevant clinical or standard research data that may be relevant to Apert syndrome. As opposed to obtaining to tediously search by way of the literature or on the internet databases the user in this scenario would merely sort "Apert Syndrome" into a user interface. |
รุ่นแก้ไขเมื่อ 09:02, 12 กรกฎาคม 2564
Given this anatomical framework we are building the OCDM Personal ontologies. Offered this anatomical framework we're creating the OCDM by 1st enhancing the FMA to provide detail on both adult and developmental craniofacial anatomy as required by a series of use situations (described within the next section) that we've elicited from craniofacial researchers. We then extract a view (or "slim" in GO terms) [Gene Ontology Consortium, 2013] of just the craniofacial elements on the FMA required to make the canonical craniofacial human sub-ontology (CHO), and make use of this view as a template for developing other OCDM elements (or sub-ontologies) coping with human malformations, typical and abnormal mouse improvement and malformations, and mappings amongst homologous anatomical structures in human and mouse. Our present concentrate is on human and mouse, and a equivalent strategy of mapping to canonical human anatomy as the fundamental organizing principle may be used with other relevant model organisms. Content Asciminib Bcr-Abl creation for the OCDM is accomplished in the Prot ?ontology authoring tool [Gennari et al., 2003], and is produced obtainable as a semantic internet service [McIlraith et al., 2001], which makes it possible for the ontology to become queried by end-user applications. Whereas the OCDM content material as well as the net solutions are "under-the-hood", of interest mainly to ontology authors, it can be the enduser applications that will offer the functionality and graphical interfaces that allow craniofacial researchers to make use of the OCDM in their own operate. In the following sections we offer a lot more detail around the use instances, the current OCDM content, instance queries that can presently be answered by the OCDM, as well as a prototype application that accesses the OCDM via the net service.Use CasesThe improvement of your OCDM is informed by a series of use situations, exactly where for our purposes a "use case" is often a activity or set of tasks that a craniofacial researcher would carry out in their function, and that would make use of the OCDM. Primarily based each on our practical experience in constructing the FaceBase Hub and on input from craniofacial researchers inside the consortium, these use instances describe tasks and scenarios that may possibly use OCDM-based descriptions to assistance data navigation, exploration, and interpretation. Every single use case is characterized by a description, a list of prospective users (e.g. clinician, researcher), a list of tasks that must be achieved to implement the use case, a list of information requirements that really should be met by the ontology, the information or each; as well as a list of userAm J Med Genet C Semin Med Genet. Author manuscript; available in PMC 2014 June 02.Brinkley et al.Pageinterface concerns that have to be addressed so that you can make the implemented use case accessible to craniofacial researchers. Present use situations are organized in 5 categories ?visualization, annotation, searching/browsing, gene expression show, and analytics (Table 1). As one distinct instance Table two describes the use case, Discovering structures associated with syndromes, that is classified beneath "Searching/Browsing". In this scenario, a user is thinking about locating relevant clinical or standard research data that may be relevant to Apert syndrome. As opposed to obtaining to tediously search by way of the literature or on the internet databases the user in this scenario would merely sort "Apert Syndrome" into a user interface.