 |
 |
Haary, So since we have a path to a prototype (axis and mind electric glue), does that rule out the simpler GET/POST model of retrieval as a functional requirement? I also think that attempting a layered approach: access via URL to registry object via a URL and then wrapping results as a SOAP message if requested, would get alot more mileage. This could then aid in decisions on where enhancements will go (usage stats). Hoping the door is not closing,,, Cheers Tod... On Tue, 2003-01-14 at 09:11, Wagner,Harry wrote: > Tod, > > > Other than you don't need a SOAP client that understands DC Registry > > soap messages (how many browsers are out there again and how > > hard is it > > fetch a URL in most programing/scripting languages)? Are there ready > > made SOAP clients? > > The whole purpose of publishing the WSDL is to abstract the soap > implementation. The clients do not need to know SOAP. There are a growing > number of wsdl2java tools that will generate client stubs automatically from > the WSDL. The Mind Electrics GLUE package (http://www.themindelectric.com/) > is one example. > > To test this level of abstraction I created a Web service, using Axis. This > service takes a term URI and language (i.e., > http://purl.org/dc/elements/1.1/title, en-US) as input and returns all known > information about the term in the requested language. It took me < 30 > minutes to download, install GLUE, create a client, and successfully use the > service. The client that GLUE created, based on the WSDL, had no knowledge > of SOAP. > > I expect to have this service available on the prototype machine next month. > This would enable others to test this, and would allow us to evaluate the > most appropriate type of object to return to clients (i.e., an XML doc, a > snippet of RDF in the form of a String, etc.). > > Regards, > Harry > > > > > > > > I am also considering WSIL > > > > > (http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-axis-wsil/ja > > va/README.htm) > > > for enabling discovery of the services. WSIL is a > > light-weight alternative > > > to UDDI. Anyone have any experience with WSIL? > > > > > > Best Regards, > > > Harry > > > > > > > -----Original Message----- > > > > From: Tod Matola [mailto:[log in to unmask]] > > > > Sent: Sunday, January 12, 2003 3:45 PM > > > > To: [log in to unmask] > > > > Subject: Re: Phase 2 Application Interface > > > > > > > > > > > > Or use alternative 3: > > > > - GET/POST to server up an RDF/S document (with some mime type). > > > > > > > > (Or in addition to the SOAP route). > > > > > > > > Cheers Tod... > > > > > > > > > > > > On Fri, 2003-01-10 at 08:39, Wagner,Harry wrote: > > > > > Dear WG Members, > > > > > I've had an opportunity to evaluate the Apache Axis project > > > > > (http://xml.apache.org/axis/index.html) recently. Axis is > > > > a Web services > > > > > toolkit built on SOAP, and appears to be a good fit for > > our phase 2 > > > > > application interface. There are numerous advantages to > > > > building on this > > > > > type of toolkit: > > > > > > > > > > - It is flexible, providing support for SOAP 1.1, parts > > of 1.2 (will > > > > > eventually support all of 1.2) and SOAP with attachments > > > > > - It greatly simplifies implementing Web services > > > > > - It would enable us to expose much of the already written > > > > phase 1 code as > > > > > Web services > > > > > - It understands WSDL and simplifies exposing it for > > all implemented > > > > > services (simply append "?wsdl" to the end of the service > > > > name). WSDL, for > > > > > those not familiar with it, is an XML language for > > > > describing Web services. > > > > > It is important because it can be used to generate client > > > > stubs, and is what > > > > > makes the implemented service protocol neutral (by removing > > > > the need for > > > > > clients to understand SOAP). > > > > > > > > > > Some issues that need considered: > > > > > > > > > > - The long-standing issue of how to send RDF using SOAP in > > > > a way that is > > > > > meaningful to the client. This problem is well documented in > > > > > > > > > > http://www-106.ibm.com/developerworks/webservices/library/ws-s > oaprdf/. The > > > options boil down to sending the data as XML, or sending it as raw RDF > (in > > > the form of a big text literal). Sending it as XML seems the more > useful > > > approach since it would be useful in that form to XML applications. RDF > > > applications could still create statements from it, with some effort on > > > their part. > > > - How to document the services. Businesses do this using well-known > UDDI > > > registries. Do we do the same? Do we create our own? > > > > > > Your comments and suggestions are welcome. I would especially like to > > hear > > > from anyone who has experience with Axis. > > > > > > Best Regards, > > > Harry Wagner > > > OCLC / DCMI > > > Dublin, OH 43017 > > > (614) 761-5178 > > > mailto:[log in to unmask] > > -- > > Tod Matola <[log in to unmask]> > -- > Tod Matola <[log in to unmask]> -- Tod Matola <[log in to unmask]>