- From: Lorrie Cranor <lorrie@research.att.com>
- Date: Thu, 11 Sep 2003 10:03:08 -0400
- To: Matthias Schunter <mts@zurich.ibm.com>
- Cc: public-p3p-spec@w3.org
Looks good except that if consent =always the required attribute could be omitted or it could be required=always (that's why I said it MAY be omitted). These two cases are semantically equivalent. Lorrie On Thursday, September 11, 2003, at 02:53 AM, Matthias Schunter wrote: > Hi Lorrie, > > thanks for your work! I've read through it and have only minor changes: > - Typo in Heading 3.7.2 "STATMENT-GROUP" > - Thanks for renaming 'required' to 'always'. This is more intuitive. > - By defining that for required="always", all inside statements must > not > have a required attribute, one can allow 'ours' and 'current' in > 'mixed' as > well as 'always' groups. I changed the spec accordingly. > - I agree that it may be easier to understand if statement-group-def > and > statement-group are explained together. In this case, the STATEMENT > section > in the consolidated spec should contain a reference/pointer to the > STATEMENT-GROUP extension. > > Enclosed is an update an a HTML-diff (note that this is experimental; > just > look at the differences in the text; it garbles the BNF). > > Regards, > matthias > > > > At 02:35 PM 9/10/2003 -0400, Lorrie Cranor wrote: >> Here is a revised version that addresses the issues we discussed on >> last >> week's call. Rigo, please post. Everyone, please review and send >> comments. >> >> Lorrie >> >> >> > <09-10-diff.htm><10-cc-changes-to-P3P.htm>-- Dr. Matthias Schunter > <mts (at) zurich.ibm.com> --- > IBM Zurich Research Laboratory, Ph. +41 (1) 724-8329 > Fax +41-1-724-8953; More info at www.semper.org/sirene > PGP Fingerprint 989AA3ED 21A19EF2 B0058374 BE0EE10D
Received on Thursday, 11 September 2003 10:02:42 UTC