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

draft backwards compatibility guidelines

From: Lorrie Cranor <lorrie@research.att.com>
Date: Thu, 1 May 2003 10:04:25 -0400
To: public-p3p-spec@w3.org
Message-Id: <D0DEF3DA-7BDD-11D7-921D-000393DC889A@research.att.com>

Here is a draft of the backwards compatibility guidelines I was 
actioned to document on yesterday's conference call. Please send your 
comments and feedback. I would like to try reach closure on these (or 
an amended version of these) at our conference call next wednesday and 
document that it is the consensus of the working group to follow them.

Lorrie



BACKWARDS COMPATIBILITY GUIDELINES

The (draft) P3P 1.1 working group charter states "The P3P 1.1
Specification should be designed for backwards compatibility with the
P3P 1.0 Specification." Here are some details of what this means
and how we will apply this as the working group goes about its
business. This is not intended to be a comprehensive or absolute set
of requirements, but rather a set of guidelines to help the group
work towards a common goal. Working group members should keep these
guidelines in mind when making proposals to the working group and
avoid proposals inconsistent with these guidelines.

- P3P 1.0 user agents should be able to process P3P 1.1 policies and
   policy reference files. This implies both that the P3P 1.1 policies
   and policy reference files are fully compliant with the P3P 1.0 XML
   schema, and that the semantics of these files will not be
   misinterpreted by a user agent that interprets them according to
   the P3P 1.0 specification.

- New vocabulary elements and syntax introduced in P3P 1.1 should be
   introduced as optional extensions using the P3P 1.0 extension
   mechanism.

- New or changed P3P HTTP headers that are not backwards-compatible
   with P3P 1.0 should use a new prefix to differentiate them from
   those used in P3P 1.0. They should be designed such
   that sites that wish to make their P3P headers accessible to both
   P3P 1.0 and P3P 1.1 user agents can include both the P3P 1.0 and P3P
   1.1 headers.

- Changes to requirements or definitions introduced in P3P 1.1. should
   add clarity where the P3P 1.0 specification is ambiguous, but should
   not cause a particular P3P vocabulary element to have different
   meanings in P3P 1.0 and P3P 1.1.

- New requirements or features may be introduced in the P3P 1.1
   specification if they do not impact the ability of P3P 1.0 user
   agents to process P3P 1.1 policies and policy reference files. For
   example, a feature that would enable P3P policies to be referenced
   from arbitrary XML documents would not impact P3P 1.0 user agents,
   since those user agents do not attempt to find P3P policy references
   in arbitrary XML documents. Of course, P3P 1.0 user agents are not
   expected to comply with new requirements introduced in P3P 1.1.

- Features, vocabulary elements, or requirements may be removed in
   the P3P 1.1 specification as long as they do not cause a P3P 1.0
   user agent to be unable to process a P3P 1.1 policy or policy
   reference file.
Received on Thursday, 1 May 2003 10:03:45 EDT

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