#SLE09

International Conference on Software Language Engineering

13 Oct, 21:18 @APierantonio: back from #models09 and working on the call-for-lectures: great proposals (including some from the organizers of both #models09 and #sle09) ※ @

12 Oct, 22:58 @AVallecillo: Back home after excellent #models09 and #sle09 (and two days off). 200+ mails waiting... ※ @
21:51 @tvdstorm: Back home finally. Enjoyed #sle09, #gpce09 and #model09 though (in that order). ※ @
2:47 @dskolovos: denver airport is apparently the subject of (yet another) conspiracy theory youtube.com #models09 #sle09 ※ @

11 Oct, 13:34 @zef: Any #sle09 people on Google Wave? Join this one: google.com (hope this type of link works) ※ @
3:57 @notquiteabba: Met some people at #sle09 w/o experience in Happy Tree Friends; here is a good one I didn't knew myself: youtube.com ※ @

10 Oct, 19:01 @anyahelene: Back in Bergen again after #gpce09 / #sle09. Tired and exhausted, but inspired by the #pepm10 deadline extension... ※ @
16:29 @cwende: goodbye snowy denver #gpce09 #models09 #sle09 twitpic.com ※ @
14:57 @renggli: Back in Switzerland after a successful #sle09 conference in Denver and exciting days in Colorado Springs. ※ @
11:35 @EelcoVisser: Back in AMS after #gpce09 #sle09 #models09; two weeks to prepare for (the last) #oopsla09 ※ @

9 Oct, 23:07 @JBezivin: Will do that Ralf. Thanks for organizing such a nice event. ※ @
22:59 @JBezivin: JBezivin #FollowFriday #SLE09 #GPCE09 #MODELS09 @dgasevic @DamienCassou @softmodeling @notquiteabba @renggli @dgroenewegen etc. ※ @
- 23:03 @notquiteabba: @JBezivin Please send me or Bardia the slides for your great SLE keynote. We'll put them online; I want to study them in slow motion. ※ @
22:52 @JBezivin: #FollowFriday #SLE09 #GPCE09 #MODELS09 @EelcoVisser @fhe @zef @dskolovos @tvdstorm @cwende @richpaige @Felienne @fbahr @avandeursen ※ @
22:42 @JBezivin: #FollowFriday to all Denver twitters #SLE09 #GPCE09 #MODELS09 ※ @
20:26 @JBezivin: Next great meeting in #MALAGA for #Tools2010 federated conferences in June 2010 including #ICMT2010. (#Models09 #SLE09 #GPCE09) ※ @
20:21 @EelcoVisser: #models09, #gpce09 and #sle09 are over and my next #WebDSL screencast is done; just out of time for rendering and uploading it ※ @
20:13 @fhe: #models09, #gpce09 and #sle09 triple-conference was great! Heading home now. ※ @

8 Oct, 15:38 @zef: Writing portable DSLs is hot! stackoverflow.com #sle09 #models09 #pil ※ @
7:31 @softmodeling: RT @dskolovos: programming with pictures and modelling with text. who would have thought? #models09 #sle09 ※ @
3:55 @acherm: RT @dgasevic Thank you all for attending to #sle09 and make it such a nice experience for all of us. Looking forward to meeting you all next ※ @
1:29 @JBezivin: twitpic.com - Discussing #SLE09 ※ @
1:27 @cwende: RT @dskolovos programming with pictures and modelling with text. who would have thought? #models09 #sle09 ※ @
0:50 @dskolovos: programming with pictures and modelling with text. who would have thought? #models09 #sle09 ※ @
0:27 @EelcoVisser: RT @djspiewak: "We should make generalized parsing more palatable. " Yes, lets do that; lets discuss with higher bandwidth medium #sle09 ※ @
0:12 @notquiteabba: yes, very nice #sle09 presentation (RT @JBezivin: twitpic.com) but I liked the one on language boxes more. ※ @

7 Oct, 23:03 @notquiteabba: Now that #sle09 is over, the steering committee is frantically busy with figuring out details for #sle10. Let's grow further! ※ @
23:01 @zef: It seems that the #sle09 audience is more Twitter aware than the #models09 audience. ※ @
21:49 @avandeursen: @zef Congrats with your best presentation award for PIL! strategoxt.org #sle09 ※ @
16:37 @anyahelene: SLE was great; already looking forward to next year, hopefully in Malaga... #sle09 ※ @
16:03 @dgasevic: Thank you all for attending to #sle09 and make it such a nice experience for all of us. Looking forward to meeting you all next year :-)! ※ @
15:40 @dgroenewegen: #sle09 was a nice conference, WebDSL received positive attention. ※ @
15:07 @dskolovos: RT @richpaige: Dimitris Kolovos: "Text is more sexy than pictures". Lots of agreement on that! #SLE09 <- not always eboi.deviantart.com ※ @
14:38 @zef: Want to give better presentations? Have a look at presentation zen, also buy the book, it's worth it: presentationzen.com #sle09 #models09 ※ @
14:25 @JBezivin: Introducing Steve Mellor at the #Models09 first session this morning. #SLE09 is now finished and was very successful. ※ @
14:18 @guwac: #sle09 is over. time to go back to Berlin. come on delta, bring me home. ※ @
11:34 @akuhn: Congrats @renggli! // RT @tvdstorm @zef: I would say the language boxes talk by Lukas Renggli is the most impressive so far. #sle09 ※ @
11:28 @akuhn: The same for Java, iam.unibe.ch // RT @djspiewak: demo, creating a Roman Numerals language extension for Smalltalk. #sle09 ※ @
6:31 @richpaige: Found really good Italian food at Denver Tech Centre, celebrating a successful SLE'09. #SLE09 ※ @
6:15 @zef: #sle09 was great! Also very happy to have been selected as the best presentation. Sadly didn't get the shirt, because I already had one. ※ @
5:19 @JBezivin: RT @guwac@fhe: #sle09 was really nice! Looking forward to (Oslo | Malaga | Eindhoven) in 2010 ;-). Thx to all. ※ @
3:53 @guwac: RT @fhe: #sle09 was really nice! Looking forward to (Oslo | Malaga | Eindhoven) in 2010 ;-) ※ @
2:58 @fhe: #sle09 was really nice! Looking forward to (Oslo | Malaga | Eindhoven) in 2010 ;-) ※ @
2:03 @AccountLottery: RT: Won the final #sle09 T-shirt lottery. Had to answer the following quiz-question: who invented the term ".. twitter.com ※ @
2:00 @tvdstorm: Won the final #sle09 T-shirt lottery. Had to answer the following quiz-question: who invented the term "grammar engineering". #lol ※ @
- 14 Oct, 14:13 @fbahr: @tvdstorm [Won the final #sle09 T-shirt lottery … quiz-question: Who invented the term "grammar engineering"?] #Answer? ※ @
  - 22 Oct, 21:19 @tvdstorm: @fbahr Winning #answer was @notquiteabba. But according to the man himself and @grammarware, natural language people used the term before. ※ @
    - 21:29 @fbahr: @tvdstorm That would have been my point … nevertheless, the 'winner' writes history ;-) ※ @
