JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-REGISTRY Archives


DC-REGISTRY Archives

DC-REGISTRY Archives


DC-REGISTRY@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-REGISTRY Home

DC-REGISTRY Home

DC-REGISTRY  January 2003

DC-REGISTRY January 2003

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Phase 2 Application Interface

From:

Tod Matola <[log in to unmask]>

Reply-To:

Dublin Core Element Set - registration <[log in to unmask]>

Date:

Mon, 13 Jan 2003 19:46:55 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (117 lines)

On Mon, 2003-01-13 at 08:32, Wagner,Harry wrote:
> Hi Tod,
> I considered using a simple GET/POST approach, but admit I don't see the
> benefit to this.  I am leaning towards implementing our application
> interfaces as Web services, using a toolkit - probably Axis.

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?

I think fetching a document is much more desirable than implement half a
client-server pair (err unless a tighter coupling is what your after).


I didn't see these as competing interfaces, but rather layers (SOAP is
pretty much an envelop right?).  The layers: Query, format/merge and
envelop (e.g., SOAP) perhaps could be designed to complement each other.

Important side effect: Giving URLs to objects in the Registry is a
stand-up idea.

Wrapping the mess in SOAP tags is not going to make specifying a query
any easier or help with merging multiple translation into a single
document (or even a single translation that is not encoded in RDFS). But
once those tasks are solved seems a shame to hide them in the bowels of
the server. Why not expose as much as you can and let the community tell
what is valuable?

Finally, WebService descriptions (UDDI, WSIL, WSDL, DAML-S,...) are
pretty much a moving target and will be hard to find any clear
consensus. So I would spend as little time here as possible.

Cheers Tod...


>
> I am also considering WSIL
> (http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-axis-wsil/java/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-soaprdf/.  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]>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

August 2021
May 2021
August 2017
June 2017
April 2017
March 2017
February 2017
January 2017
December 2016
January 2016
October 2015
September 2015
August 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
November 2014
October 2014
September 2014
July 2014
June 2014
March 2014
January 2014
September 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
September 2012
August 2012
July 2012
June 2012
May 2012
March 2012
February 2012
December 2011
October 2011
September 2011
June 2011
May 2011
April 2011
January 2011
December 2010
November 2010
October 2010
September 2010
June 2010
May 2010
October 2009
July 2009
February 2009
December 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
October 2007
August 2007
June 2007
April 2007
March 2007
February 2007
December 2006
October 2006
September 2006
August 2006
June 2006
April 2006
March 2006
January 2006
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
August 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
February 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
May 2001
April 2001
March 2001
January 2001
November 2000
October 2000
September 2000
August 2000
April 2000
February 2000
December 1999


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager