I believe there is some agreement about using scenarios so I've started a new thread as the old was getting a little long
I got round to taking a look at the scenarios page on the wiki. Hope I'm looking at the right place ( http://wiki.apache.org/ws/Tuscany/TuscanyJava/Scenarios#preview). This may be a bit controversial but I'd like to have a few descriptions, scenarios, samples (call them what you will) that take more of a business problem view on the value of SCA. From there we can show the path to the individual technical use cases mentioned. For example, we may expect the technical reader to understand why JSON or Celtix are useful but we want the reader (either inside or outside the project) to understand why there is value in SCA in making these pluggable bindings. I.e. what role is SCA playing? Any how I've done some very brief sketches. I'm completely happy if these live on a separate page so they don't mess up the technical scenarios. I'm also happy to put some effort in to expand these thoughts if the team aren't dead set against them. Help and other thoughts most welcome of course.
