finished personify.why

IEEE P2P 2012/3.personify.why

@@ -1,7 +1,13 @@
-Personify represents an advancement in programming toolset and methodology, fundamentally changing the way software is written. Most programming languages in the world revolve around Procedural, Imperative/Object-Oriented, and Functional approaches. Consequently, most software is written as a set of modules that are invoked in specific sequence to achieve desired functionality. Components of the system are passive entities, that may manifest intelligent behavior by use but may not be distinctly intelligent.
+Personify represents advancement in programming toolset and methodology, evolving the way we write software. We typically develop software as a set of passive modules, to be invoked in specific sequence to achieve desired functionality. Components of the system are receptive entities. They may manifest intelligence in use, but intelligence is not a first class concept in the implementation.
 
 Another paradigm is rapidly emerging. Agent Oriented Software Engineering [][][] seeks to engineer software as collaborative societies of agents, capable of autonomous action and adaptation. Agents form a super-structure of functionality and intelligence that they use to model beliefs, capabilities, and obligations[]. Their interactions are typically P2P.
 
-Analysis of leading BitTorrent clients[Vuze][BitTornado][OneSwarm] reveals that this software engineering paradigm has not made its way into the design of most P2P networking applications. This is not unexpected. The paradigm is very nascent.
+Analysis of leading BitTorrent clients[Vuze][BitTornado][OneSwarm] reveals that this software engineering paradigm has not made its way into the design of most P2P networking applications. This is not unexpected, the paradigm is very nascent.
 
 Such an approach may not seem to have obvious benefits. One could argue that as long as the software manifests the behavior to allow clients to connect to each other and form P2P networks, its implementation is irrelevant. Yet one cannot help but notice how  conceptually elegant the idea of building P2P applications as themselves P2P networks may seem, on a meta-level. It may also have other significant benefits.
+
+References
+[] M. Wooldridge, N. R. Jennings, and D. Kinny, "The gaia methodology for Agent-Oriented analysis and design," in Journal of Autonomous Agents and Multi-Agent Systems, vol. 3, 2000, pp. 285-312. [Online]. Available: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.17.2121
+[] F. Zambonelli and A. Omicini, "Challenges and research directions in Agent-Oriented software engineering," Autonomous Agents and Multi-Agent Systems, vol. 9, no. 3, pp. 253-283, Nov. 2004. [Online]. Available: http://dx.doi.org/10.1023/B:AGNT.0000038028.66672.1e
+[] J. Lind, "Patterns in agent-oriented software engineering," in Proceedings of the 3rd international conference on Agent-oriented software engineering III, ser. AOSE'02.    Berlin, Heidelberg: Springer-Verlag, 2003, pp. 47-58. [Online]. Available: http://portal.acm.org/citation.cfm?id=1754732
+[] T. T. Do, M. Kolp, S. Faulkner, and A. Pirotte, "Introspecting Agent-Oriented design patterns," in In S. K. Chang (Eds.), Advances in Software Engineering and Knowledge Engineering, 2004. [Online]. Available: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.104.7529