FRINK Linked Data Fragments server

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

• W2186686914 abstract "Abstract—In this paper we describe a query language calledPFSQL (Priority Fuzzy Structured Query Language) that, besidebasic fuzzy capabilities, adds the possibility to specify prioritiesfor fuzzy statements. We give an analysis of possibilities to extendthe SQL language and briefly describe the GPFCSP (GeneralizedPrioritized Fuzzy Constraint Satisfaction Problem) systems, atheoretical concept vital for the implementation of the PFSQLinterpreter. In the following, we describe the most importantideas used in the process of the interpreter implementation. Asone of the most innovative ideas we present the fuzzy JDBC (JavaDatabase Connectivity) driver as a framework for the PFSQLinterpreter. I. I NTRODUCTION In this section we will shortly describe the notion of FRDB(Fuzzy-Relational Databases) and PFSQL, and give somepointers on how the fuzzy logic enriched databases have beendeveloping in the past. Relational databases are not suitablefor representation of imprecise, uncertain or inconsistent in-formation, thus they require add-onns to handle these typesof information. The most common add-on is to allow theattributes to have values that are fuzzy sets on the attributedomain, which results in FRDB. The idea to use fuzzy setsand fuzzy logic to extend existing database models to includethese possibilities has been utilized since the 1980s. Althoughthis area has been researched for a long time, implementationsare rare.Literature contains references to several models of fuzzyknowledge representation in relational databases. For example,the Buckles-Petry model [1] is the first model that introducessimilarity relations in the relational model. The GEFRED(Generalized Model of Fuzzy Relational Databases) model[2] is a probabilistic model that refers to generalized fuzzydomains and admits the possibility distribution in domains. Itincludes the case where the underlying domain is not numeric,but contains scalars of any type. Also, it contains the notion ofunknown, undefined and null values. It experienced subsequentexpansions, such as [3], [4]. Zvieli and Chen [5] offereda first approach to incorporate fuzzy logic in ER (Entity-Relationship) model. Their model allows fuzzy attributes inentities and relationships. Chen and Kerre [6] introduced thefuzzy extension of several major EER concepts. Chaudhry,Moyne and Rundensteiner [7] proposed a method for design-ing fuzzy relational databases following the extension of theER model of Zvieli and Chen. They propose a way to converta crisp database into a fuzzy one.Galindo, Urrutia and Piattini [8] describe a way to use fuzzyEER (Extended Entity-Relationship) to model the database andhow to represent modeled fuzzy knowledge using relationaldatabase in detail. In addition they describe specification andimplementation of the FSQL - an SQL language with fuzzycapabilities.In [9] and [10] authors have studied the possibilities toextend the relational model with fuzzy logic capabilities. Thesubject was elaborated in [11], where a detailed model of fuzzyrelational database was given. Moreover, using the concept ofGPFCSP from [12] and [13] authors have found a way tointroduce priority queries into FRDB, which resulted in thePFSQL query language. In [14] and [15] authors introducesimilarity relations on the fuzzy domain which are used toevaluate FRDB conditions.In this paper we present the basics of the PFSQL - an SQLextended using priority fuzzy logic. We give an overview ofthe GPFCSP - a theoretical background for the constructionof the interpreter for the PFSQL. Next, we give some pointersand ideas about the process of the interpreter implementation.We present the fuzzy JDBC driver as a framework for thePFSQL interpreter. In the end, the most important differencesbetween the PFSQL and the FSQL, one of the most advancedlanguages of this kind today, are explained.II. T" @default.
• W2186686914 created "2016-06-24" @default.
• W2186686914 creator A5036838008 @default.
• W2186686914 date "2009-01-01" @default.
• W2186686914 modified "2023-09-27" @default.
• W2186686914 title "An Interpreter for Priority Fuzzy Logic Enriched SQL" @default.
• W2186686914 cites W132151029 @default.
• W2186686914 cites W1536777985 @default.
• W2186686914 cites W1964228009 @default.
• W2186686914 cites W2022954591 @default.
• W2186686914 cites W2072960837 @default.
• W2186686914 cites W2128987286 @default.
• W2186686914 cites W2129398837 @default.
• W2186686914 cites W2150269435 @default.
• W2186686914 cites W2161568314 @default.
• W2186686914 cites W2163044634 @default.
• W2186686914 cites W2166024418 @default.
• W2186686914 cites W35516056 @default.
• W2186686914 cites W188753855 @default.
• W2186686914 hasPublicationYear "2009" @default.
• W2186686914 type Work @default.
• W2186686914 sameAs 2186686914 @default.
• W2186686914 citedByCount "0" @default.
• W2186686914 crossrefType "journal-article" @default.
• W2186686914 hasAuthorship W2186686914A5036838008 @default.
• W2186686914 hasConcept C122783720 @default.
• W2186686914 hasConcept C124101348 @default.
• W2186686914 hasConcept C127385683 @default.
• W2186686914 hasConcept C148671577 @default.
• W2186686914 hasConcept C154945302 @default.
• W2186686914 hasConcept C17350324 @default.
• W2186686914 hasConcept C199360897 @default.
• W2186686914 hasConcept C40207289 @default.
• W2186686914 hasConcept C41008148 @default.
• W2186686914 hasConcept C42011625 @default.
• W2186686914 hasConcept C510870499 @default.
• W2186686914 hasConcept C5655090 @default.
• W2186686914 hasConcept C58166 @default.
• W2186686914 hasConcept C77088390 @default.
• W2186686914 hasConcept C80444323 @default.
• W2186686914 hasConceptScore W2186686914C122783720 @default.
• W2186686914 hasConceptScore W2186686914C124101348 @default.
• W2186686914 hasConceptScore W2186686914C127385683 @default.
• W2186686914 hasConceptScore W2186686914C148671577 @default.
• W2186686914 hasConceptScore W2186686914C154945302 @default.
• W2186686914 hasConceptScore W2186686914C17350324 @default.
• W2186686914 hasConceptScore W2186686914C199360897 @default.
• W2186686914 hasConceptScore W2186686914C40207289 @default.
• W2186686914 hasConceptScore W2186686914C41008148 @default.
• W2186686914 hasConceptScore W2186686914C42011625 @default.
• W2186686914 hasConceptScore W2186686914C510870499 @default.
• W2186686914 hasConceptScore W2186686914C5655090 @default.
• W2186686914 hasConceptScore W2186686914C58166 @default.
• W2186686914 hasConceptScore W2186686914C77088390 @default.
• W2186686914 hasConceptScore W2186686914C80444323 @default.
• W2186686914 hasLocation W21866869141 @default.
• W2186686914 hasOpenAccess W2186686914 @default.
• W2186686914 hasPrimaryLocation W21866869141 @default.
• W2186686914 hasRelatedWork W1525196937 @default.
• W2186686914 hasRelatedWork W1860944052 @default.
• W2186686914 hasRelatedWork W1886864274 @default.
• W2186686914 hasRelatedWork W1996407745 @default.
• W2186686914 hasRelatedWork W2040534140 @default.
• W2186686914 hasRelatedWork W2068245942 @default.
• W2186686914 hasRelatedWork W2085238338 @default.
• W2186686914 hasRelatedWork W2116446453 @default.
• W2186686914 hasRelatedWork W2120276080 @default.
• W2186686914 hasRelatedWork W2139040790 @default.
• W2186686914 hasRelatedWork W2252900913 @default.
• W2186686914 hasRelatedWork W2385564014 @default.
• W2186686914 hasRelatedWork W2611462593 @default.
• W2186686914 hasRelatedWork W2739283891 @default.
• W2186686914 hasRelatedWork W3181783712 @default.
• W2186686914 hasRelatedWork W370767669 @default.
• W2186686914 hasRelatedWork W826471991 @default.
• W2186686914 hasRelatedWork W98348355 @default.
• W2186686914 hasRelatedWork W2181920908 @default.
• W2186686914 hasRelatedWork W2578793321 @default.
• W2186686914 isParatext "false" @default.
• W2186686914 isRetracted "false" @default.
• W2186686914 magId "2186686914" @default.
• W2186686914 workType "article" @default.