OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: WSDL TN comments


Line 336.  Must go out of UDDI ... may not be necessary at runtime.  At 
design time you expect to go out of UDDI to retrieve WSDL and possibly 
other artifacts needed for development of services or consumers.  You may 
not need to retrieve WSDL at runtime if the UDDI binding has the 
accessPoint and you are not doing any dynamic wsdl2java code generation at 
runtime.

Line 346.  "Evolved keys" should have a reference to ...

Line 374.  determined from metadata in categoryBag - needs more 
explanation, at least a statement like " as described below".

Line 420.  First line of footnote is confusing.  You want to be clear that 
targetNamespace SHOULD be used in WSDL files.  Also, TN should state that 
it does not apply to WSDL without targetNamespace, and that automatic 
registration MUST fail if the WSDL file does not contain a 
targetNamespace.  Or perhaps require the keyValue (line 419) to be a 
well-known URI that means "null"; i.e., no targetNamespace.  (need a 
well-known URI like /dev/null; should get w3c to define it so everyone can 
use it, rather than have a Null URI for UDDI, and a different URI with same 
semantics defined by OASIS, IETF, ...).

Recommend a separate TN/BP to describe the XML Namespace tModel (i.e., 
where keyValue is a namespace URI) because it is more generally useful than 
just WSDL mapping.

Line 919.  overviewURL is broken (TN not yet published).

Lines 961, 1013..  tModelKey not yet published to UBR.

(not yet done reading the draft TN, but wanted to get these out in case I 
don't get back to it soon).

Paul




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]