ACM Computing Surveys (CSUR)
Object-oriented programming in the BETA programming language
Object-oriented programming in the BETA programming language
Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Domain-specific languages: an annotated bibliography
ACM SIGPLAN Notices
On the representation of roles in object-oriented and conceptual modelling
Data & Knowledge Engineering
On the criteria to be used in decomposing systems into modules
Communications of the ACM
ACM Transactions on Software Engineering and Methodology (TOSEM)
Logic, Programming, and PROLOG
Logic, Programming, and PROLOG
Automata and Computability
Abstraction mechanisms in the BETA programming language
POPL '83 Proceedings of the 10th ACM SIGACT-SIGPLAN symposium on Principles of programming languages
Software Engineering, An Advanced Course, Reprint of the First Edition [February 21 - March 3, 1972]
The XML Query Language Xcerpt: Design Principles, Examples, and Semantics
Revised Papers from the NODe 2002 Web and Database-Related Workshops on Web, Web-Services, and Database Systems
Essentials of Constraint Programming
Essentials of Constraint Programming
JTS: Tools for Implementing Domain-Specific Languages
ICSR '98 Proceedings of the 5th International Conference on Software Reuse
Aspect-Oriented Programming with AspectJ
Aspect-Oriented Programming with AspectJ
Aspect-Oriented Programming is Quantification and Obliviousness
Aspect-Oriented Programming is Quantification and Obliviousness
OOPSLA '04 Proceedings of the 19th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Classbox/J: controlling the scope of change in Java
OOPSLA '05 Proceedings of the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Towards Collaborative Environments for Ontology Construction and Sharing
CTS '06 Proceedings of the International Symposium on Collaborative Technologies and Systems
Just the right amount: extracting modules from ontologies
Proceedings of the 16th international conference on World Wide Web
Applied Ontology - Roles, an interdisciplinary perspective
A precise model for contextual roles: The programming language ObjectTeams/Java
Applied Ontology - Roles, an interdisciplinary perspective
GPCE '08 Proceedings of the 7th international conference on Generative programming and component engineering
Structure-Based Partitioning of Large Ontologies
Modular Ontologies
Combining OWL ontologies using E-Connections
Web Semantics: Science, Services and Agents on the World Wide Web
Modular web queries: from rules to stores
OTM'07 Proceedings of the 2007 OTM Confederated international conference on On the move to meaningful internet systems - Volume Part II
Reuse in semantic applications
Proceedings of the First international conference on Reasoning Web
Attribute grammar-based language extensions for java
ECOOP'07 Proceedings of the 21st European conference on Object-Oriented Programming
Hi-index | 0.00 |
Intelligent applications and agents on the Semantic Web typically need to be specified with, or interact with specifications written in, many different kinds of formal languages. Such languages include ontology languages, data and metadata query languages, as well as transformation languages. As learnt from years of experience in development of complex software systems, languages need to support some form of component-based development. Components enable higher software quality, better understanding and reusability of already developed artifacts. Any component approach contains an underlying component model, a description detailing what valid components are and how components can interact. With the multitude of languages developed for the Semantic Web, what are their underlying component models? Do we need to develop one for each language, or is a more general and reusable approach achievable? We present a language-driven component model specification approach. This means that a component model can be (automatically) generated from a given base language (actually, its specification, e.g. its grammar). As a consequence, we can provide components for different languages and simplify the development of software artifacts used on the Semantic Web.