Semantics-Based Filtering: Logic Programming’s Killer App

Gupta, Gopal; Guo, Hai-Feng; Karshmer, Arthur I.; Pontelli, Enrico; Iglesias, Juan Raymundo; Ranjan, Desh; Milligan, Brook G.; Datta, Nayana; Elkhatib, Omar; Noamany, Mohammed; Zhou, Xinhong

doi:10.1007/3-540-45587-6_7

Cited by 9 publications

(9 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

Section: Discussionmentioning

confidence: 99%

“…In fact, it has been applied to quite diverse scenarios [23]. For example, it has been used to map complex, multiple notations used by bioinformatics systems to each other [23] so that they are inter-operable; it has been used to systematically translate relational databases (data as well as queries) to object-oriented databases [14], as well as to translate Braille based mark-up notation (called Nemeth Math notation [10]) for mathematics to L A T E X. In the context of the Web, this approach has been used to automatically generate validating parsers from XML DTDs (the semantics of the language used to describe DTDs is expressed in terms of a DCG [22]; the generated DCG acts as a validating parser for the input XML DTD) and for translating HTML documents to VoiceXML in order to make the Web accessible via audio [11].…”

Section: Discussionmentioning

confidence: 99%

“…A relatively easy approach to accomplish this is to express the formal semantics of the mark-up language in terms of this executable notation. Such an approach has been developed in [23] using Horn Logic and denotational semantics. In this approach, to translate one notation, say L s to L t , the denotational semantics of L s is given in terms of the language constructs of L t .…”

Section: A Semantics Based Approach To Translationmentioning

confidence: 99%

“…First, to provide interoperability on the web, translators can be built that translate one format into another. Indeed this approach has been applied to translate one XML to another [23,21], as well as to convert HTML to VoiceXML in an attempt to make the web accessible via audio [11]. This helps in increasing the usability of the regular (i.e., non-semantic) web.…”

Section: Semantic Processing Of the Semantic Webmentioning

confidence: 99%

See 3 more Smart Citations

Semantic Processing of the Semantic Web

Patel

Gupta

2003

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. We develop a semantics based approach to process information on the semantic web. We show how Horn logic can be used to denotationally capture the semantics of mark-up languages designed for describing resources on the semantic web (such as RDF). The same approach can also be used to specify the semantics of query languages for the semantic web. The semantics of both the resource description languages and the query languages are executable and when put together can be used to compute answers to semantic web queries. The main advantage of this semantic-based approach to processing the semantic web is that these executable semantics can be developed extremely quickly. Thus, as the semantic web mark-up languages evolve rapidly, their implementations can be developed at the same pace. In this paper, we present our approach based on denotational semantics and Horn logic. Our approach is quite general, and applicable to any description format (XML, RDF, DAML, etc.), though in this paper we illustrate it via RDF (Resource Description Framework).

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Discussionmentioning

confidence: 99%

Section: A Semantics Based Approach To Translationmentioning

confidence: 99%

Section: Semantic Processing Of the Semantic Webmentioning

confidence: 99%

See 2 more Smart Citations

Semantic Processing of the Semantic Web

Patel

Gupta

2003

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…Software systems for translating notation from one format to another (Nemeth Braille Math code to L A T E X, computational biology formats to Nexus, etc.) have been developed [6]. 4.…”

Section: Applicationsmentioning

confidence: 99%

Language-based software engineering

Gupta¹

2015

Science of Computer Programming

Self Cite

View full text Add to dashboard Cite

Techniques for developing reliable, error free (and these days also secure) software have been a subject of research for a long time. A number of software engineering frameworks have been proposed, from the waterfall model [1] to aspect oriented frameworks [2]. In this short paper we present a language-based framework for software engineering [13]. In the language-based software engineering framework domain experts are the application developers. They program their applications in high level domain specific languages (DSLs). This approach, based on using high level DSLs, results in more robust, reliable and secure software.The task of developing a program to solve a specific problem involves two steps. The first step is to devise a solution procedure to solve the problem. This step requires a domain expert to use his/her domain knowledge, expertise, creativity and mental acumen to devise a solution to the problem. The second step is to code the solution in some executable notation (such as a computer programming language) to obtain a program that can then be run on a computer to solve the problem. In the second step the user is required to map the steps of the solution procedure to constructs of the programming language being used for coding. Both steps are cognitively challenging and require considerable amount of thinking and mental activity. The more we can reduce the amount of mental activity involved in both steps (e.g., via automation), the more reliable the process of software construction will be. Not much can be done about the first step as far as reducing the amount of mental activity is involved, however, a lot can be done for the second step. The amount of mental effort the programmer has to put in the second step depends on the "semantic" gap between the level of abstraction at which the solution procedure has been conceived and the various constructs of the programming language being used. Domain experts usually think at a very high level of abstraction while designing the solution procedures. As a result, the more low-level the programming language, the wider the semantic gap, and the harder the user's task. In contrast, if we had a language that was right at the level of abstraction at which the user thinks, the task of constructing the program would be much easier. A domain specific language indeed makes this possible.Note that for any kind of communication (including between programmers/users and the computer) the notation used for the communication determines how effectively and efficiently that communication can be understood/processed. A new, complex notation may take longer time to learn, but if the notation is carefully designed for the task/domain, then it allows far more complex things to be expressed and understood considerably more easily. It also encourages creativity, since people now have to simply focus on what to say, rather than on how to say it. This in turn affects productivity of the people (and machines) involved. A prime example of this is the position-based decimal notation...

show abstract