- From: <Patrick.Hung@csiro.au>
- Date: Thu, 15 May 2003 17:20:41 +1000
- To: reagle@w3.org, public-p3p-spec@w3.org
Hi Joseph, Based on the Registrar2Registry example discussed so far, I
simply create
the SOAP messages as follows:
The Request SOAP Message from Registrar2Registry
================================================
<?xml version='1.0' ?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Header>
<env:Privacy>
<env:rel>P3Pv1</env:rel>
<env:href>http://registry.example.com/P3P/PolicyReferences.xml</env:href>
</env:Privacy>
</env:Header>
<env:Body>
<p:OrderInfo
xmlns:p="http://registry.example.com/RegisterService/RegisterDomainName">
<p:PersonalInfo>
<p:Name>
<p:First>Joseph</p:First>
<p:Middle>M.</p:Middle>
<p:Last>Reagle Jr.</p:Last>
</p:Name>
<p:Address>
<p:Street>200 Tecnology Square</p:Street>
<p:City>Cambridge</p:City>
<p:State>MA</p:State>
<p:Zip>02139</p:Zip>
</p:Address>
</p:PersonalInfo>
<p:DomainInfo>
<p:TLD>com</p:TLD>
<p:DomainName>reagle.example</p:DomainName>
</p:DomainInfo>
</p:OrderInfo>
</env:Body>
</env:Envelope>
The Response SOAP Message from Registry2Registrar
=================================================
<?xml version='1.0' ?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Header>
<env:Privacy>
<env:rel>P3Pv1</env:rel>
<env:href>http://registry.example.com/P3P/PolicyReferences.xml</env:href>
</env:Privacy>
</env:Header>
<env:Body>
<p:RegistrationStatus
xmlns:p="http://registry.example.com/RegisterService/RegisterDomainName">
OK
</p:RegistrationStatus>
</env:Body>
</env:Envelope>
Again we are trying to introduce an extensible element for SOAP header, or
you have any other idea.
Anyway, I will study the SOAP and check how to do it tomorrow.
Once we have all these protocols, we can start to discuss about the issues
of intermediaries and
ltimate SOAP receiver for the section "Transferring to a third party."
Thanks and talk to you later.
Patrick.
Received on Thursday, 15 May 2003 03:20:48 UTC