%0 Book Section %1 Haugen13p169 %A Haugen, Øystein %B Domain Engineering %C Berlin %D 2013 %E Reinhartz-Berger, Iris %E Sturm, Arnon %E Clark, Tony %E Cohen, Sholom %E Bettin, Jorn %I Springer %K v1205 springer book software development engineering tool code generation zzz.sfit %P 159-186 %R 10.1007/978-3-642-36654-3_7 %T Domain-Specific Languages and Standardization: Friends or Foes? %X Domain-specific languages (DSLs) capture the domain knowledge through the constructs of the language, but making a good language takes more than combining a set of domain concepts in some random fashion. Creating a good language requires knowledge not only from the domain but also from the domain of language design. Generic abstraction concepts turn out to be useful for many different domains and thus for DSLs. In this chapter we discuss how DSLs can benefit from standardized generic languages to cope with abstraction needs. A successful combination will keep the DSL simple and its implementation maintainable while the generic language will add expressiveness and structuring means. We give examples of DSLs as well as general ones and use the examples to illustrate our advice on how to make a good language. We share experiences of language evolution and finally show an example of combining a generic language for variability with a DSL for train signaling. %@ 978-3-642-36653-6

@incollection{Haugen13p169, abstract = {Domain-specific languages (DSLs) capture the domain knowledge through the constructs of the language, but making a good language takes more than combining a set of domain concepts in some random fashion. Creating a good language requires knowledge not only from the domain but also from the domain of language design. Generic abstraction concepts turn out to be useful for many different domains and thus for DSLs. In this chapter we discuss how DSLs can benefit from standardized generic languages to cope with abstraction needs. A successful combination will keep the DSL simple and its implementation maintainable while the generic language will add expressiveness and structuring means. We give examples of DSLs as well as general ones and use the examples to illustrate our advice on how to make a good language. We share experiences of language evolution and finally show an example of combining a generic language for variability with a DSL for train signaling.}, added-at = {2013-11-24T17:32:22.000+0100}, address = {Berlin}, author = {Haugen, {\O}ystein}, biburl = {https://www.bibsonomy.org/bibtex/28426c80965f8df74b9cb44b16127731a/flint63}, booktitle = {Domain Engineering}, crossref = {ReinhartzBergerSturmEtAl2013}, doi = {10.1007/978-3-642-36654-3_7}, editor = {Reinhartz-Berger, Iris and Sturm, Arnon and Clark, Tony and Cohen, Sholom and Bettin, Jorn}, file = {SpringerLink:2013/Haugen13p169.pdf:PDF}, groups = {public}, interhash = {aea539049158de5ea41913d8d7894a04}, intrahash = {8426c80965f8df74b9cb44b16127731a}, isbn = {978-3-642-36653-6}, keywords = {v1205 springer book software development engineering tool code generation zzz.sfit}, pages = {159-186}, publisher = {Springer}, timestamp = {2013-11-24T17:32:22.000+0100}, title = {Domain-Specific Languages and Standardization: Friends or Foes?}, username = {flint63}, year = 2013 }