[Soaplite-devel] Re: UDDI attribute support

[Mark F. <mar...@ea...>]

Hi Paul,

I have written a script to call each v2 inquiry API service and display each
element/attribute of each result. Everything works great! I'd like to
contribute that inquiry script as a sample. The existing samples demonstrate
this. But, this one demonstrates each service and every result. More verbose
too. (I started programming in COBOL. Everythign I do looks like COBOL
<ha>). I'll send it to you in a few days.

Regarding the non-uddi namespace attributes (xml:lang in all three versions)
and elements (dsig:Signiture in v3), I discovered something else in v2 which
may affect how you plan to handle this. In v2 the method
"get_businessDetailExt" which returns a "businessEntityExt". This element
contains a "businessEntity" element and this:

  <xsd:any namespace="##other" processContents="strict" minOccurs="0"
maxOccurs="unbounded" />

I don't know if this is something you want to program for and/or how much it
overlaps the issue of non-uddi namespace elements and attribues used in the
UDDI schema.

At a minimum it will have to be documented that the user use a special
syntax to access non-uddi namespace elements and attributes unknown to the
UDDI schema.  ("foo->attr->{'ns:bar'}" for the attribute. How would the
element be accessed?)

You could apply the same rule to non-uddi namespace elements and attributes
used in the UDDI schema. Conversely, whatever you program for in the case of
non-uddi namespace elements and attributes used in the UDDI schema, could it
be made more flexible and capable of being extended in cases that a user is
processing results that are defined by a schema unknown to UDDI?  (That's
why it seems like there's a slight amount of overlap between both issues.)

Thanks,
Mark