- From: Lorrie Cranor <lorrie@research.att.com>
- Date: Wed, 25 Oct 2000 11:27:41 -0400
- To: "Gary Moison" <gary.moison@youpowered.com>, <www-p3p-dev@w3.org>, <www-p3p-public-comments@w3.org>
Gary, Thank you for your comments. I think adding a statement explaining that required is defined as in section 3.3.4 will claify this. We can also say that the default is always. Lorrie Cranor P3P Specification Working Group Chair ----- Original Message ----- From: "Gary Moison" <gary.moison@youpowered.com> To: <www-p3p-dev@w3.org>; <www-p3p-public-comments@w3.org> Sent: Wednesday, October 25, 2000 11:14 AM Subject: ? regarding the Recipient Element. > > Hello, > > The 10/18 spec made changes to the RECIPIENT element. > The statment : 'with the exception of <ours>, a required tag (analogously > to purposes), > indicating whether opt-in/opt-out sharing is available' > is somewhat unclear to me. > > Information in the Purpose's section provides a definition of required > required = " required=" `"`' ("always"|"opt-in"|"opt-out") `"` > as well as specifing that 'always' is the default when no required attribute > is present. > Which is clear to me, however, the Recipient section does not go into this > kind of specifics. > From what is there I would infer that only "opt-in" and "opt-out" should be > available. But is there a > default when no 'required' is provide ? > > Thanks > Gary > > ________________________________________________________ > Gary Moison YOUpowered, Inc. > permission based personalization > www.YOUpowered.com > > (e-mail) gary.moison@YOUpowered.com > (phone) 978.322.4324 > (fax) 978.322.4310 > > The views expressed in this message are my own and do not represent > those of YOUpowered, Inc. > > >
Received on Wednesday, 25 October 2000 11:28:21 UTC