W3C home > Mailing lists > Public > semantic-web@w3.org > January 2007

Re: web of data: how to include forms?

From: François-Paul Servant <francois-paul.servant@renault.com>
Date: Fri, 12 Jan 2007 11:49:02 +0100
Message-ID: <45A7679E.3070202@renault.com>
To: semantic-web@w3.org
Thank you for your comments.

Let's take an example to clarify.
You (or a program) wants information about removing the engine from a car.
If you are a human, you connect to the documentation server and you discover, 
for instance choosing among a hierarchy of skos-concepts, that you have to 
access the following URL:
ex:engine_removal
If you are a program, let's say that you already know that you have to access 
this URL.
You specify in the accept http header that you want to receive RDF data.

Let's say now that the way of removing the engine depends on the model of the 
car and on the type of engine. The documentation application must know these 
characteristics of your car in order to return the information that you actually 
need. (It would not make sense to return information about all the cars, not 
only because it would be a waste of bandwidth, but also because you would not be 
able to choose the pieces that are relevant to you). Hence the idea of returning 
to the client a "rdf-form", something such as:
<rdf:Description rdf:about"ex:engine_removal">
	<form:hasForm>
		<form:Form>
			<form:param rdf:resource="ex:model"/>
			<form:param rdf:resource="ex:engine_type"/>
		</form:Form>
	</form:hasForm>
</rdf:Description >

If the client program knows the conventions of the "form vocabulary", it can 
construct the following URL and send a get to it:
ex:engine_removal?ex:model=modelvalue&ex:engine_type=enginetypevalue
(url encoding needed here)

The important point: the client program knows the meaning of the params of the form.

For the model value and engine value returned by the user, the documentation 
application will maybe notice that the removal of the engine depends also on the 
type of gearbox. In this case, it will return another form asking for it:
<rdf:Description 
rdf:about"ex:engine_removal?ex:model=modelvalue&ex:engine_type=enginetypevalue">
	<form:hasForm>
		...
Note that REST principles are respected here.

Remark: a car has a URI (its "Vehicle Identification Number" or "VIN"). With 
this value, we can get at one time all (or most) of the technical 
characteristics of a car (they are stored in a database). We would use it in a 
real application.

Would it be possible to use SPARQL in the process described here?

Best Regards,

fps


-- Disclaimer ------------------------------------
Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme.
***
This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system.
Received on Friday, 12 January 2007 14:24:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:41:54 UTC