regrep message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [regrep] ACTION ITEM
- From: Anne Thomas Manes <atmanes@gmail.com>
- To: "Breininger, Kathryn R" <kathryn.r.breininger@boeing.com>
- Date: Sat, 26 Nov 2005 20:39:50 -0500
Kathryn,
I suspect I missed your deadline, but I promised Farrukh that I would provide comments on the document. Here they are.
Comments on ebXML Registry Profile for Web Services
V1.0 Draft 3
21 September 2005
Title: This profile describes how to map WSDL 1.1 to the registry,
therefore I recommend that you name it "ebXML Registry Profile for WSDL
1.1".
Overall comments: not all WSDL document will contain all parts (service
[with ports], bindings, portTypes [with operations], messages, and
types). (btw -- bindings have operations, and your WSDL data model
doesn't show that.) A WSDL document may just define a portType, or a
binding with an imported binding. The description of the WSDL object
model makes it sound as if the only type of WSDL that can be registered
is a WSDL containing a <service> definition.
Line 267. Missing period after PortType. Missing comma after "the next level".
Line 268. Missing comma after "the next level".
Line 270. "encapsulated one more" should be "encapsulates one or more".
Line 273. "contains one or more" should be "contains zero or more".
Line 281. Should begin with "A WSDL description contains zero or more
binding elements." "The binding element" should be changed to "A
binding element".
Section 2.3. Missing information: A binding element defines a binding
of one or more operational elements, and its input, output, and fault
messages.
Line 282. I suggest you remove "(typically SOAP)". .NET by default generates HTTP bindings for every service.
Line 285. "definition" should be "definitions".
Section 2.5. Missing information: an Operation element also defines fault messages.
Section 2.6. schemas may be imported or defined inline.
Section 2.7. schemas may be imported or defined inline.
Section 4.2.4. In some cases you may not want to specify the access URI
in the registry, and instead service consumers should obtain the access
URI from another source (e.g., the WSDL file at runtime or from a
broker). Therefore you should provide a mechanism to specify an
alternative means to obtain the access URI.
Section 4.3.5. You should have a classification schema for the encoding
scheme. (RPC style binding may use either SOAP encoding or literal)
Also note that SOAP 1.1 and WSDL 1.1 permit different styles and
encodings for different operations within a binding (although WS-I BP
disallows this feature). Also, even if the input and output messages
are RPC/encoded, headers and faults should be document/literal.
Section 6.2. Your required business rules are somewhat arbitrary. The
first business rule will disallow any service developed using .NET,
because all .NET services, by default, have HTTP bindings in addition
to SOAP bindings. The second rule will disallow WS-I compliant services
that implement rpc/literal bindings. It's much more important to make
sure that the WSDL is valid -- not from a schema validation
perspective, but from a semantic perspective. i.e., can a typical WSDL
compiler generate a valid object model from the WSDL?
Line 976. Replace "??" with the appropriate reference.
Line 978. Remove "produces as output" from end of sentence.
Line 986. All occurrances of "URN" should be replaced with "URI".
Line 990. "URN" should be changed to "URI".
Line 991. "URN" should be changed to "URI".
Line 1019. "queries may hidden" should be "queries may be hidden"
Line 1034. Remove period after "well"
Line 1036. "explore" should be "exploring".
Line 1041. "Association" should be "Associations"
Line 1042. "therfor" should be "therefore"
Line 1062. "MUST are" should be "MUST be"
Line 1064. Should this be a header? (8.2?) If so, all subsequent headers in Chapter 8 must be adjusted.
Chapter 10: TBDs...
Line 1971. There's no reference to this implementation in the document, so the reference should be removed.
Best regards,
Anne
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]