Abstract
AbstractSundown of the twentieth century saw the emergence of the World Wide Web. A decade later, semantic web (SW) envisioned enriching of web-accessible information and services with machine-processable semantics to solve the problems of information management and sharing which are aroused by the success of the web. However, success of the SW largely depends on the availability of formal ontologies for representing and structuring information in different domains. To facilitate web ontology engineering (OE), methodologies are proposed by the researchers since years. However, OE particularly web OE is still immature and none of the methodologies is standardized for web OE projects as yet. This paper presents an evolutionary SW ontology engineering methodology called POEM. POEM presents a complete methodology comprising of various phases for performing conceptualization, designing, implementation, evaluation, and project management tasks. POEM exploits and incorporates the large experiences from the widel...
Highlights
Ontology is old genie in a new bottle
We have presented a methodology for Semantic web (SW) ontology building called practical ontology engineering model (POEM) that leverages the large valuable experiences and concepts from the widely accepted standards of software engineering and other state-of-the-art technologies
practical OE model for SW ontologies (POEM) is an evolutionary incremental methodology that consists of sequence of phases and activities for guiding SW ontology building projects from inception to deployment
Summary
Ontology is old genie in a new bottle. The term ontology was first used in Philosophy in the nineteenth century where it gave an organized justification of being (Breitmann, Casanova, & Truszkowski, 2007) and is a most relevant word in the knowledge engineering community (Corcho, FernándezLópez, & Gómez-Pérez, 2003). The proposed methodologies are valuable but are limited in scope due focusing mainly on the core web ontology building activities such as identifying classes, defining properties and relations between classes They have no definitions of strategies for ontological constructs identifications and application dependency/independency, and have completely ignored management activities (i.e. schedule and quality assurance) as well as supporting activities (ontology integration, ontology evaluation, and ontology documentation, etc.) which are essential for web ontology building projects like any other software development project. POEM divides the ontology building methodology into several cycles (i.e. iterations), a cycle into phases (i.e. process), and a phase into activities for requirements specifications, project planning and scheduling, risk analysis, implementation, and testing.
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
