RE: "private" Element Attribute

["Hollenbeck, Scott" <shollenbeck@verisign.com>]

> On Tue, Oct 22, 2002 at 09:50:57AM -0400,
>  Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net> wrote 
>  a message of 68 lines which said:
> 
> > Please see the discussion of the data collection policy 
> <dcp> element,
> > in the -07 draft. This stuff got formalized for us around the London
> > meeting.
> 
> I was not there and I find nothing in the mailing list archive.

You need to look a little bit deeper.  Here are some pointers:

http://www.cafax.se/ietf-provreg/maillist/2001-04/msg00108.html

http://www.cafax.se/ietf-provreg/maillist/2001-07/msg00002.html

http://www.cafax.se/ietf-provreg/maillist/2001-09/msg00040.html

http://www.cafax.se/ietf-provreg/maillist/2001-09/msg00165.html

There's more, but I'm sure you can find them yourself if you look towards
the end of 2001 more closely.

> <dcp> has exactly the same problem: while it acknowledges the work of
> the P3P WG, it tries to reinvent P3P, instead of using it. At the cost
> of great complexity, EPP uses the whole XML zoo, including the ability
> to add any XML element (not just those specified in EPP) in an EPP
> element. Why not use <POLICY> and not <dcp>?

It's not trying to reinvent P3P at all -- it uses a subset of P3P that makes
sense in a different (that is, not web-based) operating environment.  All of
P3P just isn't appropriate for what we're doing.

"dcp" is an acronym for "Data Collection Policy".  "policy" by itself is too
vague a term to use in this context.

-Scott-