- From: David Fallside <fallside@us.ibm.com>
- Date: Wed, 5 Dec 2001 10:25:57 -0800
- To: Glen Daniels <gdaniels@macromedia.com>
- Cc: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>
Glen, thanks for working on these pieces. Regarding the description of "Conventions for describing state as properties" (1), I think it's content is basically about right but it will need some further editorial work. For example: -- The subsection "Properties, Features ....." starts with the statement "We have had some discussion .... The view advanced here .....": This type of voice is inappropriate for spec text. I suggest a simple fix is to start the paragraph with "A message is an abstraction of the information .... ", i.e. delete the first sentence and the beginning of the second. -- Similarly, the last paragraph "We leave it open (at least for now) ...." should be changed to something like "A property may appear ....". -- The subsection "Properties, Features ....." also needs some more organisation and a crisper style. Breaking up that subsection's first paragraph would make it less dense, and shortening some of the sentences would improve readability (e.g. the paragraph starting "Having abstracted messages ..." consists of a single sentence). I am available over the next few days to help edit. Regards, David ............................................ David C. Fallside, IBM Ext Ph: 530.477.7169 Int Ph: 544.9665 fallside@us.ibm.com Glen Daniels <gdaniels@macrome To: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org> dia.com> cc: Sent by: Subject: TBTF pieces for the specs xml-dist-app-requ est@w3.org 12/04/2001 10:00 AM All: Here are the current versions of the four pieces which the TBTF proposes inserting into the upcoming WD. The Binding Framwork itself may be found at [1]. This will become section 5 (I believe) of Section 1. The other pieces, which all go in Section 2 (Adjuncts), are attached to this message. As a reminder, they are: 1) A description of the property naming/typing conventions, plus the "logical architecture", which we use in the following pieces. 2) A description of Transport MEPs, and a specification for a "Simple-Request-Repsonse" MEP. 3) An HTTP binding per the framework, using the property convention and the Simple-Request-Repsonse MEP. These pieces were mostly taken wholesale from earlier text which the TF had produced. The structure has changed a bit, and some small edits have been done in a few places. A "merged" version of this text to see how it appears in the actual flow of the WD should be available tomorrow. --Glen [1] http://lists.w3.org/Archives/Public/www-archive/2001Dec/att-0008/01-SOAPBind ingFramework-01.html #### Default HTTP Binding.htm has been removed from this note on December 05 2001 by David Fallside #### Framework-Properties.png has been removed from this note on December 05 2001 by David Fallside #### PropertyConventions.html has been removed from this note on December 05 2001 by David Fallside #### Requesting-STD.png has been removed from this note on December 05 2001 by David Fallside #### Responding-STD.png has been removed from this note on December 05 2001 by David Fallside #### SRR-Std.png has been removed from this note on December 05 2001 by David Fallside #### Transport Message Exchange Pattern.htm has been removed from this note on December 05 2001 by David Fallside
Received on Wednesday, 5 December 2001 13:25:26 UTC