<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0">
			<channel>
			<title>Application Generation - DSL Evolution</title>
			<link>http://www.pbell.com/index.cfm</link>
			<description>A series of occasional musings on architecting, securing, optimizing and generating web based applications. By Peter Bell.</description>
			<language>en-us</language>
			<pubDate>Wed, 19 Jun 2013 09:48:00 -0400</pubDate>
			<lastBuildDate>Thu, 25 Jun 2009 16:15:00 -0400</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>test@test.com</managingEditor>
			<webMaster>test@test.com</webMaster>
			
			
			
			
			
			<item>
				<title>Transformation Based MetaModeling (what to do when your DSLs change)</title>
				<link>http://www.pbell.com/index.cfm/2009/6/25/Transformation-Based-MetaModeling-what-to-do-when-your-DSLs-change</link>
				<description>
				
				Generally the biggest issue with metamodeling is DSL evolution. You have a collection of DSLs that you use for building applications. However, you find an case where your DSL is not sufficiently expressive. Perhaps you have an attribute/property that really needs to be a class/element/concept with its own sub-properties. However, you already have lots of statements in the DSL, so what do you do? Generally there are three approaches . . .
				 [More]
				</description>
				
				<category>Application Generation</category>
				
				<category>Domain Specific Modeling</category>
				
				<category>DSL Evolution</category>
				
				<category>Domain Specific Languages</category>
				
				<pubDate>Thu, 25 Jun 2009 16:15:00 -0400</pubDate>
				<guid>http://www.pbell.com/index.cfm/2009/6/25/Transformation-Based-MetaModeling-what-to-do-when-your-DSLs-change</guid>
				
			</item>
			
		 	
			</channel></rss>
	

