<?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">Semantic Association of Taxonomy-based Standards Using Ontology</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Hung-Ju</forename><surname>Chu</surname></persName>
							<email>hchu@cise.ufl.edu</email>
							<affiliation key="aff0">
								<orgName type="department">Computer and Information Science and Engineering</orgName>
								<orgName type="institution">University of Florida Gainesville</orgName>
								<address>
									<region>FL</region>
									<country key="US">U.S.A</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Randy</forename><forename type="middle">Y C</forename><surname>Chow</surname></persName>
							<email>chow@cise.ufl.edu</email>
							<affiliation key="aff0">
								<orgName type="department">Computer and Information Science and Engineering</orgName>
								<orgName type="institution">University of Florida Gainesville</orgName>
								<address>
									<region>FL</region>
									<country key="US">U.S.A</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Su-Shing</forename><surname>Chen</surname></persName>
							<email>suchen@cise.ufl.edu</email>
							<affiliation key="aff0">
								<orgName type="department">Computer and Information Science and Engineering</orgName>
								<orgName type="institution">University of Florida Gainesville</orgName>
								<address>
									<region>FL</region>
									<country key="US">U.S.A</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Raja</forename><forename type="middle">R A</forename><surname>Issa</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">Rinker School of Building Construction</orgName>
								<orgName type="institution">University of Florida</orgName>
								<address>
									<settlement>Gainesville</settlement>
									<region>FL</region>
									<country key="US">U.S.A</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Ivan</forename><surname>Mutis</surname></persName>
							<email>imutis@ufl.edu</email>
							<affiliation key="aff1">
								<orgName type="department">Rinker School of Building Construction</orgName>
								<orgName type="institution">University of Florida</orgName>
								<address>
									<settlement>Gainesville</settlement>
									<region>FL</region>
									<country key="US">U.S.A</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Semantic Association of Taxonomy-based Standards Using Ontology</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">E3C02ACA2924429F40C1115CE0D267F4</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T09:02+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>H.3.1 [Information Storage and Retrieval]: Content Analysis and Indexing -Indexing methods, Linguistic process</term>
					<term>I.2.4 [Artificial Intelligence]: I.2.1 Applications and Expert Systems -Industrial automation</term>
					<term>I.2.4 Knowledge Representation Formalisms and Methods</term>
					<term>I.2.6 [Artificial Intelligence]: Learning -Knowledge Acquisition taxonomy and standards, semantic interoperability, ontology-based knowledge extraction, semantic mapping</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The vision of semantic interoperability, the fluid sharing of digitalized knowledge, has led much research on ontology/schema mapping/aligning. Although this line of research is fundamental and has brought valuable contributions to this endeavor, it does not represent a solution to the challenge, semantic heterogeneity, since the performance of proposed approaches significantly relies on the degree of uniformity, formalization and sufficiency of data representations but most of today's independently developed information systems seldom have common knowledge modeling frameworks and their data are often not formally and adequately specified. Consequently, a workable solution usually requires interventions of domain experts.</p><p>In human society, hierarchically structured standards (or taxonomies) for characterizing complex application processes and objects used in the processes are often used as a common and effective way to achieve some semantic agreements among stakeholders within a domain. This research hypothesizes that the establishment and the use of such standards can serve as a framework that can effectively facilitate the reconciliation of semantic heterogeneity in complex application domains. However, the reality shows that a comprehensive priori consensus is extremely difficult, if not impossible, to reach. Consequently, various complementary and competing standards are often created and their constant-changing nature yields another level of challenge in achieving the hypothesis. This paper focuses on the development of methodology for bridging complementary standards within an application domain. It exemplifies such standards in building construction industry where interoperability problems are prevalent and human interactions are commonplace. It proposes a semi-automatic approach for semantically associating the standards to reduce costly human intervention in a workflow. The approach formalizes standards by using ontology and discovers their affinity (to what degree they are related with respect to their usage) from automated project document processing and semi-automatic domain expert inputs. A high-level architecture of an integration framework in web environment is suggested for depicting the role of the semantic association approach in the system.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">INTRODUCTION</head><p>The vision of semantic interoperability, the fluid sharing of digitalized knowledge, has led much research on ontology (formal specification of conceptualization) and its languages, such as Web Ontology Language (OWL) <ref type="bibr" target="#b7">[8]</ref>. The language provides primitives for specifying concepts, properties, explicit semantic relationships, and logical constraints on those objects. However, it does not address the issue of semantic heterogeneity between two independently developed ontologies. For example, a program that reads an ontology in OWL does not understand another ontology in the same language unless there is an explicit mapping between them. This difficulty has led much research on ontology/schema mapping/alignment <ref type="bibr" target="#b3">[4]</ref>, <ref type="bibr" target="#b4">[5]</ref>, <ref type="bibr" target="#b5">[6]</ref>, <ref type="bibr" target="#b10">[11]</ref>, <ref type="bibr" target="#b11">[12]</ref>, <ref type="bibr" target="#b12">[13]</ref>, and <ref type="bibr" target="#b13">[14]</ref> and various matching technologies have been developed based on the attributes of objects and their associated data. Although this line of research is fundamental and has brought valuable contributions to this endeavor, it does not represent a solution to the challenge as we see. The performance of proposed approaches significantly relies on the degree of uniformity, formalization and sufficiency of data representations. Unfortunately, the concept of unified, formal, and sufficient specification is often an after-thought and most of today's independently developed information systems seldom have common knowledge modeling frameworks and their data are often not formally and adequately specified. Consequently a workable solution usually requires interventions of domain experts.</p><p>In human society, hierarchically structured standards (or taxonomies) for characterizing complex application processes and objects used in the processes are often used as a common and effective way to achieve some semantic agreements among stakeholders within a domain. This research hypothesizes that the establishment and the use of such standards can serve as a framework that can effectively facilitate the reconciliation of semantic heterogeneity in complex application domains. However, the reality shows that a comprehensive priori consensus is extremely difficult, if not impossible, to reach. Consequently, various complementary and competing standards are often created and their constant-changing nature yields another level of challenge in achieving the hypothesis. This paper focuses on the development of methodology for bridging complementary standards within an application domain. We have chosen a target application in the building construction domain, where interoperability problems are prevalent and human interactions are commonplace. In that domain, a variety of taxonomy-based standards have been established but still lack a uniform and systematic way for supporting efficient collaboration among project participants using different standards. This problem is further compounded by the complexity and the dynamics of business applications, which often require changes of the wellknown standards. The interoperability cost in such environment is tremendous. For example, based on a recent National Institute of Standards and Technology (NIST) report <ref type="bibr" target="#b2">[3]</ref>, a conservative figure of $15.8 billion was determined to be annual costs due to a lack of interoperability in the capital facilities industry in 2002.</p><p>Two mainstream complementary standards, MasterFormat and UniformatII, in that domain are considered in our research. MasterFormat <ref type="bibr" target="#b0">[1]</ref> is a specification standard established by the Construction Specification Institute (CSI) for most nonresidential building construction projects in North America. UniformatII is a newer American Society of Testing and Materials (ASTM) standard aiming at providing a consistent reference for the description, economic analysis, and management of buildings during all phases of their life cycles <ref type="bibr" target="#b1">[2]</ref>. These standards were created by different stakeholders with different perspectives for different purposes. For instance, an architect is interested in the design and structure of a building, a contractor wants to know what materials are used and how much they cost, and a building inspector is concerned about building code compliance issues. MasterFormat classifies items primarily based on the specification of products and materials used in construction, so it is based on a conceptual view of a contractor. Complementarily, the taxonomical classification in Uniformat II is primarily based on the attributes and location of structural building components, such as foundations and exterior walls, which reflects the architect's view of a construction project. Although their views are different but both address the same building object. In other words, the taxonomies of the standards classify the same set of objects but on different attributes. From here one can easily infer that crossreferencing or document conversion between the standards is inevitable for interaction among project participants in applications such as cost estimation and code compliance checking. For example, a wall (interial or exterial) in Uni-formatII needs to be associated with the material (metal, wood or fiberglass) in MaterFormat and conformed to its intended usage (hurricane or fire proof) according to building code regulations (standards yet to be formalized by the industry). In general, UniformatII by design is more suitable as a participant communication/interaction framework than MasterFormat during the earlier phases of the life cycle. On the other hand, Masterformat has been used for years and has gained the majority of the construction industrial support for specifying detailed project documents. To facilitate more efficient collaboration among project participants, it is a common practice to supplement Unifor-matII with Preliminary Project Descriptions (PPDs) or schematic design in earlier phases, and convert them to construction documents in Masterformat during later phases. In addition, the conversion is also necessary for cost calculation since most databases of building materials suppliers are based on MasterFormat. It is desirable to transform pre-bid elemental estimates to MasterFormat, and from there to the trade costs of the project <ref type="bibr" target="#b1">[2]</ref>. This process is often tedious and requires cross-area knowledge. Currently, it is done manually by domain experts and it is considered a major cause that hampers interoperability in the construction domain. Bridging the two standards is a key enabler for enhancing the interoperability.</p><p>Directly matching approaches based on attributes of the entities of the standards are expected to be inefficient due to the heterogeneous nature of complementary standards. This paper proposes a practical compromise by redefining the notion of mapping with a semi-automatic semantic extraction framework to assist domain experts in achieving interoperability. The mapping is termed as semantic association for relating elements between standards, and is dependent on the intended use such as cross-referencing of elements or specification semantic mapping. The semantic relationship can be characterized in two measurements: similarity (how closely objects resemble each other in their representation) and affinity (to what degree they are coupled in their usage). In some sense similarity is more static while affinity is more dynamic and general. For example, a bicycle is similar to a car due to their physical structures and properties. However, gasoline is more affinitive to a car although they do not resemble each other. Exploiting affinity in addi-tion to similarity through semantic association is the focus of this research.</p><p>The approach consists of three components: formalization of taxonomies, ontology-based semantic extraction and measurement of affinity. The first component is a simple and yet novel approach for annotating a standard in primitive descriptive statements constructed by a set of necessary and sufficient orthogonal relations. They are then normalized and generalized into ontology. The second component shows how the ontology can be used for the extraction of relevant information from the instances in other standards for semantic association. The third component quantifies the affinity for ranking the extracted metadata to identify optimal association. The following sections detail the three components and outline an overall architecture of an integration framework depicting the relationship between the proposed approach and other related technologies and systems.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">FORMALIZATION OF TAXONOMY</head><p>Taxonomies are initially designed for human consumption therefore some domain knowledge that is obvious and assumed by stakeholders is often omitted in their specifications. Moreover, taxonomies classifying large and complex items usually have the following characteristics:</p><p>1. The entities being classified and the attributes upon which the classification is based, are themselves complex concepts.</p><p>2. Multiple attributes (different concepts) might be used to classify entities at the same level.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Attributes are not orthogonal and might result in overlapping concepts in low-level entities (an object can fit into multiple categories).</head><p>There is a need for a systematic approach for annotating assumed semantics, clarifying complex concepts, and transforming them into formal representation before taxonomies can be effectively used for semantic association.</p><p>Semantic depends on context and context depends on applications. In other words, the semantic of a standard is open depending on how they are used. To avoid a standard being bound to specific applications, the intrinsic semantic of a standard without context should include the following:</p><p>1. the attributes being used for classification under the general perception in the application domain and 2. the entities under the inheritance of the taxonomy and the attributes.</p><p>To model the intrinsic semantics, ontology is considered in this research. The following subsection describes a systematic approach for transforming taxonomy into ontology.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ontology Development from Taxonomy</head><p>The term, ontology, has been widely used in several disciplines, such as philosophy, epistemology, and computer science. There is much confusion in its definition. For example, in philosophy it refers to the subject of existence while in epistemology it is about knowledge and knowing.</p><p>In computer science, many people use Gruber's definition <ref type="bibr" target="#b9">[10]</ref> -an explicit specification of a conceptualization. In the context of our research, we interpret it as a description of the concepts/terms and relationships that can exist in an application domain. Centered on terms and relations, the transformation of taxonomy into ontology is described in the following steps.</p><p>Step 1: relation set identification</p><p>The goal of this step is to identify a sufficient and necessary set of orthogonal relations for a given taxonomy/standard so that assumed domain knowledge and complex concepts can be formally specified. This step should be manually done by standard committees who know best about the original intended use of the standards. The set should be constructed from two types of relations: primitive and derived.</p><p>Primitive relations are those that are unambiguously understood by the general public and the relationship between concepts connected by them does not change over time. Moreover, they reflect the intrinsic properties of objects or describe time and space and the intention of users when the objects are used. In addition, their definitions should include set relationship, such as instance-instance, instanceclass, and class-class, to avoid ambiguity. For example, part_of is ambiguous since it could mean a subcomponent of an object or the membership of an object in a class. Its meaning can be identified as the first explanation if instance-instance is specified.</p><p>Derived relations are those that can be composed/modeled from primitive relations.</p><p>To elaborate this step, a small portion of the top three levels in MasterFormat taxonomy, Division 5 (D5) Metals and Division 6 (D6) Wood and Plastic rooted from Material, is exemplified as follows:</p><p>Division </p><formula xml:id="formula_0">kind_of + + + instance_of + + + made_of + - -</formula><p>Step 2: relation statements construction This step is to construct simple statements using the relations defined in step one and all keywords in the taxonomy.</p><p>The statements are then processed in subsequent steps for constructing ontology. There are two advantages using this bottom-up approach for formalizing taxonomies. One is that it can better address the dynamic nature of standards by enabling incremental updates and modifications of the statements and their resulting ontology. (05410_1) 05410 7. 05410 is used_for 05400 (05400_05410) Note that each statement is given a unique identifier (following ) derived from the original identifier of a taxonomy entity.</p><p>Step 3: normalization It is likely that redundant or conflict statements are generated along the way when domain experts annotate their taxonomies in the above steps. Based on the mathematical properties of the relations, this step normalizes the statements by: 1. redundancy elimination (removing same or equivalent statements) 2. conflict detection (for example: A-r1-B, and B-r1-A statements are conflict if r1 has asymmetric property) 3. implication detection (for example, A-r1-B, and B-r1 C statements imply A-r1-C through transitive property).</p><p>Step 4: semi-automatic generalization This step is to generalize the resulting statements from step 3 into higher-level concepts connected by the same set of relations. Human being intervention is required in this step due to the complexity of the process. For example, if there exist A-r1-C, A-r1-D, B-r1-C, and B-r1-D, they can be generalized to concept1{A,B}-r1-concept2{C,D} by union. However, it becomes difficult when the above example is extended to include concept1{A,B}-r1-E and con-cept2{C,D}-r2-F. One cannot conclude concept1{A,B}-r1-concept2{C,D,E} unless an exception indicating no E-r2-F is added. Alternatively, it can be generalized to con-cept1{A,B}-r1-concept3{E,concept2{C,D}}. The system interacts with users by prompting the dilemmas for resolutions along the process of a whole taxonomy. The task of the previous module, standard formalization, is usually a one-time effort (though it is an iterative process) and it needs significant domain experts' involvement. This module is different in that it is used in every workflow/task and extracted semantics can be accumulated in repository and used for improving future semantic association performance. Also, it can be relatively automated by using general linguistic processing technologies.</p><p>Standards, such as UniformatII and MasterFormat, addressed in this paper are functionally complementary to each other in an application domain and they are costly cross-referenced by domain experts in workflows due to their complexity (vast many-to-many mappings). This module basically is to automat the process by mimicking a domain expert doing cross-referencing from the context of a standard-compliant project specification, a script representation indexed of the standard, which defines intentionality. For example, the following text is quoted from a PPD <ref type="bibr" target="#b6">[7]</ref> under entity B2010 in UniformatII taxonomy:</p><formula xml:id="formula_1">B SHELL B20 EXTERIOR CLOSURE B2010 EXTERIOR WALLS 1.</formula><p>Exterior Wall Framing: Cold-formed, light gage steel studs, C-shape, galvanized finish, 6" metal thickness as designed by manufacturer according to American Iron and Steel Institute (AISI) Specification for the Design of Cold Formed Steel Structural Members, for L/240 deflection. Downside: specifications often contain note-style sentences.</p><p>Supposedly, the PPD is written by an architect and a contractor wants to estimate cost for exterior walls. He might comprehend that the wall framing will be made of coldformed steel studs (semantic). Based on his expertise, he identifies that its corresponding entity in Masterformat is 05410 Load bearing metal studs (association). The following paragraph shows how the ontology/relation statements being used for discovering the semantic under the context of entity B2010 that links the entity to MasterFormat entity 05410 (semantic association):</p><p>In the diagram, "steel" and "framing" match the statement 05100_1 (one of the identifiers of the relation statements exemplified in previous subsection) which is Metals (D5) used_for framing. The "steel" matches "Metals" through the transitive property of the relation, kind_of. The match is extended to statement 05400, which includes "cold-formed".</p><p>Finally "studs" is added to the match of statement 05410, through statement (05400_05410). Indeed the entity B2010 Exterior Wall in UniformatII has a semantic relationship with 05410 Load bearing metal studs in MasterFormat and the semantic can be described by the relation made_of.</p><p>One characteristic worthy of mentioning is that the entity B2010 Exterior Wall in the taxonomy provides a good context for helping refining the association. For instance, the above matching, even without the "framing" keyword, is still possible since the inherited semantic of the hierarchy, shell, closure, and exterior walls, has very close meaning as framing.</p><p>As shown in the above example, the documents or specifications that this research addresses have following characteristics:</p><p>1. Content has limited scope. It often details what, where, how, and when objects and activities being involved in a domain application. It usually contains rich semantics (author's intention for communicating with other stakeholders) related to standards (due to the agreement among stakeholders) that coordinate objects and activities in the domain.</p><p>2. Content are categorized according to taxonomy. In other words, text in a document has some assumption or context, which is inherited along the taxonomy hierarchy.</p><p>3. Terminologies are relatively unified and unambiguous.</p><p>4. Sentences are relatively free styled, such as notestyled or template-styled due to writing convention or standards.</p><p>These characteristics distinguish this research from others, such as <ref type="bibr" target="#b8">[9]</ref> and <ref type="bibr" target="#b14">[15]</ref> which extract shallow information from general or web documents.</p><p>In addition to the intrinsic semantics of standards, this module also explores their application or context semantics in order to achieve more effective semantic extraction. The application semantics depend on the stakeholders' view or interests, such as information they intent for. For example, a cost estimator might look for MasterFormat items and some numerical information so that they can link them to their MasterFormat-based cost databases. On the other hand, an inspector might be interested in the same information but in different view points that yield to different semantics. For example, to a cost estimator, "6" metal thickness" in the PPD means how much the studs with such thickness cost. But for an inspector, it means 6" thickness compliance to associated code.</p><p>In summary, this module extracts semantics from the instances (specifications) of multiple standards based on three kinds of ontologies: the ontology of the source standard, the B2010 Exterior Wall:</p><p>1. Exterior Wall Framing: Cold-formed, light gage steel studs, C-shape, galvanized finish, 6" metal thickness 05100_1 05400 05410 ontology of target standard, and the application ontology based on the stakeholders' views. The extracted semantics are evidences of semantic association of entities between source and target standards.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">MEASUREMENT OF AFFINITY</head><p>The ontology-based semantic extraction module can be implemented via a matching process between relation statements and text. The goal is to identify a set of matched relation statements of related entities with respect to their standards. For a given entity, its associated relation statements carry different weights depending on their positions in the taxonomy and the information content <ref type="bibr" target="#b15">[16]</ref> of their keywords. The measurement of affinity is to quantify the weights so that the degree of the closeness between matched relation statements and their associated entity can be determined. Based on the measurement, a ranking scheme can be devised to identify optimal semantic associations among all matches. The ranking scheme can be modeled as a function of the following factors:</p><p>1. Number of relation statements matched.</p><p>2. Number of keywords matched.</p><p>3. Quality of the matches. The measurement of the quality is an open question. Basically the more specific the matches are, the higher quality they represent. One effective way to model the quality is by their positions in the taxonomy (higher level means less specific and thus carries less weight) and by the information content of their keywords. The information content can be quantified by their inverse document frequency (IDF) <ref type="bibr" target="#b16">[17]</ref> combined with their counts in the taxonomy (appearing more times means less specific and thus carries less weight)</p><p>For instance, in the given example, several entities in Mas-terFormat contain "framing" and "Metals", which are all candidates for semantic association. The entity 05410 is considered as the optimal one because it matches more keywords along its taxonomy hierarchy and some of them, such as studs, are very specific with respect to both position and IDF.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">ARCHITECTURE</head><p>The major thrust of the research is to develop an integration framework that facilitates exploitation of semantics from taxonomy-based standards and instantiations of the standards to achieve higher interoperability between domain participants and their information systems. To demonstrate the applicability of the proposed approach toward the goal, this section shows an overall architecture depicting one possible implementation and its relationship with other related technologies.</p><p>In the framework shown in Figure <ref type="figure">2</ref>, relations and relation statements of various versions of standards written in natural languages are developed and uploaded via web-based tools to the system by stakeholders in the application domain. The taxonomy formalization along with the change management modules process them through parsing, normalization, generalization, linguistic processing (such as inflection, derivation, compounds, and synonyms), and indexing for incremental update in the ontology database. For a particular application, the stakeholders upload instances of the source standard (e.g., PPDs), target standard, and its application ontology. After processing the free text of PPD instances through linguistic techniques such as tokenization, chunk parsing, and grammatical function recognition <ref type="bibr" target="#b8">[9]</ref>, the system applies the semantic extraction and ranking algorithms, and returns/deposits extracted metadata and semantic association to the ontology database and also to the users or clients, if applicable, for feedback.</p><p>The integration of competing and complementary standards is a critical step for enhancing interoperability among heterogeneous systems using the standards. The proposed semantic association is only one aspect in this effort. It should be supplemented with other technologies such as ontology mapping, reconciling, and merging to provide a practical and complete solution. The framework includes a plug-in mechanism via XML-based interfaces and API for external software component integration.  </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Data</head><p>Human</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>ETIF</head><p>The formalized standards, their instances, users' application ontologies, and extracted metadata form a semantic rich ontology repository. Integrating the repository with other ontology techniques through the plug-in mechanism allows the effective construction of application domain ontology.</p><p>Web services enriched with the vision of the semantic web have emerged as a mainstream solution to system integration over the Internet. Following the same trend, the implementation of the proposed framework adopts the Web Ontology Language (OWL) <ref type="bibr" target="#b7">[8]</ref> with the intention of integrating building construction workflow systems via semantic web services.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">CONCLUSION AND FUTURE WORKS</head><p>This paper demonstrates the effective use of taxonomy for ontology developments and the semantic association of ontology for interoperability in a workflow system with building construction as the target example. It illustrates a systematic approach to semantic association through taxonomy formalization and ontology-based semantic extraction.</p><p>The overall system implementation in web environment is also proposed. Current activities of the research project include the complete ontological formalization of the Ma-terFormat and UniformatII standards, refinement of the affinity measure for general taxonomy, and the integration of the algorithms with dynamic workflow systems through semantic web services.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 Figure 1</head><label>11</label><figDesc>Figure 1 shown below depicts the generalized view or ontology of the relation statements shown in previous steps.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure</head><label></label><figDesc>Figure 2. Extensible Taxonomy-based Integration Framework (ETIF)</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1</head><label>1</label><figDesc>shows the mathematical properties of these relations that are used in the subsequent step for data normalization. They are also used for reasoning in knowledge extraction.</figDesc><table><row><cell>5-Metals</cell></row><row><cell>05100 Structural Metal Framing</cell></row><row><cell>05120 Structural steel</cell></row><row><cell>05140 Structural aluminum</cell></row><row><cell>05160 Metal framing systems</cell></row><row><cell>05400 Cold formed metal framing</cell></row><row><cell>05410 Load bearing metal studs</cell></row><row><cell>05420 Cold formed metal joists</cell></row><row><cell>05430 Slotted channel framing</cell></row><row><cell>Division 6 -Wood and Plastics</cell></row><row><cell>06100 Rough carpentry</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 1 .</head><label>1</label><figDesc>Mathematical Properties of the relations</figDesc><table><row><cell>Relations</cell><cell>Transitive</cell><cell>reflexive</cell><cell>antisymmetric</cell></row><row><cell>used_for</cell><cell>-</cell><cell>-</cell><cell>-</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head></head><label></label><figDesc>Load bearing metal studs" are kind_of Metal studs</figDesc><table><row><cell>6. "</cell></row><row><cell>The other advan-</cell></row><row><cell>tage is that domain experts who are not familiar with ontol-</cell></row><row><cell>ogy can directly express their knowledge in the simple</cell></row><row><cell>statements without communication overhead with knowl-</cell></row><row><cell>edge modeling experts.</cell></row><row><cell>The following are examples of relation statements that par-</cell></row><row><cell>tially describe the example shown in previous step.</cell></row><row><cell>1. Metals (D5), Wood (D6), Plastics (D6_1) are in-</cell></row><row><cell>stance_of Material (root) (D5_root, D6_root,</cell></row><row><cell>D6_1_root)</cell></row><row><cell>2. Metals (D5) are used_for framing 05100_1</cell></row><row><cell>3. Structural is a kind_of "metal framing" (05100_1)</cell></row><row><cell>05100</cell></row><row><cell>4. Cold formed is a kind_of "metal framing" (05100_1)</cell></row><row><cell>05400</cell></row><row><cell>5. Studes are made_of Metals (D5) (05410_1)</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_3"><head></head><label></label><figDesc>2. Extensible Taxonomy-based Integration Framework (ETIF)</figDesc><table><row><cell cols="2">Ontology DB</cell><cell></cell><cell></cell><cell></cell></row><row><cell cols="2">Standards, stances, Views, In-meta data, Rela-</cell><cell>Ontology Generation</cell><cell cols="2">Ontology Mapping, Reconciling, Merge, Data Mining</cell></row><row><cell>tions</cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell cols="2">Change Man-</cell><cell>Semantic</cell><cell></cell><cell></cell></row><row><cell>agement</cell><cell></cell><cell>Extraction &amp;</cell><cell cols="2">Ontology</cell></row><row><cell></cell><cell></cell><cell>Association</cell><cell>Editing</cell><cell>and</cell></row><row><cell>Taxonomy</cell><cell></cell><cell></cell><cell cols="2">Presentation</cell></row><row><cell cols="2">Formalization</cell><cell></cell><cell></cell><cell></cell></row><row><cell cols="2">Protocol Adapter</cell><cell cols="3">Component Plug-in: XML Interface &amp; API,</cell></row><row><cell></cell><cell></cell><cell>Internet</cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>Semantic Web</cell></row><row><cell></cell><cell></cell><cell>View: Appli-</cell><cell></cell><cell>Services</cell></row><row><cell></cell><cell>Instance,</cell><cell>cation Ontol-</cell><cell>Browsers:</cell><cell>Based Dy-</cell></row><row><cell>Standards.</cell><cell>PPD….</cell><cell>ogy, standard</cell><cell>PC, Mobile</cell><cell>namic Work-</cell></row><row><cell></cell><cell></cell><cell>IDs</cell><cell>Devices</cell><cell>flow Systems</cell></row></table></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="8.">ACKNOWLEDGMENTS</head><p>This work is partially supported by an NSF research grant ITR-0404113.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m">MasterFormat 95™</title>
				<meeting><address><addrLine>Alexandria, VA</addrLine></address></meeting>
		<imprint>
			<publisher>The Construction Specifications Institute</publisher>
			<date type="published" when="1995">1995</date>
		</imprint>
		<respStmt>
			<orgName>Construction Specifications Institute</orgName>
		</respStmt>
	</monogr>
	<note>edition</note>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">UNIFORMAT II Elemental Classification for Building Specifications, Cost Estimating, and Cost Analysis</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">P</forename><surname>Charette</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">E</forename><surname>Marshall</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">NISTIR 6389</title>
				<meeting><address><addrLine>Gaithersburg, MD</addrLine></address></meeting>
		<imprint>
			<date type="published" when="1999-10">October, 1999</date>
		</imprint>
		<respStmt>
			<orgName>National Institute of Standards and Technology</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">P</forename><surname>Gallaher</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">C</forename><surname>O'connor</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">L</forename><surname>Dettbarn</surname></persName>
		</author>
		<author>
			<persName><surname>Jr</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">T</forename><surname>Gilday</surname></persName>
		</author>
		<idno>04-867</idno>
		<title level="m">Cost Analysis of Inadequate Interoperability in the U.S. Capital Facilities Industry</title>
				<meeting><address><addrLine>Gaithersburg, MD</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2004-08">August, 2004</date>
		</imprint>
		<respStmt>
			<orgName>National Institute of Standards and Technology</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">NIST GCR</note>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Generic Schema Matching with Cupid</title>
		<author>
			<persName><forename type="first">Jayant</forename><surname>Madhavan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Philip</forename><forename type="middle">A</forename><surname>Bernstein</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Erhard</forename><surname>Rahm</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">at the Twenty Seventh International Conference on Very Large Databases (VLDB&apos;2001)</title>
				<meeting><address><addrLine>Roma, Italy</addrLine></address></meeting>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">The prompt suite: Interactive tools for ontology merging and mapping</title>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">F</forename><surname>Noy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Musen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Human-Computer Studies</title>
		<imprint>
			<biblScope unit="volume">59</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page" from="983" to="1024" />
			<date type="published" when="2003">2003</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Semantic matching of web services capabilities</title>
		<author>
			<persName><forename type="first">M</forename><surname>Paolucci</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Kawamura</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Payne</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Sycara</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The First International Semantic Web Conference (ISWC)</title>
				<imprint>
			<date type="published" when="2002">2002</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<author>
			<persName><forename type="first">Harold</forename><forename type="middle">J</forename><surname>Rosen</surname></persName>
		</author>
		<title level="m">Construction specifications writing : principles and procedures 5th edition</title>
				<editor>
			<persName><surname>Hoboken</surname></persName>
		</editor>
		<meeting><address><addrLine>N.J.</addrLine></address></meeting>
		<imprint>
			<publisher>J. Wiley</publisher>
			<date type="published" when="2005">c2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<author>
			<persName><forename type="first">Mike</forename><surname>Dean</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Guus</forename><surname>Schreiber</surname></persName>
		</author>
		<ptr target="http://www.w3.org/TR/2004/REC-owl-ref-20040210" />
		<title level="m">Editors OWL Web Ontology Language Reference, W3C Recommendation</title>
				<imprint>
			<date type="published" when="2004-02-10">10 February 2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<title level="m" type="main">Bootstrapping an Ontology-Based Information Extraction System, Intelligent Exploration of the Web</title>
		<author>
			<persName><forename type="first">A</forename><surname>Maedche</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Neumann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Staab</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2002">2002</date>
			<publisher>Springer</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">A Translation Approach to Portable Ontology Specification</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">R</forename><surname>Gruber</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Knowledge Acquisition</title>
		<imprint>
			<biblScope unit="volume">5</biblScope>
			<biblScope unit="page" from="199" to="220" />
			<date type="published" when="1993">1993</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">A Survey of Approaches to Automatic Schema Matching</title>
		<author>
			<persName><forename type="first">E</forename><surname>Rahm</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">A</forename><surname>Bernstein</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">The VLDB Journal</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="page" from="334" to="350" />
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Comparison of Schema Matching Evaluations</title>
		<author>
			<persName><forename type="first">H</forename><surname>Do</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Melnik</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Rahm</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 2nd Int. Workshop on Web Databases</title>
				<meeting>the 2nd Int. Workshop on Web Databases</meeting>
		<imprint>
			<publisher>German Informatics Society</publisher>
			<date type="published" when="2002">2002</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">The Chatty Web: Element Semantics through Gossiping</title>
		<author>
			<persName><forename type="first">K</forename><surname>Aberber</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Cudré-Mauroux</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hauswirth</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Proceedings of the 20 th International World Wide Web Conference</title>
				<imprint>
			<date type="published" when="2003">2003</date>
			<biblScope unit="page" from="197" to="206" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Learning to Map between Ontologies on the Semantic Web</title>
		<author>
			<persName><forename type="first">A</forename><surname>Doan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Madhavan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Domingos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Halevy</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">The VLDB Journal</title>
		<imprint>
			<biblScope unit="volume">12</biblScope>
			<biblScope unit="page" from="303" to="319" />
			<date type="published" when="2003">2003</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Ontology-based extraction and structuring of information from datarich unstructured documents</title>
		<author>
			<persName><forename type="first">David</forename><forename type="middle">W</forename><surname>Embley</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Douglas</forename><forename type="middle">M</forename><surname>Campbell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Randy</forename><forename type="middle">D</forename><surname>Smith</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Stephen</forename><forename type="middle">W</forename><surname>Liddle</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the seventh international conference on Information and knowledge management</title>
				<meeting>the seventh international conference on Information and knowledge management<address><addrLine>Bethesda, Maryland, United States</addrLine></address></meeting>
		<imprint>
			<date type="published" when="1998">November 02-07, 1998</date>
			<biblScope unit="page" from="52" to="59" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Ross</surname></persName>
		</author>
		<title level="m">A First Course in Probability</title>
				<imprint>
			<publisher>Macmillan Publishing</publisher>
			<date type="published" when="1976">1976</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Inverse document frequency (IDF): A measure of deviations from Poisson</title>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">W</forename><surname>Church</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">A</forename><surname>Gale</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Third Workshop on Very Large Corpora</title>
				<editor>
			<persName><forename type="first">D</forename><surname>Yarowsky</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">K</forename><surname>Church</surname></persName>
		</editor>
		<meeting>the Third Workshop on Very Large Corpora</meeting>
		<imprint>
			<publisher>Association for Computational Linguistics</publisher>
			<date type="published" when="1995">1995</date>
			<biblScope unit="page" from="121" to="130" />
		</imprint>
	</monogr>
</biblStruct>

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