Agile and Semantic
I recently discovered Jimmy Nilsson’s weblog, I think that it was by searching the web on Eric Evans, Domain Driven Design etc. I am trying to understand how to begin a Delphi implementation of Specification domain pattern (Martin Fowler and Eric Evans).
Anyway, Jimmy Nilsson’s recent blog post, Post-agile struck a chord with me, as he grouped in the same article the things that interested me the most in the last year, year and a half or so: Domain Driven Design, Ruby and Rails, Behavior-Driven Development and Domain-Specific Languages. He also mentioned Intentional software, but I will leave that for the next year 
What I really, really wanted to say is that I feel that the semantic (web or not) approach to the software development or domain design if you like is at least as important as the other items on the list. Maybe it isn’t or doesn’t seem as “agile” as the other ones, but I think that we’ll see more and more the influence the ontologies and their use on the development process itself.
If after a couple of years and projects what you accomplish is a semantic representation of your domain or domain patterns, collaboratively built, shared with customers and on which your working software is built (through BDD and DDD), you do follow the Agile manifesto, so building it starting today should be called agile too, right?
If you don’t believe me, read on to Danny Ayers’ Raw and then search “semantic agile” on Google.
Other links:
