Re: Clarifications list for SOAP specification

Cool.  I had intended to do that,  thanks.  Given David's suggesiton on 
the call that this all be merged with the issues list, I'm not sure how 
much maintenance will be done on the XSL, but every little bit helps. What 
I sent last night was the result of a few minutes hacking, just to see if 
the whole structure would work as a start.   Thanks again.

------------------------------------------------------------------------
Noah Mendelsohn                                    Voice: 1-617-693-4036
Lotus Development Corp.                            Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------------







christopher ferris <chris.ferris@east.sun.com>
Sent by: Chris.Ferris@Sun.COM
05/30/01 05:16 PM

 
        To:     Noah_Mendelsohn@lotus.com
        cc:     xml-dist-app@w3.org
        Subject:        Re: Clarifications list for SOAP specification


Noah/DavidF,

A suggestion for handling clarifications might be
to modify the stylesheet such that it added anchors in
the HTML document generated for each proposed clarification
such that they could be individually addressed via an href (from the
proposal link?) from the issues list for each of the
issues that the clarification is intended to resolve.

Conversely, the clarifications list should reference
back to the issue(s) that it is intended to resolve.

I've attached a modified xsl that adds the anchor tags
to each clarification for giggles. It might also be
worthwhile to add a TOC to the generated HTML.

Cheers,

Chris

Noah_Mendelsohn@lotus.com wrote:
>
> Although I confess to being a little vague on the details, I believe 
that
> Henrik and I (and perhaps someone else) were assigned some sort of 
action
> item to begin the gathering of areas in the SOAP version 1.1 
specification
> that appear to require clarification.  In fact, Henrik and I have not 
yet
> managed to coordinate this effort, but with a call coming up tomorrow, I
> thought I would post the following to the whole list. The attached are
> primarily ambiguities that were identified in my note [1] and related
> discussions that followed.  As I say, nobody has reviewed these and this 
is
> at best a partial list.  So, this is just oone attempt to get the
> discussion started.
>
> In keeping with the way that other work groups have tracked things of 
this
> sort, I have invented a simple XML vocabulary and started tracking these 
in
> the form of an XML document.  I have also hacked up a simple style sheet
> that produces HTML from the XML.  Copies of all three are attached. Most
> casual readers will want to look only at the HTML.  Editing should, of
> course, be done on the XML.  All this is pretty quick and dirty, but I
> think it is OK as a start and easily fixed if not a useful base.
>
> Henrik: if you have made any progress, we will have to figure out how to
> merge the results.  In any case, what is attached is just a start.
>
> [1] http://lists.w3.org/Archives/Public/xml-dist-app/2001May/0310.html
>
> (See attached file: clarification.xsl)(See attached file:
> clarification.xml)(See attached file: clarification.html)
>
> ------------------------------------------------------------------------
> Noah Mendelsohn                                    Voice: 1-617-693-4036
> Lotus Development Corp.                            Fax: 1-617-693-8676
> One Rogers Street
> Cambridge, MA 02142
> ------------------------------------------------------------------------
>
> 
----------------------------------------------------------------------------------------------------
>                         Name: clarification.xsl
>    clarification.xsl    Type: unspecified type 
(application/octet-stream)
>                     Encoding: base64
>
>                         Name: clarification.xml
>    clarification.xml    Type: unspecified type 
(application/octet-stream)
>                     Encoding: base64
>
>                          Name: clarification.html
>    clarification.html    Type: Hypertext Markup Language (text/html)
>                      Encoding: base64
]>

Received on Wednesday, 30 May 2001 17:51:01 UTC