<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SQL queries in UML</title>
	<atom:link href="http://abstratt.com/blog/2009/03/18/sql-queries-in-uml/feed/" rel="self" type="application/rss+xml" />
	<link>http://abstratt.com/blog/2009/03/18/sql-queries-in-uml/</link>
	<description>We have one obsession: stopping people from writing so much code</description>
	<lastBuildDate>Thu, 12 Jan 2012 07:22:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Un café con Rafael Chaves (TextUML Toolkit) &#124; MOdeling LAnguages</title>
		<link>http://abstratt.com/blog/2009/03/18/sql-queries-in-uml/comment-page-1/#comment-1668</link>
		<dc:creator>Un café con Rafael Chaves (TextUML Toolkit) &#124; MOdeling LAnguages</dc:creator>
		<pubDate>Wed, 09 Mar 2011 22:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://abstratt.com/blog/?p=146#comment-1668</guid>
		<description>[...] JC - Have you thought in extending TextUML with some basic OCL support (i.e. mixing simple OCL constraints inline with the textual definition of the class diagram as a way to simplify the writing of basic OCL constraints)   RC - There is some overlap between Action Semantics and OCL and at some point I was trying to see if it was possible to merge them or use both of them at the same time but a lot of effort is needed to bridge them. The corresponding metamodels do not work together that well. I wanted to allow using OCL expressions within Action Semantics specifications but I realised that would require changing/extending the metamodels. For instance, the concept of variable in OCL is not equivalent to the concept of variable in Action Semantics. Also, I was interested in the concept of OCL collections (and all operations defined to manipulate them) since because I needed that kind of support and Action Semantics has no direct support for them. In Action Semantics it is very convoluted to apply an operation on all instances of a class and things like this so as a workaround I ended up avoiding the Action Semantics support for building sets of objects and trying to mimic what you have in OCL by having some predefined classes in TextUML that represent collections and provide some operations for them (for more details on this check  this blog post  [...]</description>
		<content:encoded><![CDATA[<p>[...] JC &#8211; Have you thought in extending TextUML with some basic OCL support (i.e. mixing simple OCL constraints inline with the textual definition of the class diagram as a way to simplify the writing of basic OCL constraints)   RC &#8211; There is some overlap between Action Semantics and OCL and at some point I was trying to see if it was possible to merge them or use both of them at the same time but a lot of effort is needed to bridge them. The corresponding metamodels do not work together that well. I wanted to allow using OCL expressions within Action Semantics specifications but I realised that would require changing/extending the metamodels. For instance, the concept of variable in OCL is not equivalent to the concept of variable in Action Semantics. Also, I was interested in the concept of OCL collections (and all operations defined to manipulate them) since because I needed that kind of support and Action Semantics has no direct support for them. In Action Semantics it is very convoluted to apply an operation on all instances of a class and things like this so as a workaround I ended up avoiding the Action Semantics support for building sets of objects and trying to mimic what you have in OCL by having some predefined classes in TextUML that represent collections and provide some operations for them (for more details on this check  this blog post  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

