W3C home > Mailing lists > Public > www-rdf-interest@w3.org > September 2000

Re: SOAP, RDF and Semantic Web screenscraping...

From: Rahul Dave <rahul@reno.cis.upenn.edu>
Date: Thu, 7 Sep 2000 22:12:04 -0400 (EDT)
Message-Id: <200009080212.WAA15023@reno.cis.upenn.edu>
To: martind@netfolder.com
Cc: JTauber@bowstreet.com (James Tauber), Daniel.Brickley@bristol.ac.uk ('Dan Brickley'), www-rdf-interest@w3.org
Can I "me too" on this? I'm working on a perl rdf-soap 
implementation, adding a RDF
interface to Everything(www.everydevel.com), which incidentally has
an object model quite similar to RDF.
Rahul
I got this from you:
> 
> Hi James,
> 
> James said:
> It's called Redfoot
> and is basically an RDF store/viewer/editor framework in Python that will
> soon include support for peer-to-peer communication between different stores
> using SOAP.
> 
> Didier replies:
> Will you publish the peer to peer exchange API before the code? I am also
> working on a store, having an RDF reply to a SOAP request. Maybe we can
> synch our API so that the stores can inter-operate and also provide a good
> demonstration of peer to peer data exchange. We thought of:
> 
> find (string topic) returns the RDF element for this resource. For example,
> the following call:
> 
> POST /device-profile HTTP/1.1
> Host: www.priceline.com
> Content-Type: text/xml; charset=”utf-8”
> Content-Length: nnnn
> SOAPAction: “”
> 
> <?xml version=”1.0”?>
> <SOAP-ENV:Envelope
> 	xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/SOAP/envelope/”>
> 	<SOAP-ENV:Body>
> 	<XXX:find xmlns:TALVA=”http://www.talva.com/schema/XXX”>
> 	    <resource>UP.Browser/3.01-IG01 UP.Link/3.2.3.4</resource>
> 	</XXX:find>
> 	</SOAP-ENV:Body>
> <SOAP-ENV:Envelope>
> 
> ask for the RDF element associated to this resource and return the following
> reply:
> 
> HTTP/1.1 200 OK
> Content-Type: text/xml; charset=”utf-8”
> Content-Length: nnnn
> <?xml version=”1.0”?>
> <SOAP-ENV:Envelope
> 	xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/SOAP/envelope/”>
> 	<SOAP-ENV:Body>
> 		<TALVA:GetDeviceProfile xmlns:TALVA=http://www.talva.com/schema/cc-pp
> 						    xmlns:rdf=”http://www.w3.org/1999/02/22-rdf-syntax-ns#”>
> 			<rdf:description about="UP.Browser/3.01-IG01 UP.Link/3.2.3.4">
> 				<up-uplink>up2.upl.sprintpcs.com</up-uplink>
> 				<fax-accepts>none</fax-accepts>
> 				<fax-limit>0</fax-limit>
> 				<soft-key-size>5</soft-key-size>
> 				<is-color>0</is-color>
> 				<charset>us-ascii</charset>
> 				<screen-chars>24,9</screen-chars>
> 				<screen-pixels>120,127</screen-pixels>
> 				<screen-depth>1</screen-depth>
> 				<max-pdu05d4></max-pdu>
> 			</rdf:description>
> 		</TALVA: GetDeviceProfile >
> 	</SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> 
> You have probably recognized here the CC/PP stuff. A peer to peer network
> could be useful to resolve a resource capability request. Now that you have
> the context, what are your ideas on the info exchange API between stores. we
> may try to create a chain of stores containing capability record with the
> following algorithm
> 
> a) the client request for a capability record,
> b) the server does not have it and ask to a linked store for it
> c) and so forth until one gets it, return the RDF record to the previous
> calling store... and so forth until the first requested store gets it and
> reply to the client with an RDF element.
> 
> Your ideas?
> 
> Cheers
> Didier PH Martin
> ----------------------------------------------
> Email: martind@netfolder.com
> Conferences: xml devconf 2000 (http://www.xmldevconf2000.com)
> Book: XML Professional (http://www.wrox.com)
> column: Style Matters (http://www.xml.com)
> 
> 
Received on Thursday, 7 September 2000 22:07:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:51:44 GMT