Pete / Roland,
Think about this from the client's viewpoint.  You call a remote service and
expect to get something back.  What is that 'something'?  You have to type
it!  Last time I checked rdf is not a valid type in Perl, Java, or any other
programming language I know :).  I'll put this service up on the prototype
machine next month and you can run your own clients against it.  That might
make the issue more clear.  Keep in mind that the goal here is for the
service to deliver up information in a form that is most usable to the
client applications.

Regards,
Harry

> -----Original Message-----
> From: Pete Johnston [mailto:[log in to unmask]]
> Sent: Tuesday, January 14, 2003 10:55 AM
> To: [log in to unmask]
> Subject: Re: Phase 2 Application Interface
>
>
> > The issue here is not whether or not to follow W3C
> > recommendations, but rather, how to type the return value
> > from registry Web services.  In other words, if the services
> > respond with RDF what should that look like to the client
> > code (a String?)?
>
> I admit I'm getting into territory which I'm really not
> familiar with...
>
> ... but isn't this a problem only if you use
> env:encodingStyle="http://www.w3.org/2001/12/soap-encoding" ?
>
> The final part of the article you cite
>
> http://www-106.ibm.com/developerworks/webservices/library/ws-soaprdf/
>
> says
>
> ===
> there is no reason you should have to mutate our SOAP message into RPC
> form in order to use SOAP. If you are not locked in by the
> need for RPC
> integration into other systems, you can take the more natural course,
> the declarative approach of sending the data and leaving the remote
> system free to process it as seen fit. There is no official
> RDF encoding
> for SOAP yet, but this discussion is based on the conventions and
> prescriptions of RDF and SOAP.
> ===
>
> See their Listing 6 example and a similar one in section 5.2 of:
>
> http://www.w3.org/TR/2002/CR-soap12-part0-20021219/
>
> Pete, going back to dancing on the head of a pin over namespaces
>