tag:blogger.com,1999:blog-3944976411672994427.post1630092812180466631..comments2023-09-03T17:53:38.313+07:00Comments on James Clark's Random Thoughts: MGrammarJames Clarkhttp://www.blogger.com/profile/04798042939786677843noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-3944976411672994427.post-40318630643662510292009-01-19T21:50:00.000+07:002009-01-19T21:50:00.000+07:00You might be interested to check my ETL framework....You might be interested to check my ETL framework. I'm still working on web site, but documentation is available as a part of distributive. I have just released the version 0.2.1.<BR/><BR/>Just download http://downloads.sourceforge.net/etl/etl-java-0_2_1-xmlout.zip<BR/>and open etl-java-0_2_1\doc\readme.html inside it. There is a tutorial that could help to get language basics.<BR/><BR/>This language definition mechanism is designed to allow grammar reuse but at the cost of universality. And it also defines passive grammars. It is designed to be orthogonal to metamodel issue. It is easy to establish mapping to existing metamodels. From what have been actually implemented: JavaBeans, EMF, and simple model that uses reflection over classes and fields.consthttps://www.blogger.com/profile/14198516934017644045noreply@blogger.comtag:blogger.com,1999:blog-3944976411672994427.post-18658765883276564052008-12-05T22:12:00.000+07:002008-12-05T22:12:00.000+07:00"I definitely don't want every application to be u..."I definitely don't want every application to be using its own completely custom syntax"<BR/><BR/>You already have to do this to some degree. When you start working for a new company or a new department in your current company you have to wade through it's terminology how all that's cooked into the code. Also when you bring in a 3rd party API. Or even when you create an API for other developers to use.<BR/><BR/>Hopefully the MGrammers would reduce noise and make it easier for us to learn and use the APIs.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3944976411672994427.post-48062904452562164562008-11-25T11:50:00.000+07:002008-11-25T11:50:00.000+07:00MGrammar in some ways is the most immediately usef...MGrammar in some ways is the most immediately useful part of Oslo. There's no reason you need to write a new DSL to use it. In fact, writing MGrammar descriptions of formats you <I>already</I> use can be a very big win.<BR/><BR/>I see using Oslo DSLs more for business rules and other algorithmic/declarative information that doesn't really have a lot of interoperability implications. It's not targeted at data communication per se. (Though it's no slouch at expressing protocols, if you want to use it for that.)Rob Jellinghaushttps://www.blogger.com/profile/18279998727078480190noreply@blogger.comtag:blogger.com,1999:blog-3944976411672994427.post-57201549367884733012008-11-24T17:42:00.000+07:002008-11-24T17:42:00.000+07:00DAG Directed Acyclic GraphDSL Domain Specific ...DAG Directed Acyclic Graph<BR/>DSL Domain Specific Language.Unknownhttps://www.blogger.com/profile/15776391827458687437noreply@blogger.comtag:blogger.com,1999:blog-3944976411672994427.post-59322536063100016722008-11-23T21:39:00.000+07:002008-11-23T21:39:00.000+07:00"I definitely don't want every application to be u..."I definitely don't want every application to be using its own completely custom syntax"<BR/><BR/>I don't think you'll need to worry about having to deal with lots of DSLs. My impression is that Microsoft is targeting in-house business applications and developers. I think there's a lot of scope for using DSLs for describing business rules in a form that is understandable by non-programmers in the business.Ben Lingshttps://www.blogger.com/profile/11581788810445263130noreply@blogger.com