Re: Edits to part 2

Hey, Glen,

On Thu, 29 Jul 2004 18:10:05 -0400
Glen Daniels <gdaniels@sonicsoftware.com> wrote:
> * If the HTTP serialization thing is going to be a separate thing and
> not built into the binding, it should be a feature (not a module, since
> modules are specifically about SOAP) with its own URI.  Hence we should
> add the following under the title of section 3.3:

But it isn't a feature, and it isn't a module.  Hugo labelled it as the
HTTP serialization of the AD feature, which I'm comfortable with (much as
I hate the term "serialization" with respect to XML).

Anyway, I *won't* call it a feature.  It isn't a feature.  It binds a
feature, or extends a binding with respect to a feature.  This is the
whole micro-specification issue.

> --
> This feature is identified with the URI
> http://www.w3.org/@@@@/@@/features/AD-HTTP

So I'm doing this as "This feature-binding ...".  But where, if anywhere,
would this URI be used?

DONE with that modification.

> --
> 
> * Sec 3.3.2, end of 2nd para, add "if possible" after "MUST be turned
> into an HTTP header".

DONE.

Although that changes the meaning to, in effect, "MAY be turned into an
HTTP header."  MUST is MUST; not fulfilling a MUST [MUST NOT] be
permitted.  But then, we have a mandataory mandatoriness in part one, so
why not?

> * Sec 3.3.2, first para after the bullet list, add "property " before
> "<constraint>" to make this more clear and avoid confusion like Hugo
> had.

DONE.  I don't like the result, though.  Should it be tagged, instead, so
that it shows up like {property constraint}?

> * Fix the link in that same sentence to point to the property constraint
> description in part 1
> (http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?con
> tent-type=text/html;%20charset=utf-8#Property)

Errm.  I don't know how to do this, or if it can be done.  That link is
generated by a bibref tag, with the attribute ref="WSDL-PART1".  Can I put
#Property at the end of the attribute value?  Or do I need to do something
#else?  Or is it not doable?  Or xspecref instead?

> * Missed a couple of still-unquoted URIs

Argh.  I do not know where they are.  I don't see any.  Maybe you want
quotes around some entity thingies?

> * OK, back to the feature now.  Add the following:
> 
> --
> 3.1.5 The "ad:mustUnderstand" Attribute
> 
> You may choose to decorate your application data element declarations
> with an attribute with the namespace
> "http://www.w3.org/@@@@/@@/wsdl/feature/AD" and the local name
> "mustUnderstand".  This indicates at the abstract level that the
> particular element thus decorated is mandatory, and implementations of
> this feature which support expression of mandatory data (i.e. the
> Application Data SOAP Module[link]) should mark them as mandatory in an
> appropriate way.
> --

DONE.

> * Add the following to the <schema> element in the example:
> 
>    xmlns:ad="http://www.w3.org/@@@@/@@/wsdl/feature/AD"

DONE.

> * Replace section 3.2.2, 2nd paragraph, 2nd sentence, with:
> 
> --
> The elements are serialized according to their schemas, and if the
> "ad:mustUnderstand" attribute exists with the value "true" on any given
> element declaration, that particular SOAP header should be marked as
> "mustUnderstand='true'" or "mustUnderstand='1'" as per the SOAP
> specification.

DONE.

Asir, please double-check our work?

Working Group members, please check, *quickly*, and make comments, so that
I may report to our chair that I believe this part is ready for Last Call.
 Thanks.

Hmm.  It's possible that this checkin won't be visible via cvsweb,
depending on what's happened to the makefiles and how they interact. 
Should I check in wsdl-20.extensions.html, Hugo?  Or you?

Amy!
-- 
Amelia A. Lewis
Senior Architect
TIBCO/Extensibility, Inc.
alewis@tibco.com

Received on Friday, 30 July 2004 10:59:04 UTC