<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main"></title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Asiyah</forename><forename type="middle">Yu</forename><surname>Lin</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Axle Research and Technology</orgName>
								<address>
									<settlement>Rockville</settlement>
									<region>Maryland</region>
									<country>U.S</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">John</forename><surname>Graybeal</surname></persName>
							<email>jbgraybeal@sonic.net</email>
							<affiliation key="aff2">
								<orgName type="institution">Graybeal.SKI Consulting</orgName>
								<address>
									<settlement>Stanford</settlement>
									<region>California</region>
									<country>U.S</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Anna</forename><forename type="middle">Maria</forename><surname>Masci</surname></persName>
							<email>amasci@mdanderson.org</email>
							<affiliation key="aff3">
								<orgName type="institution">University of Texas MD Anderson Cancer Center</orgName>
								<address>
									<settlement>Huston</settlement>
									<region>Texas</region>
									<country>U.S</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Juliane</forename><surname>Schneider</surname></persName>
							<email>juliane.schneider@pnnl.gov</email>
							<affiliation key="aff4">
								<orgName type="institution">Pacific Northwest National Laboratory</orgName>
								<address>
									<settlement>Richland</settlement>
									<region>Washington</region>
									<country>U.S</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Ruth</forename><surname>Duerr</surname></persName>
							<email>ruth.duerr3@gmail.com</email>
							<affiliation key="aff5">
								<orgName type="institution">Ronin Institute for Independent Scholarship</orgName>
								<address>
									<settlement>Montclair</settlement>
									<region>New Jersey</region>
									<country>U.S</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Eric</forename><forename type="middle">G</forename><surname>Stephan</surname></persName>
							<email>eric.stephan@pnnl.gov</email>
							<affiliation key="aff4">
								<orgName type="institution">Pacific Northwest National Laboratory</orgName>
								<address>
									<settlement>Richland</settlement>
									<region>Washington</region>
									<country>U.S</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Hande</forename><forename type="middle">Kũçük</forename><surname>Mcginty</surname></persName>
							<affiliation key="aff6">
								<orgName type="institution">Kansas State University</orgName>
								<address>
									<settlement>Manhattan</settlement>
									<region>Kansas</region>
									<country>U.S</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff0">
								<address>
									<postCode>2024</postCode>
									<settlement>Enschede</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">4A4ED3FAB28A55ED2ED1477E2D56CC7E</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T17:46+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Ontology</term>
					<term>Vocabulary</term>
					<term>Terms</term>
					<term>Best Practices</term>
					<term>Semantics</term>
					<term>FAIR</term>
					<term>Reusability1</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The development of biomedical ontologies has been rising exponentially in the last 10 years. In 2010, 181 ontologies were listed in BioPortal. As of June 2024, this number has increased to 1124, and many other open ontology registration systems exist. When an ontology engineer starts developing an ontology related to clinical studies, or anyone who wants to reuse similar ontologies, he/she may need to navigate multiple similar ontologies, such as Clinical Study Ontology, Clinical Trial Ontology, Clinical Research Ontology, SNOMED CT or NCIT, and more. A search of the term "clinical trial" shows that 35 ontologies have the term labeled "clinical trial". This presents a challenge for data engineers and ontologists: how does one select the best fit-forpurpose ontologies that work well for specific use cases? Often the selection process is unstructured and highly biased, influenced by the domain experts involved, the background of the development team, and the team's theoretical approach to ontology adoption. While pursuing FAIR Principles for ontology development, the reuse and interoperability of ontologies have been a serious concern among ontologies, decision makers, and funders.</p><p>Beginning with work in the Research Data Alliance (RDA) Vocabulary and Semantic Services Interest Group (VSSIG) over several years, our group has been gathering published and lived evaluation techniques for choosing terms and ontologies. Here we share our observations of structured guidance and specific criteria to choose the right ontologies that fit various semantic purposes. We distinguish between criteria that can be evaluated with existing tools and services, criteria that can be evaluated manually or subjectively, and criteria that could be evaluated with as-yet-unimplemented techniques.</p><p>Finally, we invite collaboration in ongoing development of the evolving materials through the RDA VSSIG group, its slack channel, and its collaborative development in our Google Drive folder.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body/>
		<back>
			<div type="references">

				<listBibl/>
			</div>
		</back>
	</text>
</TEI>