1:33 @richpaige: Good presentation by Uwe Ralf Laemmel Jugel on generating smart wrapper libraries. #SLE09 ※ @
1:29 @zef: .@notquiteabba did a good Uwe Jugel impression. #sle09 ※ @
1:16 @EelcoVisser: yUML generates cute diagrams, but fonts are hard to read when used on slides #sle09 (feedback for @tobinharris ) ※ @
1:13 @EelcoVisser: Ralf Laemmel: "API coverage (usage) is often minimal" confirms our choice to replace Hibernate with minimal ORM subset #sle09 ※ @
1:09 @zef: RT @richpaige: Dimitris Kolovos: "Text is more sexy than pictures". Lots of agreement on that! #SLE09 ※ @
1:02 @EelcoVisser: RT @richpaige: Dimitris Kolovos: "Text is more sexy than pictures". Lots of agreement on that! #SLE09 ※ @
1:01 @JBezivin: RT @richpaige Dimitris Kolovos: "Text is more sexy than pictures". Lots of agreement on that! #SLE09 ※ @
0:57 @richpaige: Dimitris Kolovos: "Text is more sexy than pictures". Lots of agreement on that! #SLE09 ※ @
0:57 @zef: Just registered strategoxt.org #pil #sle09 ※ @
0:46 @richpaige: Domain specific metamodelling #SLE09 ※ @
0:45 @FAISTECH: RT @fabfas Another example of Eclipse being used in modeling research. It really is ubiquitous. #sle09 << nice to hear ※ @
0:14 @richpaige: Clock stuff that Francois is discussing seems related to time bands, e.g., paper Time bands in System Structure by Burns and Baxter #SLE09 ※ @
0:13 @zef: Already got an offer to develop a SmallTalk back-end for #pil and a potential user who wants to use it for his dsl. #sle09 ※ @
- 0:14 @EelcoVisser: @zef There is also interest for a PHP back-end for PIL #pil #sle09 ※ @
0:11 @djspiewak: To summarize: PEGs are very nice, but also extremely risky. They don't absolve the developer from thinking about ambiguity. #sle09 ※ @
0:06 @richpaige: Francois Terrier talking about multi-level modelling. #SLE09 ※ @

6 Oct, 23:31 @djspiewak: I think that perhaps PEG *recognizers* are closed under composition, whereas parsers may produce different results. #sle09 ※ @
23:26 @zef: RT @djspiewak: I nominate Lukas for an SLE T-Shirt just because his talk was the coolest. #sle09 ※ @
23:23 @richpaige: Preparing for our talk on Domain-Specific Metamodelling in an hour. #SLE09 ※ @
23:13 @JBezivin: ReMODD project presented by Betty Cheng at the educator symposium. #models #sle09 ※ @
23:13 @EelcoVisser: Language composition with PEGs is dynamic scoping for languages; parts of a language maybe shadowed without developer being aware #sle09 ※ @
- 23:16 @djspiewak: @EelcoVisser Only if the composed fragment happens to accept the *exact* same input as the shadowed bit. #sle09 ※ @
  - 23:19 @EelcoVisser: @djspiewak if there is an overlap between the languages; doesn't need to be the entire language #sle09 ※ @
    - 23:22 @djspiewak: @EelcoVisser Well, it's more than an overlap. The *entire* parse would have to complete successfully along both paths. #sle09 ※ @
      - 23:25 @EelcoVisser: @djspiewak yes, that is the definition of ambiguity #sle09 ※ @
        23:28 @djspiewak: @EelcoVisser Right, so what you're saying is that you don't like the fact that ambiguity must be predicted by the developer? #sle09 ※ @
        7 Oct, 0:09 @EelcoVisser: @djspiewak Indeed; with PEGs ambiguities are not detected, neither statically nor dynamically #sle09 ※ @
        0:10 @djspiewak: @EelcoVisser Well, static detection of ambiguity is undecidable in general, but your point is well taken. #sle09 ※ @
        0:13 @EelcoVisser: @djspiewak For subsets of CFG ambiguity is decidable, as in the Silver/Copper approach (i.e. LR) #sle09 ※ @
        0:14 @djspiewak: @EelcoVisser Hmm, that's true. I wonder if it would be possible to statically check PEGs in such a fashion. #sle09 ※ @
        23:29 @djspiewak: @EelcoVisser The developer would have to understand the ambiguity anyway in order to resolve the parse forest. #sle09 ※ @
        7 Oct, 0:11 @EelcoVisser: @djspiewak with SDF/SGLR an ambiguity produces a parse forest, i.e. notification of ambiguity + artifact that can be inspected #sle09 ※ @
        0:12 @djspiewak: @EelcoVisser Right. That works because SGLR is generalized. Most people are leery of generalized parsing though. #sle09 ※ @
        0:14 @EelcoVisser: @djspiewak And we should take emotions into account because? #sle09 ※ @
        0:21 @djspiewak: @EelcoVisser Well, if nobody uses the tool, then it doesn't really matter how safe it is. #sle09 ※ @
        1:36 @EelcoVisser: @djspiewak Agreed; but what can we do if ppl are just 'leery about generalized parsing' and not convinceable by technical arguments? #sle09 ※ @
        1:41 @djspiewak: @EelcoVisser I think we have to find a way to make generalized parsing more palatable. #sle09 ※ @
        1:41 @djspiewak: @EelcoVisser I think the two big issues are: flow is unintuitive ("worse" than standard LR) and parse forests are scary. #sle09 ※ @
        1:42 @djspiewak: @EelcoVisser IMHO, the flow problem is neatly solved by GLL. As for the parse forests... Disambiguation filters might help there. #sle09 ※ @
    - 23:23 @djspiewak: @EelcoVisser PEGs will backtrack as soon as they hit a failure. That backtracking works even after a reduce. #sle09 ※ @
