db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
@InProceedings{Welch12c,
  title =        "occam {O}bviously",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  author=        "Welch, Peter H.",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  editor=        "Welch, Peter H. and Barnes,  Frederick R. M. and Chalmers,  Kevin and Pedersen,  Jan Bækgaard and Sampson,  Adam T.",
db_connect: Could not connect to paper db at "wotug@dragon.kent.ac.uk"<br>
  pages =        "213--214",
  booktitle=     "{C}ommunicating {P}rocess {A}rchitectures 2012",
  isbn=          "978-0-9565409-5-9",
  year=          "2012",
  month=         "aug",
  abstract=      "This talk explains and tries to justify a range of questions
     for which
its title is the answer. It reviews the history of
     occam: its underlying
philosophy (Occam's Razor), its
     semantic foundation on Hoare's CSP, its
principles of
     process oriented design and its development over
     almost
three decades into occam-pi (which blends in the
     concurrency dynamics of
Milner's pi-calculus). Also
     presented will be its urgent need for
rationalisation --
     occam-pi is an experiment that has demonstrated
significant
     results, but now needs time to be spent on careful
     review
and implementing the conclusions of that review.
     Finally, the future is
considered. In particular, how do we
     avoid the following question being
final: which language had
     the most theoretically sound semantics, the
most efficiently
     engineered implementation, the simplest and most
pragmatic
     concurrency model for building complex systems ... and
     was
mostly forgotten (even as its ideas are slowly and
     expensively and
painfully being reinvented piece-by-piece,
     as they must be)?"
}