Ontologies Sample Clauses

Ontologies. To clear up any possible confusion, when ‘ontology’ is mentioned in this disserta- tion, this does not refer to the branch of philosophy, but the information science concept: a representation of concepts in a specific domain (Xxxxxx, 1995). This is similar to a thesaurus or word list, with the most well known Dutch example being the Archeologisch Basisregister (ABR) ontology (Xxxxxx et al., 1992). For NER, it is useful to have ontologies for the categories of entities you are targeting, as whether or not a token occurs in such a word list is an indication that it might be an entity. For Artefacts and Time Periods, we use the aforementioned ABR ontology. This is a hierarchical list of artefacts, time periods and monument types, created and maintained by the RCE. We have slightly adjusted some of the entries to better match natural language, e.g. changing “bijl, doorboord” (axe, perforated) to “doorboorde bijl” (perforated axe). Unfortunately, the ABR is not very exhaustive and only contains a basic list of time periods. This is why we decided to use the PeriodO time appellations list (Xxxxxxxxxx et al., 2016) for translating Time Periods to year ranges (further described in chapter 7). We also altered this list by adding more time periods, mainly geological time spans (e.g., Holocene) and specific cultures (e.g., Bell Beaker Culture). For Locations and Species, we are not using any ontologies, as we are focusing more on Artefacts and Time Periods for the time being. For future work on these
Sample 1
AutoNDA by SimpleDocs
Ontologies. For the terminology used in the WP6 literature database no existing ontology was used. For the column headers (field names) the WP6 NanoReg terminology was mapped against existing ontologies. 258 terms in the Wp6 NanoReg database needed to be mapped to Uniform Resource Identifiers (URIs). 207 terms were mapped (~80%) but most of the terms were mapped against multiple URIs. For example dispersion protocol was mapped against the Nanoparticle ontology term 1969, dispersion, and the Information Artifact Ontology term 0000301, protocol (NPO_1969 IAO:0000301). 51 terms could not be mapped to URIs at all(~20%). This mapping was done only based on the exact term (not the actual meaning of the term). In future projects it is essential that mapping of ontologies and database fields it done on the meaning and interpretation of the term and field rather than a textual match. For example: “number of different incubation times” was matched to the terms “number”(PATO:0001555), “different”(C46003), “incubation” (npo:NPO_2000) and “times” (PATO:0000165). None of these terms in itself cover the meaning of the term “number of different incubation times”. The use of existing ontologies for the column headers helps in harmonizing the interpretation of the database fields and the interpretation of the database structure. This facilities for example data analysis and data entry. In the data-entry tool users are allowed to enter free text fields for various entries. Moreover users can extend and edit pick-list that are used for various fields. By doing this there has been no 1xxxx://xxx.xxxx.xxx/apps/group_public/download.php/30992/Money,%20C.,%20Reg%20Toxicol%20Pharma col,%202013.pdf control on the terminology that was used to explain various parameters. For example titanium dioxide can be explained by: Titanium dioxide, TiO2, tio2 etc. these are 3 terms meaning the same thing. An important lesson is that data entry should be restricted to specific terminology, preferably linked to a specific existing ontology as much as possible. This guarantees the description of parameters to be both unique and exclusive By doing this the interpretation of a specific term by different experts is fixed. Existing ontologies can and should be used for: Chemical abbreviations, nanoparticle characterization, cell assays, biological assays, physical conditions, physical chemical characteristics, media etc. Through the eNanoMapper database existing ontologies are used for the NanoReg2 and Calibrate ...
Sample 1
Ontologies. 5.1.1. Symptom Ontology (SO) The Symptom Ontology (SO) [41] was designed around the guiding concept of a symptom being: "A perceived change in function, sensation or appearance reported by a patient indicative of a disease". The Symptom Ontology captures and documents the semantics of two sets of terms, the term “Sign” and the term “Symptom”. The ontology is open source. It was developed as part of Gemina project, starting in 2005 at the Institute Genome Sciences (IGS) at the University of Maryland. Work ended on 2009. In July 2008 the Symptoms Ontology was submitted for inclusion and review to the OBO Foundry and today the standardization body for the Symptom Ontology is the OBO Foundry. The ontology also provides human readable text together with computer readable format. The available computer readable formats of the ontology are in OBO and OWL. The semantics of the Ontology are coherent, consistent and there is a rigid domain specification. Last but not least the symptom ontology reaches high level of interoperability.
Sample 1

Related to Ontologies

  • Therapies Acupuncture and acupuncturist services, including x-ray and laboratory services. • Biofeedback, biofeedback training, and biofeedback by any other modality for any condition. • Recreational therapy services and programs, including wilderness programs. • Services provided in any covered program that are recreational therapy services, including wilderness programs, educational services, complimentary services, non- medical self-care, self-help programs, or non-clinical services. Examples include, but are not limited to, Tai Chi, yoga, personal training, meditation. • Computer/internet/social media based services and/or programs. • Recreational therapy. • Aqua therapy unless provided by a physical therapist. • Maintenance therapy services unless it is a habilitative service that helps a person keep, learn or improve skills and functioning for daily living. • Aromatherapy. • Hippotherapy. • Massage therapy rendered by a massage therapist. • Therapies, procedures, and services for the purpose of relieving stress. • Physical, occupational, speech, or respiratory therapy provided in your home, unless through a home care program. • Pelvic floor electrical and magnetic stimulation, and pelvic floor exercises. • Educational classes and services for speech impairments that are self-correcting. • Speech therapy services related to food aversion or texture disorders. • Exercise therapy. • Naturopathic, homeopathic, and Christian Science services, regardless of who orders or provides the services. Vision Care Services • Eye exercises and visual training services. • Lenses and/or frames and contact lenses for members aged nineteen (19) and older. • Vision hardware purchased from a non-network provider. • Non-collection vision hardware. • Lenses and/or frames and contact lenses unless specifically listed as a covered healthcare service.

  • Inoculations The Employer agrees to pay full expenses for inoculation or immunization shots for the employee and for members of an employee’s household when such becomes necessary as a result of said employee’s exposure to contagious diseases (including AIDS, tuberculosis and hepatitis) where said officer has been exposed to said disease in the line of duty.

  • Analytics 1.1. IFS may track and analyze the usage of the IFS Offering for purposes of determining usage made of the IFS Offering, for the purposes of security, to assist customers, and for improving the Software and Services and the user experience in using such Software and Services. For example, IFS may use this information to help customers derive more value from the Software and Services, to understand and analyze trends, or to track which features are used most often in order to improve the Software and Services. IFS may share anonymous usage data with its service providers for the purpose of helping in such tracking, analysis and improvements. Additionally, IFS may share such anonymous usage data on an aggregate basis in the normal course of operating their business; for example, IFS may share information publicly to show trends about the general use of its software and services. TERMS - SERVICES

  • Screening 3.13.1 Refuse containers located outside the building shall be fully screened from adjacent properties and from streets by means of opaque fencing or masonry walls with suitable landscaping.

  • Health Screening The Contractor shall conduct a Health Needs Screen (HNS) for new members that enroll in the Contractor’s plan. The HNS will be used to identify the member’s physical and/or behavioral health care needs, special health care needs, as well as the need for disease management, care management and/or case management services set forth in Section 3.8. The HNS may be conducted in person, by phone, online or by mail. The Contractor shall use the standard health screening tool developed by OMPP, i.e., the Health Needs Screening Tool, but is permitted to supplement the OMPP Health Needs Screening Tool with additional questions developed by the Contractor. Any additions to the OMPP Health Needs Screening Tool shall be approved by OMPP. The HNS shall be conducted within ninety (90) calendar days of the Contractor’s receipt of a new member’s fully eligible file from the State. The Contractor is encouraged to conduct the HNS at the same time it assists the member in making a PMP selection. The Contractor shall also be required to conduct a subsequent health screening or comprehensive health assessment if a member’s health care status is determined to have changed since the original screening, such as evidence of overutilization of health care services as identified through such methods as claims review. Non-clinical staff may conduct the HNS. The results of the HNS shall be transferred to OMPP in the form and manner set forth by OMPP. As part of this contract, the Contractor shall not be required to conduct HNS for members enrolled in the Contractor’s plan prior to January 1, 2017 unless a change in the member’s health care status indicates the need to conduct a health screening. For purposes of the HNS requirement, new members are defined as members that have not been enrolled in the Contractor’s plan in the previous twelve (12) months. Data from the HNS or NOP form, current medications and self-reported medical conditions will be used to develop stratification levels for members in Hoosier Healthwise. The Contractor may use its own proprietary stratification methodology to determine which members should be referred to specific care coordination services ranging from disease management to complex case management. OMPP shall apply its own stratification methodology which may, in future years, be used to link stratification level to the per member per month capitation rate. The initial HNS shall be followed by a detailed Comprehensive Health Assessment Tool (CHAT) by a health care professional when a member is identified through the HNS as having a special health care need, as set forth in Section 4.2.4, or when there is a need to follow up on problem areas found in the initial HNS. The detailed CHAT may include, but is not limited to, discussion with the member, a review of the member’s claims history and/or contact with the member’s family or health care providers. These interactions shall be documented and shall be available for review by OMPP. The Contractor shall keep up-to-date records of all members found to have special health care needs based on the initial screening, including documentation of the follow-up detailed CHAT and contacts with the member, their family or health care providers.

  • Diagnostic procedures to aid the Provider in determining required dental treatment.

  • Devices BNY Mellon will restrict the transfer of Customer Data from its network to mass storage devices. BNY Mellon will use a mobile device management system or equivalent tool when mobile computing is used to provide the services. Applications on such authenticated devices will be housed within an encrypted container and BNY Mellon will maintain the ability to remote wipe the contents of the container.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Blasting Blasting shall be permitted only for road construction purposes unless advance permission is obtained from Forest Service. Whenever the Industrial Fire Precaution Level is II or greater, a fire security person equipped with a long handled round point No. 0 or larger shovel and a 5 gallon backpack pump can filled with water, will stay at location of blast for 1 hour after blasting is done. Blasting may be suspended by Forest Service, in areas of high rate of spread and resistance to control. Fuses shall not be used for blasting. Explosive cords shall not be used without permission of Forest Service, which may specify conditions under which such explosives may be used and precautions to be taken.

  • PIONEERING Pioneering may not extend past construction that will be completed during the current construction season. Pioneering may not extend more than 500 feet beyond completed construction unless approved in writing by the Contract Administrator. In addition, the following actions must be taken as pioneering progresses:  Drainage must be provided on all uncompleted construction.  Road pioneering operations may not undercut the final cut slope or restrict drainage.  Culverts at live stream crossings must be installed during pioneering operations prior to embankment.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!