To:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
cc:
"'Eric Brunner-Williams in Portland Maine'" <brunner@nic-naa.net>, "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>, brunner@nic-naa.net
From:
Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Date:
Mon, 17 Sep 2001 13:58:54 -0400
In-Reply-To:
Your message of "Mon, 17 Sep 2001 08:31:55 EDT." <3CD14E451751BD42BA48AAA50B07BAD6C5FA45@vsvapostal3.prod.netsol.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: P3Pv1.xsd
>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? Actually Scott what I wanted to do was put the xsd out as-is before going off to Montevideo (ICANN) and vacation (now). It will be a few days before I make it back to Portland. The semantic nexus of P3P Spec WG discussion of expiry is the data collector making a promise (of sorts) about the non-necessity of re-fetching and re- evaluatinga policy. I don't think "expiry" is the sense of a temporal ID we need, and we've already got <*Date>. Eric