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:

"Wagner,Harry" <[log in to unmask]>

Reply-To:

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

Date:

Mon, 13 Jan 2003 09:58:29 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (53 lines)

Hi Pete,
> I'm interested in a SOAP-based approach, but I think I agree with Tod
> that having a simple HTTP GET/POST interface which returns an RDF/XML
> document would be nice.

I guess I don't see the advantage of this.  Why would we want to create our
own interface, query syntax, etc. when everyone else seems to be
implementing Web services?

> Is it not putting a (slightly) heavier burden on user applications to
> insist that they use SOAP? Or is the difference really
> minimal? If it is
> minimal, then that seems OK.

No.  Not if we implement the Web services in a protocol-neutral manner.
Publishing the WSDL abstracts the SOAP implementation (the WSIL document
would include a pointer to the WSDL).  The clients need not be aware the
service is implemented using SOAP.

> On the issue of transmitting RDF/XML in SOAP messages... I
> must admit it
> never occurred to me there was a problem, but I looked briefly at
>
> http://www-106.ibm.com/developerworks/webservices/library/ws-soaprdf/
>
> I think (but I'm not sure?) that all the resources described
> in the DCMI
> schemas (or at least the resources for which we'd expose descriptions
> through this interface) have URIs assigned to them and so don't use
> rdf:ID, so wouldn't that fit into the simple case illustrated
> by listing
> 6?

The provenance information for the translation relies heavily on rdf:ID.  If
we do not offer the provenance info as a service then we avoid this problem,
but are still faced with the encoding problem (see below).

> In, the SOAP primer at
>
> http://www.w3.org/TR/2002/CR-soap12-part0-20021219/
>
> section 5.2 shows RDF/XML encoded in SOAP using an RDF-specific
> env:encodingStyle. Will something like that work for the DC
> descriptions? Or are there subtleties I'm not seeing? Quite probably!

I need to play around with this a bit, but I believe this will look, to the
client, like one big structure.  I'm not sure that is particularly useful.
I think it would be more useful to deliver an XML document that conforms to
a published schema.  Anyone else have any thought on this?

Regards,
Harry

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