23:09 @richpaige: Coffee. Coffee. Coffee. #SLE09 ※ @
- 23:14 @JBezivin: @richpaige Thanks Richard, I'm coming to coffee. #sle09 ※ @
23:08 @djspiewak: My airport shuttle is late, and I'm missing the rest of #sle09. Not a happy combination. ※ @
23:05 @djspiewak: I nominate Lukas for an SLE T-Shirt just because his talk was the coolest. #sle09 ※ @
23:03 @djspiewak: I was immensely impressed with the Language Boxes demo. It's too bad we can't embed video in LaTeX for printing. #sle09 ※ @
23:01 @tvdstorm: Totally agree: RT @zef I would say the language boxes talk by Lukas Renggli is the most impressive so far (to me). #sle09 ※ @
23:01 @richpaige: Good debate on language composition! #SLE09 ※ @
22:56 @zef: I would say the language boxes talk by Lukas Renggli is the most impressive so far (to me). #sle09 ※ @
22:55 @tvdstorm: Language Boxes by Lukas Renggli et al.: scoped language extension with support for debugging, syntax highlighting etc. Cool stuff. #sle09 ※ @
22:53 @djspiewak: Smalltalk looks a lot like Ioke. Absolute awesomeness would be Squeak-style tooling for that language. @olabini #sle09 ※ @
22:52 @djspiewak: Language Boxes demo is over. Too bad, it was really quite impressive! #sle09 ※ @
22:50 @djspiewak: Cue spontaneous applause from audience. #sle09 ※ @
22:50 @djspiewak: Wow. Just by defining the language extension for Smalltalk, we get Squeak tooling support (debug, highlighting) for free. #sle09 ※ @
22:49 @djspiewak: Oh here we go...I'm drooling over Smalltalk again. #sle09 ※ @
- 23:15 @michaelg: @djspiewak I don't know what I'd do without Smalltalk, it's the punchline to so many of my jokes. ※ @
  - 23:18 @djspiewak: @michaelg Heh. You wouldn't be laughing if you saw the same demo. Really wild stuff. #sle09 ※ @
22:48 @djspiewak: Smalltalk example. #sle09 twitpic.com ※ @
22:47 @djspiewak: Compositional conflicts are handled elegantly by Packrat parsing. IMHO, Packrat/PEG is the absolute best way to compose languages. #sle09 ※ @
- 22:49 @psnively: @djspiewak You mean parsing, presumably. Composing semantics is another matter entirely... ※ @
  - 22:54 @djspiewak: @psnively Example. Semantic composition is much harder, though not quite as bad if you're using attribute grammars. #sle09 ※ @
22:44 @djspiewak: Why is Packrat parsing more or less deterministic than vanilla PEGs? #sle09 ※ @
22:44 @zef: SmallTalk is cool. #sle09 ※ @
- 22:45 @grammarware: @zef ahahaha, it took #SLE09 to convince you of that? ※ @
  - 22:47 @zef: @grammarware no, but it gave more examples of its awesomeness :) #sle09 ※ @
22:42 @JBezivin: Jordi Cabot presenting the new MDE Diploma going to open in February 200 at Ecole des Mines de Nantes in France #SLE09 #MODELS09 ※ @
22:42 @djspiewak: I've seen demos of Squeak in the past, but the dynamic integration of the language never ceases to amaze me. #sle09 ※ @
22:39 @JBezivin: #MODELS09 Educational symposium : teaching UML less exciting than #SLE09 presentations ※ @
22:39 @djspiewak: Demo: creating a Roman Numerals language extension for Smalltalk. #sle09 ※ @
22:34 @djspiewak: We're learning a little bit about Swiss culture and geo-culture. Different regions, different languages; all under the same law. #sle09 ※ @
22:33 @djspiewak: Lukas Renggli to talk about language boxes for managing language change. #sle09 ※ @
22:09 @djspiewak: Modular Language Engineering. Reduce complexity for language implementations, adaptation, integration, etc. #sle09 ※ @
22:04 @djspiewak: It's really too bad, but I'm going to have to leave early (14:55), so I'm going to miss the end (including Haskell scripting). #sle09 ※ @
22:03 @djspiewak: Lunch is done, we're back for the start of the modularity session. #sle09 ※ @
21:49 @rusinsky: #sle09 Too bad I am moving, I must attend next year ※ @
20:25 @IanSkerrett: RT @djspiewak: Another example of Eclipse being used in modeling research. It really is ubiquitous. #sle09 << nice to hear ※ @
20:21 @renggli: The first demo at SLE. I like presentations with running demos. #sle09 ※ @
20:19 @djspiewak: Another example of Eclipse being used in modeling research. It really is ubiquitous. #sle09 ※ @
20:09 @djspiewak: Elina Kalnina is now talking about Graphical Template Languages for Transformation Synthesis. #sle09 ※ @
20:08 @djspiewak: So, is PIL's ORM completely stand-alone, or does it still wrap platform-specific ORMs? #sle09 ※ @
20:01 @djspiewak: PIL also has its own ORM, since wrapping doesn't work all the time (severe mismatch with ActiveRecord). #sle09 ※ @
20:00 @djspiewak: PIL also defines wrappers for language-specific frameworks (servlets, ActiveRecord, etc). #sle09 ※ @
19:58 @richpaige: Prepping a Muppet-filled talk for FOSD #SLE09 ※ @
19:55 @djspiewak: PIL has a Java-like syntax. Odd that it would be so high-level. #sle09 ※ @
19:53 @djspiewak: Traditional ILs still work on the machine level (registers, etc). This isn't really acceptable for DSL builders. #sle09 ※ @
19:53 @djspiewak: Why not use an intermediate language and translate from there? #sle09 twitpic.com ※ @
19:51 @djspiewak: @zef claims JRuby isn't completely compatible with other versions. I'm guessing @headius would take issue with that. #sle09 ※ @
19:49 @djspiewak: This turns out to be a problem. For example, the Java language conversion assistant of .NET infamy. #sle09 ※ @
19:49 @djspiewak: Instead of translating from DSL into each platform, why not translate into one platform and from there to the rest? #sle09 ※ @
19:47 @djspiewak: The features you want in the developer platform are very different from the features you want in a language for code generation. #sle09 ※ @
19:47 @notquiteabba: #sle09 is very intense; I can't even keep up with tweeting. Thanks to @zef and @richpaige and @jbezivin for doing a better job. ※ @
19:46 @djspiewak: @zef I missed the link for TweetView. When you get a chance, could you repost here? #sle09 ※ @
- 19:56 @Felienne: @djspiewak Here it is: tweetview.net #sle09 But the tweets are mostly yours :) ※ @
- 20:12 @zef: @djspiewak tweetview.net ※ @
19:45 @djspiewak: The most obvious way to support multiple platforms is to just duplicate the transformation layer. #sle09 ※ @
19:44 @djspiewak: This talk focuses only on the backend for DSLs. We want to extend this architecture for more general platforms. #sle09 ※ @
19:44 @djspiewak: Typical external DSL architecture. #sle09 twitpic.com ※ @
19:42 @djspiewak: ANTLR has many backends, but all of those backends have to be individually maintained. #sle09 ※ @
19:41 @djspiewak: Plug for (broken link), which apparently uses WebDSL. #sle09 ※ @
19:38 @djspiewak: Compilers usually generate code for a particular platform (Java, .NET, PHP, etc). #sle09 ※ @
19:37 @djspiewak: The concept deals with "compiled" DSLs, or external DSLs. #sle09 ※ @
19:36 @djspiewak: @zef is up to talk about a platform independent language for retargetable DSLs. #sle09 ※ @
19:32 @djspiewak: If there are a lot of errors in a big region, fine-grained repair might hit performance issues. #sle09 ※ @
19:31 @djspiewak: Two errors in close proximity is handled by expanding the region to include both regions (fine-grained repair). #sle09 ※ @
19:29 @djspiewak: Permissive grammars project: strategoxt.org #sle09 ※ @
19:29 @djspiewak: Region selection and bridge parsing are independent of parsing algorithm. The fine-grained repair is SGLR specific. #sle09 ※ @
19:27 @djspiewak: Recovery evaluation. Fine-grained + bridge parsing does best. #sle09 twitpic.com ※ @
19:24 @djspiewak: Solution: 1) select erroneous region; 2) try bridge parsing; 3) try fine grained repair; 4) skip region. #sle09 ※ @
19:22 @djspiewak: The goal is to recover at the smallest region which contains the error. If that doesn't work, move to the parent region. #sle09 ※ @
19:21 @djspiewak: Region selection. #sle09 twitpic.com ※ @
19:20 @djspiewak: First select candidate region, check if candidate contains error (then skip), otherwise repeat until error region is found. #sle09 ※ @
19:19 @djspiewak: Two assumptions: we assume indentation conventions and there are some assumptions on the structure of the language. #sle09 ※ @
19:18 @djspiewak: Bridge parsing detects missing braces. #sle09 twitpic.com ※ @
19:17 @djspiewak: Inspiration was bridge parsing. Bridge parsing uses indentation to recover from scope errors. #sle09 ※ @
19:17 @djspiewak: Impressive recovery on the missing paren case. #sle09 ※ @
19:16 @djspiewak: Solution in SLE paper restricts area of text that is inspected. #sle09 ※ @
19:16 @djspiewak: Backtracking recovery: too clever for its own good. #sle09 twitpic.com ※ @
19:12 @djspiewak: Backtracking is alright when the error can be recovered very near to its occurrence. #sle09 ※ @
19:11 @djspiewak: Parallel parsing and backtracking are options, but parallel is bad on large regions, and backtracking has an awful worst-case. #sle09 ※ @
19:10 @djspiewak: The trick is to find the best alternative. #sle09 ※ @
19:10 @djspiewak: It turns out that recover productions introduce ambiguities which recreate a search space of alternate parses. #sle09 ※ @
19:09 @djspiewak: Extend the grammar with recover productions. Insert special chars, delete special chars and words. Derive recover rules from grammar. #sle09 ※ @
19:08 @djspiewak: SGLR error recovery in Eclipse. #sle09 twitpic.com ※ @
19:07 @djspiewak: Main use of this new error recovery technique: SGLR (which previously lacked error recovery). #sle09 ※ @
19:06 @djspiewak: Question from the audience: why don't you use indentation? That's exactly what the paper is about. #sle09 ※ @
19:06 @djspiewak: Delete/insert works better, but it often misses the most natural place to correct the error. #sle09 ※ @
19:05 @djspiewak: Traditional approach to error recovery is panic mode. Once we hit a problem, just skip tokens until we start working again. #sle09 ※ @
19:04 @djspiewak: Error recovery fail. #sle09 twitpic.com ※ @
19:02 @djspiewak: Main usage scenario for graceful error recovery is IDEs. For example, Eclipse can't crash the editor on malformed exprs. #sle09 ※ @
19:02 @djspiewak: Maartje is up to talk about Error Recovery. This is a very nice and imaginative concept; the paper is well-worth the read. #sle09 ※ @
18:58 @djspiewak: Interesting: composed parse tables aren't that much larger than the tables for composed grammars. #sle09 ※ @
18:57 @djspiewak: Component-LR can't gracefully handle back-references to the host grammar. #sle09 ※ @
18:55 @djspiewak: Are Packrat parsers closed under composition? Does anyone know? #sle09 ※ @
18:53 @djspiewak: PEGs are closed under composition. This intuition is born out by parser combinators which are composable through virtual dispatch. #sle09 ※ @
18:51 @djspiewak: Composed parse tables does impose some performance overhead (~2x) beyond composed grammars, but not too bad. #sle09 ※ @
18:50 @djspiewak: Solution: Make a different scanner only for marking terminals and run it in parallel with the pre-built scanners (polynomial time). #sle09 ※ @
18:50 @djspiewak: Problem: Scanners for marking terminals (µ) must be built at composition time. #sle09 ※ @
18:49 @djspiewak: Parse table merging. #sle09 twitpic.com ※ @
18:45 @djspiewak: The test ensures that the parse tables for composed extensions are partitioned into distinct sections; one for host and each ext. #sle09 ※ @
18:43 @djspiewak: In order to do this composition, any production with a host non-term on the LHS must have FIRST={ µ }, where µ is not used elsewhere. #sle09 ※ @
18:42 @djspiewak: Formal expression of isComposable. #sle09 twitpic.com ※ @
18:41 @djspiewak: A theoretical test for extensions which guarantees that each extension will compose correctly. #sle09 ※ @
18:40 @djspiewak: This does require context-aware scanning. I should think that scanner-less would be an easier way to go. #sle09 ※ @
18:39 @djspiewak: Idea: distribute pre-compiled parse tables which can then be composed. #sle09 ※ @
18:39 @djspiewak: Recompilation is theoretically exponential-time, which is too time-consuming to perform at parse-time. #sle09 ※ @
18:38 @djspiewak: Extensible languages as modular components, only assembled by the end-user. Extensions only distribute grammar fragments. #sle09 ※ @
18:35 @djspiewak: August at #sle09 twitpic.com ※ @
18:34 @djspiewak: August is up to talk about Verifiable Parse Table Composition. Nice paper, btw! #sle09 ※ @
18:24 @zef: Upcoming session is the session of my talk. Don't miss it! ;-) #sle09 ※ @
- 18:33 @djspiewak: @zef I'm looking forward to it! #sle09 ※ @
18:12 @djspiewak: #sle09 twitpic.com ※ @
18:09 @djspiewak: Questions on the second-day keynote. #sle09 twitpic.com ※ @
18:05 @djspiewak: There are models you extract from systems, and models which allow you to *build* systems. #sle09 ※ @
18:01 @djspiewak: #sle09 second-day keynote is finished. Time for questions. ※ @
18:00 @djspiewak: #sle09 is building this area of tolerance and competition. ※ @
17:59 @djspiewak: The "Towers of Models" grand challenge - Robin Milner. #sle09 twitpic.com ※ @
17:59 @richpaige: Reminder of Robin Milner's notion of Towers of Models #SLE09 ※ @
17:56 @djspiewak: RT @martiell: [RT: A model of a model is not a metamodel. #sle09] And I'll be disappointed if it's not a model of a modern major general... ※ @
17:55 @martiell: [RT @djspiewak: A model of a model is not a metamodel. #sle09] And I'll be disappointed if it's not a model of a modern major general... ※ @
17:53 @richpaige: CESAR project for tool interoperability via metamodels #SLE09 ※ @
17:53 @djspiewak: We can also build transformations from other data sources, like Excel->Bugzilla, or Excel->Mantis. #sle09 ※ @
17:52 @djspiewak: They extract the metamodel from Bugzilla and Mantis and are able to build a transformation for data from Bugzilla to Mantis. #sle09 ※ @
17:51 @richpaige: JeanB: the increasing importance of data models #SLE09 ※ @
17:51 @djspiewak: At some point, models of the data will be much more important than models of the code. #sle09 ※ @
17:50 @djspiewak: We are trying to automate; to try to understand the methodology. #sle09 ※ @
17:49 @djspiewak: MoDisco is a new Eclipse component. The name is short for "Model Discovery". #sle09 ※ @
17:47 @djspiewak: "Where is the model coming from?" Naive answer: Rational Rose. #sle09 ※ @
17:47 @richpaige: Need to read Brian Cantwell-Smith's work. #SLE09 ※ @
17:43 @djspiewak: Model Driven Engineering inherits from grammar engineering and ontology engineering. #sle09 ※ @
17:42 @djspiewak: Correction: "model of a model". #sle09 ※ @
17:41 @djspiewak: A model of a mode is not a metamodel. #sle09 twitpic.com ※ @
17:39 @richpaige: Jean Bezivin: a model of a model is not a metamodel. Punchline coming up (megamodels, anyone?) #SLE09 ※ @
17:38 @djspiewak: In grammarware, a program is a tree, but it's very difficult to unify the definitions. In MDE, it's already been done. #sle09 ※ @
17:38 @tvdstorm: MDE vs language engineering: model vs AST, graph vs tree, class vs ADT, metamodel vs grammar, diagram vs text. #sle09 constructing bridges. ※ @
17:38 @djspiewak: An abstract model is a graph, and it precisely follows the formal definition. #sle09 ※ @
17:36 @djspiewak: Java just isn't declarative. I'm sure you could represent a Java grammar in Java (e.g. as a parser), but that seems like cheating. #sle09 ※ @
17:35 @djspiewak: Unification of the Java program with the Java grammar (a la XSD schemata). I'm not sure how possible that is. #sle09 ※ @
17:31 @richpaige: Another reminder to read Dragan Gasevic's book, which is on my shelf :-( #SLE09 ※ @
17:26 @djspiewak: The point is that we can use decorated models to represent the system, but you won't find those artifacts actually in the system. #sle09 ※ @
- 17:32 @andreyplatov: @djspiewak why not? what about interpreted models (artifacts)? ※ @
  - 17:39 @djspiewak: @andreyplatov I'm not really sure, to be honest. I think he's trying to be extremely rigorous with his definitions. #sle09 ※ @
17:25 @richpaige: Do not eat the plastic plates - good advice from Jean B. #SLE09 ※ @
17:25 @djspiewak: "You can't eat models." Good advice. #sle09 ※ @
17:24 @richpaige: MDE for interoperability - this is exactly the direction that is being taken in system integration projects with the SSEI #SLE09 ※ @
17:23 @richpaige: Jean Bezivin talking about the Evolution of MDE #SLE09 ※ @
17:22 @djspiewak: There are many types of modeling (mathematical, software, etc). In all of them, you have a system and the model represents that sys. #sle09 ※ @
17:20 @djspiewak: It takes about 15 years to mature a technology (18 ± 3). If that is true, then MDE is well on its way with 5-10 years to see the end. #sle09 ※ @
17:17 @djspiewak: UML has helped us to take a very important step between '95 and '96. #sle09 ※ @
17:15 @djspiewak: Representing the "cat on the mat" operation in sNets #sle09 twitpic.com ※ @
17:10 @djspiewak: Started with Smalltalk, but wanted more operations. The idea was to build a framework (sNets) in which we could def operations. #sle09 ※ @
17:09 @djspiewak: People are using (in the real world) higher-order transformation in ATL. #sle09 ※ @
17:06 @djspiewak: #sle09 keynote speaker twitpic.com ※ @
17:02 @djspiewak: We have not seen the full application development of MDE. MDE may be the important item for CompSci in this century. #sle09 ※ @
- 17:39 @deanwampler: @djspiewak Gut feel: textual DSLs will be the only form of MDE that survives in the real world. ※ @
  - 17:42 @djspiewak: @deanwampler +1 But I suppose we'll have to see. I've never been keen on modeling in general, but other people are. #sle09 ※ @
17:02 @djspiewak: If Model Driven Enginering is the solution, then what is the problem? #sle09 ※ @
16:58 @djspiewak: We're getting started with the second-day keynote. #sle09 ※ @
14:49 @DamienCassou: Search for people interested in hiking in Denver mountains on Wednesday #sle09 #gpce09 #models09 ※ @
3:42 @grammarware: Thanks to @djspiewak for covering #sle09 in such detail, it feels like I’m reading my own twitflood ;) Keep it up & as interesting as now. ※ @
2:11 @zef: RT @djspiewak: @zef won the enviable SLE T-Shirt. I'll have to plan my heist very carefully... #sle09 ※ @
2:08 @djspiewak: @zef won the enviable SLE T-Shirt. I'll have to plan my heist very carefully... #sle09 ※ @
2:03 @zef: "I know I'm extremely smart, that's not the issue." -- @notquiteabba #sle09 ※ @
2:02 @djspiewak: Main message of this talk: "Don't call yourself a stupid grammarware person". #sle09 ※ @
1:55 @djspiewak: It's amazing how universal Eclipse is among modeling researchers. It's also amazing that everyone sticks with the default purple. #sle09 ※ @
1:42 @djspiewak: Current talk is about Ontological Metamodeling with Explicit Instantiation. #sle09 ※ @
1:40 @djspiewak: Very enjoyable talk on WebDSL validations. Looks like Wicket form validations with a really pretty syntax. #sle09 ※ @
1:30 @djspiewak: WebDSL looks very interesting. It also looks like it could be an internal DSL in Scala without any syntactic concessions. #sle09 ※ @
- 1:36 @psnively: @djspiewak Curious how it compares with impredicative.com ※ @
  - 1:41 @djspiewak: @psnively Seems to be a bit higher-level. webdsl.org #sle09 ※ @
1:23 @djspiewak: Data Validation in a DSL for Web applications. A talk by Danny Groenewegen. #sle09 ※ @
1:23 @tvdstorm: RT Felienne Great talk by @djspiewak on language integrated SQL queries in Scala #SLE09 ※ @
1:17 @Felienne: Great talk by @djspiewak on language integrated SQL queries in Scala #SLE09 ※ @
- 1:22 @djspiewak: @Felienne Thanks! I wish I had a bit more time; I would have explained the syntactic combinators thing a little better. #sle09 ※ @
0:48 @djspiewak: Problem: how to allow rapid DSL change and how to allow these adaptations to take place dynamically. #sle09 ※ @
0:45 @djspiewak: Paul Laird is up to talk about Dynamic Evolution of DSLs. #sle09 ※ @
0:44 @djspiewak: The "Models as ADTs" talk ran a bit long. I wonder if we're going to get the schedule back on track. #sle09 ※ @
0:39 @djspiewak: "This approach provides a practical way to formally define the semantics of complex model transformation languages" #sle09 ※ @
0:38 @djspiewak: They've implemented some Eclipse-based tooling. Will be done in future work. #sle09 ※ @
0:33 @djspiewak: Metamodels are java packages; metaclasses are classes; metaattributes are annotated fields. #sle09 ※ @
0:32 @djspiewak: They have implemented metamodel ADTs in Java and defined an embedded language strongly based on ATL. #sle09 ※ @
0:27 @djspiewak: Simplified RDB metamodel. #sle09 twitpic.com ※ @
0:24 @djspiewak: Metamodels as ADTs. Models transformations turn into graph manipulations. #sle09 ※ @
0:22 @djspiewak: They want to define a formal approach to support definition of models and metamodels. #sle09 ※ @
0:21 @djspiewak: Jerónimo Irazábal is up to talk about Model Transformation Languages. #sle09 ※ @
0:21 @tvdstorm: Anya Bagge presenting the latest cool stuff in Magnolia: strategic compiler plugging for language extension. #sle09 ※ @
0:19 @djspiewak: Ah! They might solve the `where`-clause issue by restricting their contents to be strongly normalizing. #sle09 ※ @
- 0:22 @ekabanov: @djspiewak Even if they wouldn't they could still have a formal semantics. E.g. Agda has a formal semantics. ※ @
  - 0:27 @djspiewak: @ekabanov I'll have to look at Agda. Never heard of it before. #sle09 ※ @
0:17 @djspiewak: They plan to define formal semantics for Magnolia transformations. Given the `where`-clauses, I'm skeptical. #sle09 ※ @
0:13 @djspiewak: `where`-clauses let you evaluate code at compile-time in Magnolia. How does that not make compilation undecidable? #sle09 ※ @
0:10 @djspiewak: Anya Bagge is talking about Magnolia and compilation by transformation. #sle09 ※ @
0:09 @djspiewak: @zef kindly gave me the username/password for the wifi here at the Hyatt, so I'm back to tweeting nonstop! #sle09 ※ @

5 Oct, 22:35 @tvdstorm: Another walk down memory lane: mapping feature models to implementation models. Steffen Zschaler on VML* for variability management. #sle09. ※ @
22:16 @tvdstorm: Correction on before-last-tweet: it's Mathieu *Acher*. #sle09 ※ @
22:10 @tvdstorm: Listening to "Composing Feature Models" talk by Mathieu Archer. Brings back memories... #sle09 ※ @
21:35 @guwac: Presented our #sle09 paper on the evolution of modelling languages in #gmf together with Markus. ※ @
20:04 @zef: Tijs van der Strom talks about migrating the use of an XML API by wrapping and emulating the old API. #sle09 ※ @
20:00 @EelcoVisser: "Integration of Data Validation and User Interface Concerns in #WebDSL" this afternoon at #sle09 blog.eelcovisser.net ※ @
19:31 @EelcoVisser: "Quine in Stratego" a Stratego program that generates itself blog.eelcovisser.net (reminiscing about OOPSLA'04 at #gpce09 #sle09) ※ @
19:04 @djspiewak: Having a really hard time with AT&T's network. #sle09 ※ @
19:04 @djspiewak: The organizers are paid in T-Shirts. #sle09 ※ @
18:54 @djspiewak: Reception is at 19:00, *not* 20:00. #sle09 ※ @
- 22:47 @EelcoVisser: @djspiewak is the reception of #sle09 shared with the #gpce09 reception? ※ @
  - 6 Oct, 0:08 @djspiewak: @EelcoVisser Yes it is. Do you have any idea where it is being held? ※ @
    - 0:21 @EelcoVisser: @djspiewak I think the #gpce09 #sle09 reception is just outside the meeting rooms; maybe @SLE2009 can tell us ※ @
18:52 @djspiewak: At the opening for #sle09. They're talking about the PC et al. ※ @
18:48 @zef: Dragan is introducing the #sle09 conference. twitpic.com ※ @
18:45 @EelcoVisser: Not clear that the gap between meta and object levels that confuses users is avoidable in DSL engineering, MDE though #GPCE09 #SLE09 ※ @
18:43 @EelcoVisser: I'm reading Cooper's "The Inmates are running the asylum"; useful lessons for software usability relevant for Cordy's talk #GPCE09 #SLE09 ※ @
17:59 @fhe: "It's in our interest to make them dependend on our dog food". Words of honesty at #gpce09 #sle09 keynote. ※ @
17:54 @zef: Eric van Wyk: we have to eat our own dogfood so you don't have to. #sle09 #gpce09 ※ @
17:53 @djspiewak: We should eat our own dogfood so that others don't have to. #sle09 ※ @
17:49 @webdsl: Jim Cordy everybody should try to build languages like me! #gpce09 #sle09 ※ @
17:48 @djspiewak: The agenda: understand the user's point of view and design appropriate families of GTE DSLs. #sle09 ※ @
17:45 @djspiewak: #sle09 keynote speaker. twitpic.com ※ @
17:43 @webdsl: RT @zef: Jim Cordy likes #webdsl, calls it beautiful and perfect. Yay :) #sle09 #gpce09 ※ @
17:42 @djspiewak: More recent example of GTE DSL: RSL. #sle09 ※ @
17:39 @tvdstorm: Jim Cordy example Mu*: a family of languages for instantiating code templates based on a design model in Prolog (from 1992). #sle09 #gpce09 ※ @
17:39 @djspiewak: Examples MU* and HSML. #sle09 ※ @
17:34 @djspiewak: Why don't we sped our time transforming user-level DSLs into our languages *using* our languages. Use GTE to address adoption issues. #sle09 ※ @
17:32 @tvdstorm: Jim Cordy asks for sets of "WebDSL"s (mutatis mutandis) in the domain of generational and tranformational tools. #sle09 #gpce09 ※ @
17:32 @djspiewak: WebDSL is a good example of how we can solve the problem. But we can't just make DSLs for every GTE application. #sle09 ※ @
17:31 @djspiewak: The real problem: we're asking users to tranform their problems into our domain. #sle09 twitpic.com ※ @
17:30 @zef: Jim Cordy likes #webdsl, calls it beautiful and perfect. Yay :) #sle09 #gpce09 ※ @
17:25 @tvdstorm: Cordy at #sle09 #gpce09: #Colm and #Rascal to make transformation/generation tools more familiar and accessible.But aiming for generality... ※ @
17:25 @zef: Jim Cordy: Problem of today's language engineering tools is that they attempt to solve everything, to apply to everything. #sle09 #gpce09 ※ @
17:24 @notquiteabba: Cordy cont'd: in addition to notation and paradigm issues; current tech aren't adopted because they use general purpose trafo languages ※ @
17:24 @djspiewak: Colm and Rascal are easier to use, but they still don't solve the problem. They're still aiming at the whole problem domain. #sle09 ※ @
17:24 @djspiewak: User's view is that transforming and generation is not the problem. The user's want to solve their domain-specific issue. #sle09 ※ @
17:22 @djspiewak: Colm doesn't look like a rewriting language. Syntax is based on Python. #sle09 twitpic.com ※ @
17:19 @djspiewak: Transformative parsers can be non-terminating? That doesn't sound right. #sle09 ※ @
17:18 @notquiteabba: Jim Cordy's keynote at #sle09 and #gpce09 does a meta talk on trafo/generative technologies: adoption issues ※ @
17:18 @djspiewak: Trying to solve adoption issues with practical tutorials. Breaks down because the user still has to decide applicable concepts. #sle09 ※ @
17:17 @tvdstorm: Jim Cordy's keynote #sle09/#gpce09: who's using transformational tools? The makers and their colleagues. Adoption issues of GTSE tools. ※ @
17:14 @djspiewak: Overwhelming TXL code. Just not accessible to average Joe programmer. #sle09 twitpic.com ※ @
17:14 @zef: Jim Cordy keynote #sle09 #gpce09 twitpic.com ※ @
17:11 @zef: Jim Cody: does it take a PhD to use language engineering tooling? #gpce09 #sle09 ※ @
17:10 @djspiewak: Talking about successful transformative DSLs. Most of them seem to be used exclusively by their authors. #sle09 ※ @
17:06 @djspiewak: Cordy is talking about DSLs and generative languages. #sle09 ※ @
16:58 @djspiewak: My #sle09 tweets may be a bit spotty due to really bad network coverage both from the hotel and AT&T. Sorry! ※ @
16:54 @djspiewak: Getting ready for the keynote at #sle09. Absolutely *terrible* wireless coverage in the meeting rooms! ※ @
16:48 @zef: In the room, ready for the #gpce09 and #sle09 keynote! ※ @
16:27 @guwac: Who builds a hair dryer with 30cms of cord? Registering for #sle09 now. ※ @
16:13 @andersonledo: This is a week to follow #models09, #gpce09 and #sle09. Although I cannot be in Denver, I'll follow it by twitter at least. :P ※ @
14:46 @EelcoVisser: Decided to work on another #WebDSL screencast after waking up at 4:30 #SLE09 ※ @
14:30 @zef: Concidering that I woke up at 5am this morning, I must be very excited for #sle09 to start today! What else could it be? ※ @
11:08 @notquiteabba: Thanks for insights at the steering committee dinner of SLE and the after-meetings. I am tired now & hope to recover until #sle09 starts. ※ @
1:33 @inkytonik: Thanks all for the #gpce09, #sle09 and #models09 updates! (Special Denver area tip: plan a trip up to Boulder to see the Flatirons.) ※ @
1:19 @renggli: My Denver excursion of this morning in pictures: gallery.lukas-renggli.ch #denver #sle09 ※ @

4 Oct, 22:38 @zef: Challenge for upcoming speakers: limit your slides to pictures, tiny code fragments and upto 140 characters of text #gpce09 #sle09 #models09 ※ @
21:44 @EelcoVisser: Got 'demo' by @cwende of LanGems language composition framework using roles to model language interface langems.cwende.de #GPCE09 #SLE09 ※ @
19:44 @cwende: Nearly finished slides for language composition talk at #sle09 in denver ※ @
18:00 @renggli: Exploring Denver downtown. Pretty busy place for a sunday morning. #sle09 ※ @
12:07 @zef: It's 4am Denver time and I'm already completely awake. Welcome to the US. #gpce09 #sle09 ※ @
8:05 @notquiteabba: We all arrived at #sle09 / #models09 / #gpce09 and thought it is in Denver; well Denver is more than 1h by public transit. OMG ※ @
7:39 @JBezivin: Also arrived for a week in Denver (#sle09, #gpce09, #models09). Quick and pleasant dinner with @notquiteabba and other nice people. ※ @
5:37 @tvdstorm: Arrived in Denver for #sle09, #gpce09 and #models09. ※ @
4:42 @renggli: Arrived in Denver for #sle09. Met @notquiteabba in Frankfurt, as well as two #models09 attendees in the plane and during baggage pickup. ※ @
3:09 @notquiteabba: In Denver for #sle09; I am staying at Homestead Studio Suites; great concept in the US. ※ @
2:46 @dgasevic: In Denver for SLE 2009. ※ @
- 7:45 @JBezivin: @dgasevic Nice meeting you this evening Dragan ( #sle09, #gpce09, #models09 ) ※ @

3 Oct, 19:28 @SLE2009: Registration will be open from 8am on Monday, Oct 5. The keynote starts at 9am. Please, plan to come at lest 15' earlier to register. ※ @
19:25 @SLE2009: Updated program is available planet-sl.org. Get familiar with the other authors - their photos are there too :-). ※ @
10:38 @Felienne: On my way to Denver for #models09, #sle09 and #gpce09 ※ @
8:54 @dgroenewegen: Flying to Denver today for #sle09, #models09 and #gpce09 conferences. ※ @
5:41 @renggli: Zurich → Frankfurt → Denver → #SLE09 ※ @

2 Oct, 23:48 @dskolovos: packing for Denver #models09 #sle09 ※ @
21:32 @SLE2009: Reception starts at 19:00 (not 20:00 - changed) on Monday. It is shared with GPCE and MODELS. ※ @
21:32 @SLE2009: The Grand Mesa room in the hotel is allocated for SLE 2009 for both days. ※ @
19:27 @softmodeling: I've not found recent pictures of myself online but take a look at this one modeling-languages.com to recognize me at #MoDELS09 ※ @
- 21:26 @EelcoVisser: @softmodeling I'll take some fresh pictures of you and the rest of the gang; packing my camera as we speak #GPCE09 #SLE09 #MoDELS09 ※ @
17:32 @zef: RT @softmodeling: hope to meet many of you at the #models09 and #sle09 conferences next week! Let's see if I recognize you in "real life" ※ @
17:28 @EelcoVisser: RT @softmodeling: hope to meet many of you at the #models09 #sle09 and #ocl09 conferences next week! Let's see if I recognize you IRL ※ @
17:23 @softmodeling: hope to meet many of you at the #models09 #sle09 and #ocl09 conferences next week! Let's see if I recognize you in "real life" ※ @
17:05 @grammarware: #SLE09 related #FollowFriday: @dgasevic @GorelHedin @JeanMarieFavre @notquiteabba @EelcoVisser @JurgenVinju @PauloBorba @ststaab @inkytonik. ※ @
15:25 @institute4cs: RT @grammarware As usual for any new conference, you can follow #SLE09 at uni-koblenz.de (mine) or tweetview.net ( ... ※ @
15:19 @grammarware: As usual for any new conference, you can follow #SLE09 at uni-koblenz.de (mine) or tweetview.net (@zef's). #i4cs ※ @
- 15:32 @zef: @grammarware #i4cs? ※ @
  - 15:36 @grammarware: @zef it’s our local department’s hashtag, don’t worry about it. Whatever is marked with it, gets retweeted to @institute4cs. ※ @
- 15:36 @zef: @grammarware ah, I see it, it's a hint for the @institute4cs account. ※ @
14:05 @zef: My PIL language now has a very basic website, which, yes, I know, is still very incomplete: strategoxt.org #sle09 ※ @
13:58 @notquiteabba: RT @zef: To all SLE twitterers, a twitter search showed that #sle is too general and can also refer to a disease, please use #sle09. ※ @
13:39 @zef: To all SLE twitterers, a twitter search showed that #sle is too general and can also refer to a disease, please use #sle09. ※ @
- 13:46 @Felienne: @zef and how about #models? No good either, I suppose? :) ※ @
  - 13:57 @zef: @Felienne nope, #models09 please :) And pay attention to the lecture! ※ @
21:44 @zef: Printing some #sle09 papers for on the way. ※ @

1 Oct, 22:53 @notquiteabba: Time to get into #sle mode. planet-sl.org Does the tag work? I hate hotel-hosted confs; need to get out of my way for SLE. ※ @

30 Sep, 14:39 @zef: RT @SLE2009: The detailed program is available! planet-sl.org #sle09 ※ @
14:17 @inkytonik: Unfortunately, I can't make it to #SLE in Denver, so am seeking a tweet feed. Can offer #SAPLING updates on Friday... plrg.science.mq.edu.au ※ @
- 16:08 @djspiewak: :@inkytonik /me frowns. I'll be there. Can't promise I'll tweet everything, but I'll definitely do the interesting stuff. ※ @
  - 1 Oct, 2:22 @inkytonik: @djspiewak Thanks, will look for #SLE09 tag ※ @
- 20:56 @zef: @inkytonik #sle09 feed (on tweetview): tweetview.net see tweetview.net for other events. No RSS or anything yet though. ※ @
13:26 @SLE2009: The detailed program is available! planet-sl.org ※ @

29 Sep, 15:51 @zef: Just bought a new suitcase for my trip to Denver on Saturday for #sle09 #models09 and #gpce09 even has a TSA lock on it. ※ @

24 Sep, 18:05 @acherm: It seems that #SLE program has been released, great ※ @

23 Sep, 8:48 @SLE2009: 12 days left ※ @

22 Sep, 8:46 @SLE2009: Reminder: SLE 2009 will take place in the Hyatt Denver Tech Center. 7800 East Tufts Avenue, ※ @

18 Sep, 11:06 @SLE2009: Keynote abstracts are available on-line planet-sl.org -> Keynotes ※ @

17 Sep, 21:01 @SLE2009: SLE 2009 takes place in the Hyatt Denver Tech Center. 7800 East Tufts Avenue, Denver, Colorado, USA 80237 ※ @

15 Sep, 10:09 @SLE2009: Did you know that additional copies of the LNCS postproceedings ($60) and conference reception tickets ($50) can be purchased separately? ※ @

14 Sep, 16:09 @SLE2009: Early registration ends today at 11:59pm!!! ※ @

10 Sep, 8:32 @SLE2009: Student? Do not forget to email mailing a scanned copy of your student card to the general chair Dragan Gasevic, dgasevic@acm.org. ※ @

9 Sep, 19:43 @SLE2009: Both regular and student registrations include lunches and coffee breaks, conference reception and LNCS post-proceedings. ※ @
21:08 @SLE2009: NB: Due to some technical issues experienced by the host of our registration website, the response times of the website might be higer. ※ @

8 Sep, 12:42 @SLE2009: Deadline for the early registration is approaching! Sept 14! planet-sl.org ※ @
12:05 @institute4cs: RT @grammarware Anyone interested in attending @SLE2009 in Denver? Hurry up, early registration ends next Monday! #i4cs ※ @
12:04 @grammarware: Anyone interested in attending @SLE2009 in Denver? Hurry up, early registration ends next Monday! #i4cs ※ @
8:49 @SLE2009: Registration payment can only be made using a Visa, MasterCard, or American Express. Problems? Please contact Eric Van Wyk, evw@cs.umn.edu ※ @

7 Sep, 15:54 @SLE2009: Even more dates for your calendar: December 7 - submission for the post-proceedings, Feb 2010 - LNCS publication. ※ @
21:26 @SLE2009: Deadline for the pre-proceedings submissions (Sept. 14) is approaching! Consult planet-sl.org -> Important Dates ※ @

4 Sep, 20:32 @SLE2009: SLE news by mail? Subscribe to our mailing list: listes.imag.fr ! ※ @

3 Sep, 8:37 @SLE2009: Lower rates are available at the conference hotel: (broken link) The booking deadline is today ! ※ @

2 Sep, 23:16 @SLE2009: Denver can easily be reached by plane thanks to Denver International Airport. flydenver.com ※ @
8:30 @SLE2009: SLE 2009 is supported by the Software Engineering Center, University of Minnesota. ※ @

1 Sep, 21:39 @SLE2009: Early registration closes at 11:59pm on September 14, 2009! planet-sl.org ※ @
21:04 @SLE2009: Do you need a visa to visit the US? Check travel.state.gov and planet-sl.org -> Visa support ※ @

31 Aug, 21:46 @SLE2009: SLE will host two keynote talks: by Jim Cordy (Queen's University, Canada) and Jean Bézivin (École des Mines de Nantes, France). ※ @
8:31 @SLE2009: This year SLE'09 co-locates with MODELS'09 and GPCE'09. More details on planet-sl.org ※ @

29 Aug, 18:39 @SLE2009: Brueghel's The Tower of Babel used in the animated gif on planet-sl.org can be admired in Kunsthistorisches Museum, Vienna. ※ @
21:03 @SLE2009: 15 full papers, 6 short papers and 2 tool presentations. Isn't it great? See more on planet-sl.org ※ @

28 Aug, 20:08 @SLE2009: Welcome! ※ @

Generated by Twit2Html on 6 November 2009.