- From: Dan Brickley <danbri@w3.org>
- Date: Thu, 16 Jan 2003 15:10:59 -0500
- To: Rich Salz <rsalz@datapower.com>
- Cc: Mark Baker <distobj@acm.org>, Sudhir Agarwal <sag@aifb.uni-karlsruhe.de>, xml-dist-app@w3.org
* Rich Salz <rsalz@datapower.com> [2003-01-16 14:57-0500] > > >http://example.com/averages?temp=http://example.org/temp/city/Ottawa > > Doesn't this require the "averages" program to know the output format? ...which is where we benefit from shared output formats. XML obviously. RDF, less obviously to some. RDF gives you structural similarity across a variety of XML-encoded output formats. Instead of needing to know the encoding rules used by each service, a generic datamodel-to-encoding strategy is used, so that applications share knowledge of the classes/properties encoded in the XML, rather than less interesting knowledge of the encoding strategies used by each service/site. In that respect, RDF and SOAP Encoding are strangely similar... Dan
Received on Thursday, 16 January 2003 15:11:03 UTC