W3C home > Mailing lists > Public > public-p3p-spec@w3.org > May 2003

RE: [BH] First (Very Rought) Outline of Beyond HTTP

From: <Patrick.Hung@csiro.au>
Date: Wed, 14 May 2003 21:26:50 +1000
Message-ID: <754324CDE8E4EE4498D8E0357D9136850160105F@saab-bt.act.cmis.CSIRO.AU>
To: reagle@w3.org, public-p3p-spec@w3.org

Hi Joseph,

> Patrick, the service description is true to the scenario, but as I'm not a

> WSDL expert, what led you to include the my:Privacy element as a child of 
> the wsdl:definitions?

I just try to make it simple and follow the style of your XForm example [1].

There may have other much better approach... I have to think about it...
Auy idea?

> So if I understand the WSDL extension model, we would also have to have
our 
> own schema that includes a redefinition of globalExt or base my:Privacy on

> the ExtensibilityElement complexType? (I don't understand this myself yet 
> and haven't found a good example.)

Is this something that you are looking for [1]:

       <schema targetNamespace="http://registry.example.com/2003/ns1.xsd"
              xmlns="http://www.w3.org/2000/10/XMLSchema">
           <complexType name="OrderInfo">
              <all>
                 <complexType name="PersonalInfo">
                    <all>
                       <complexType name="Name">
                          <all>
                             <element name="First" type="string"/>
                             <element name="Middle" type="string"/>
                             <element name="Last" type="string"/>
                          </all>
                       </complexType>        
                       <complexType name="Address">
                          <all>
                             <element name="Street" type="string"/>
                             <element name="City" type="string"/>
                             <element name="State" type="string"/>
                             <element name="Zip" type="string"/>
                          </all>
                       </complexType>
                    </all>
                 </complexType>
                 <complexType name="DomainInfo">
                    <all>
                       <element name="TLD" type="string"/>
                       <element name="DomainName" type="string"/>
                    </all>
                 </complexType> 
              </all>
           </complexType>
           <element name="RegistrationStatus" type="string"/>
           <complexType name="Privacy">
              <attribute name="rel" type="string" use="required"/>
              <attribute name="href" type="string" use="required"/>
           </complexType>
       </schema>

I am lazy here so that I put all stuff into one schema
"http://registry.example.com/2003/ns1.xsd"
We should separate the data types and the P3P privacy policies into
different schemas.
Anyway, let's focus on the basic concept and approach first and then we can
polish
and debug it later.

> Also, I presume that our WSDL extension is optional. Privacy is not
optional 
> at the point of solicitation, but since we are saying a WSDL declaration
is 
> (usefully) redundant, I don't think we need to argue that a WSDL processor

> must understand our extension to even process the description.

Yes, I agree with you. I will write something about SOAP messages tomorrow.

[1] http://www.w3.org/P3P/2003/p3p-beyond-http/
Received on Wednesday, 14 May 2003 07:27:01 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 17 March 2004 17:46:24 EST