- From: Lorrie Cranor <lorrie+@cs.cmu.edu>
- Date: Mon, 13 Jun 2005 22:56:48 -0400
- To: 'public-p3p-spec' <public-p3p-spec@w3.org>
Here are the minor issues I found with the 4 January 2005 working draft http://www.w3.org/TR/2005/WD-P3P11-20050104/ Status As far as those suggestions have found sufficient support, they are now included in this new P3P 1.1 Working Draft. --> As a result of this feedback, the working group developed a list of problems to fix and new features to add. These problem fixes and new features are now included in this new P3P 1.1 Working Draft. All P3P 1.0 preserve their old namespace. --> All P3P 1.0 policy syntax continues to use the old namespace. 1.1.1 Reorder bullets to match numeric order of sections (3.3.X sections are out of order currently) Add bullet: In Section 3.3.3 a new definition is provided for the CONSEQUENCE element. In Section 3.36 --> In Section 3.3.6 2.3.2.9.1 OUR-HOST Extension There are several places where the space afer italicized text has been ommitted so words run together. user agents can not verify --> user agents cannot verify 2.3.2.9.3 Hosts may return an special token --> Hosts may return a special token authorityis --> authority is 2.5 elementcarrying --> element carrying 3.3.3 CONSEQUENCEelement --> CONSEQUENCE element 3.3.6.1 the URI of the 95/46 directive given here is no longer valid 5.1.1 Shouldn't we explain where the old format is defined (in the P3P 1.0 spec... provide specific section numbers) ? 5.5.1.2 why is there a triangle symbol before loccode ? 5.7 A translation of P3P including the data schema into RDF and OWL can be found at [UPDATE]. 6.4 Update ?? with approriate section General Do we want the xml namespace for the extension to be xmlns="http://www.w3.org/2004/02/P3Pv11" ?
Received on Tuesday, 14 June 2005 02:57:28 UTC