FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W71604965> ?p ?o ?g. }

• W71604965 endingPage "9" @default.
• W71604965 startingPage "5" @default.
• W71604965 abstract "In this paper we describe how UML schemes can be converted into OWL Ontology, thus enabling reasoning on them by Semantic Web applications. The proposed solution is based on a three phases approach, the first step is to present the class diagram in the mathematical formulation and the second one is converting the UML Class into encoded text file, finally, the structure of the classification scheme is converted into OWL ontology. We demonstrate the practical applicability of our approach by showing how the results of reasoning on these OWL ontology can help improve the Web systems. Keywordscomponent; RDF, OWL, Web ontologie,UML 1.INTRODUCTION This document aims to define a correspondence between the class diagrams of Unified Modeling Language (UML) [1] and OWL using the mathematical representation of the class diagram. The OWL Web Ontology Language [2] is designed for use by applications that need to process the content of information instead of just presenting information to humans. The use of ontology Web is growing rapidly since the emergence of the Semantic Web. Most of the data is still modeled and stored in relational databases / objects and therefore out of reach for many applications of the Semantic Web. A critical requirement for the evolution of the current Web of documents into a Web of Data is the inclusion of the vast quantities of data stored in Relational Databases (RDB). The mapping of these vast quantities of data from RDB to the Resource Description Framework (RDF) has been the focus of a large body of research work in diverse domains. Some of the most notable approaches of this kind are R2O [3], D2RQ [4], Virtuoso RDF Views [5, 6] and DartGrid [7]. The R2O approach defines declarative and extensible language (in xml) to describe mapping between given RDB and an OWL ontology or RDFS schema so that tools can process this mapping and generate triples that correspond to source RDB data. G.Bumans et al [8] demonstrate a very simple standard SQLbased RDB to RDF/OWL mapping approach that is based on defining correspondence between the tables of the database and the classes of the ontology, as well as between table fields/links in the database and datatype/object properties in the ontology. UML models cannot be easily exchanged over the Web, the reasoning possibilities with UML models being also quite restricted. [9] and [10] propose a simples transformations between UML and ontology representation languages. Recently, some efforts arose in bringing together UML and the Semantic Web. Nevertheless, most of these approaches do not use all proprieties of the UML diagrams as a data source. In this direction several researches are underway to transform data into Web semantic (XML/RDF/OWL). J. Fong et al [11] proposes a method for Converting relational database into XML data with DOM. Wu and Hsieh [12] used a technique for mapping UML to XML. They created XSD from class diagrams, but this technique is very complex to generate the XSD file for each class diagram. In our previous work [13], we have developed a Framework for converting a class diagram into an XML document and show how to use Web files for the design of data based on the classification UML. Our approach for mapping is based on several steps. First step is to formulate the class diagram into a mathematical structure and transform it into an encoded text file (Section II). After the text file is imported into the system to build the structure of OWL diagram using the algorithm called GenarateOWL described in Section III, and finally the exported OWL file will be validated and stored 2.UML FOR THE SEMANTIC WEB A. Mathematical representation of UML Class. Modeling Layer allows the representation of the UML model into a logical representation. For this task, we have applied a mathematical approach for semantically enriching of the UML Model. In our approach, a class diagram in UML is represented as a set of classes, denoted as 4-tuple:   R O A N C C C C C C C UML , , , ( : :   " @default.
• W71604965 created "2016-06-24" @default.
• W71604965 creator A5042785802 @default.
• W71604965 creator A5086015490 @default.
• W71604965 date "2012-09-17" @default.
• W71604965 modified "2023-09-23" @default.
• W71604965 title "A New Method for Mapping UML Class into OWL Ontology" @default.
• W71604965 cites W1983519136 @default.
• W71604965 cites W2031162680 @default.
• W71604965 cites W2053173742 @default.
• W71604965 cites W2171884570 @default.
• W71604965 cites W2963784807 @default.
• W71604965 cites W3040898077 @default.
• W71604965 cites W640831942 @default.
• W71604965 cites W23685451 @default.
• W71604965 hasPublicationYear "2012" @default.
• W71604965 type Work @default.
• W71604965 sameAs 71604965 @default.
• W71604965 citedByCount "3" @default.
• W71604965 countsByYear W716049652013 @default.
• W71604965 countsByYear W716049652018 @default.
• W71604965 countsByYear W716049652020 @default.
• W71604965 crossrefType "journal-article" @default.
• W71604965 hasAuthorship W71604965A5042785802 @default.
• W71604965 hasAuthorship W71604965A5086015490 @default.
• W71604965 hasConcept C101230327 @default.
• W71604965 hasConcept C111472728 @default.
• W71604965 hasConcept C115408247 @default.
• W71604965 hasConcept C136764020 @default.
• W71604965 hasConcept C138885662 @default.
• W71604965 hasConcept C145644426 @default.
• W71604965 hasConcept C148792806 @default.
• W71604965 hasConcept C167379230 @default.
• W71604965 hasConcept C199360897 @default.
• W71604965 hasConcept C202446494 @default.
• W71604965 hasConcept C2129575 @default.
• W71604965 hasConcept C23123220 @default.
• W71604965 hasConcept C25810664 @default.
• W71604965 hasConcept C2777904410 @default.
• W71604965 hasConcept C29321653 @default.
• W71604965 hasConcept C41008148 @default.
• W71604965 hasConcept C50382505 @default.
• W71604965 hasConcept C61673122 @default.
• W71604965 hasConcept C71695816 @default.
• W71604965 hasConceptScore W71604965C101230327 @default.
• W71604965 hasConceptScore W71604965C111472728 @default.
• W71604965 hasConceptScore W71604965C115408247 @default.
• W71604965 hasConceptScore W71604965C136764020 @default.
• W71604965 hasConceptScore W71604965C138885662 @default.
• W71604965 hasConceptScore W71604965C145644426 @default.
• W71604965 hasConceptScore W71604965C148792806 @default.
• W71604965 hasConceptScore W71604965C167379230 @default.
• W71604965 hasConceptScore W71604965C199360897 @default.
• W71604965 hasConceptScore W71604965C202446494 @default.
• W71604965 hasConceptScore W71604965C2129575 @default.
• W71604965 hasConceptScore W71604965C23123220 @default.
• W71604965 hasConceptScore W71604965C25810664 @default.
• W71604965 hasConceptScore W71604965C2777904410 @default.
• W71604965 hasConceptScore W71604965C29321653 @default.
• W71604965 hasConceptScore W71604965C41008148 @default.
• W71604965 hasConceptScore W71604965C50382505 @default.
• W71604965 hasConceptScore W71604965C61673122 @default.
• W71604965 hasConceptScore W71604965C71695816 @default.
• W71604965 hasIssue "1" @default.
• W71604965 hasLocation W716049651 @default.
• W71604965 hasOpenAccess W71604965 @default.
• W71604965 hasPrimaryLocation W716049651 @default.
• W71604965 hasRelatedWork W101751036 @default.
• W71604965 hasRelatedWork W120522366 @default.
• W71604965 hasRelatedWork W1990094248 @default.
• W71604965 hasRelatedWork W2014585320 @default.
• W71604965 hasRelatedWork W2041447039 @default.
• W71604965 hasRelatedWork W2050174582 @default.
• W71604965 hasRelatedWork W2097270982 @default.
• W71604965 hasRelatedWork W2140795255 @default.
• W71604965 hasRelatedWork W214201719 @default.
• W71604965 hasRelatedWork W2186780989 @default.
• W71604965 hasRelatedWork W2296329277 @default.
• W71604965 hasRelatedWork W2364625113 @default.
• W71604965 hasRelatedWork W2416562408 @default.
• W71604965 hasRelatedWork W2742362814 @default.
• W71604965 hasRelatedWork W2806921620 @default.
• W71604965 hasRelatedWork W2980152150 @default.
• W71604965 hasRelatedWork W2988193897 @default.
• W71604965 hasRelatedWork W3034107741 @default.
• W71604965 hasRelatedWork W52848903 @default.
• W71604965 hasRelatedWork W1580023110 @default.
• W71604965 isParatext "false" @default.
• W71604965 isRetracted "false" @default.
• W71604965 magId "71604965" @default.
• W71604965 workType "article" @default.