RE: P3Pv1.xsd

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

Eric,

This differs slightly from the suggestion you sent to the list back in
April:

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

Give more time to think about things, are you now suggesting that the expiry
element isn't useful, and that the entity element (which can include things
like name and address of the policy publisher for those who might not
understand the schema) is?

<Scott/>

>-----Original Message-----
>From: Eric Brunner-Williams in Portland Maine
>[mailto:brunner@nic-naa.net]
>Sent: Monday, September 10, 2001 1:44 PM
>To: Hollenbeck, Scott
>Cc: 'ietf-provreg@cafax.se'; brunner@nic-naa.net
>Subject: P3Pv1.xsd
>
>
>Available at: http://www.s3.org/2000/12/P3Pv1.xsd, and here 
>for future list
>reference.
>
>As we look at data collectors using epp (registries, and 
>registrars, and even
>possibly resellers), there are several areas of the P3P 
>vocabulary that have
>different "fits" for our data collection policy purposes. In 
>top-to-bottom
>order these are (in my non-exhaustive estimation):
>	useful		not useful
>--------+---------------+----------------------------
>			POLICY-REFERENCES
>			POLICY-REF
>			EXPIRY
>			POLICIES
>			POLICY
>	ENTITY
>	ACCESS
>			DISPUTES-GROUP
>	STATEMENT
>	PURPOSE
>	RECIPIENT
>	RETENTION
>			DATA-GROUP
>			DATA
>	EXTENSION

[snip]