To:
Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
cc:
"Hollenbeck, Scott" <shollenbeck@verisign.com>, ietf-provreg@cafax.se, brunner@nic-naa.net
From:
Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Date:
Wed, 11 Apr 2001 11:18:01 -0400
In-Reply-To:
Your message of "Wed, 11 Apr 2001 10:10:31 EDT." <200104111410.f3BEAVD11241@nic-naa.net>
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: Registrant Access (Data Protection/Privacy)
Oops! Please disregard my last. I plead distraction or temporary insanity.
When we did the P3P spec (ongoing) we put in the EXTENSION element and put
in the optional attribute to allow the distinction between manditory and
optional extensions.
The ABNF is
extension = "<EXTENSION"
[" optional=" `"` ("yes"|"no") `"`] ">"
PCDATA
"</EXTENSION>"
The schema is
<!--
Extension
-->
<element name="EXTENSION">
<complexType mixed="true">
<choice minOccurs="0" maxOccurs="unbounded">
<any processContents="skip" minOccurs="0" maxOcc urs="unbounded"/>
</choice>
<attribute name="optional" type="abc:yes_no" use="default" value="yes"/>
</complexType>
</element>
I hope this is a little less incoherent, and it shows I didn't grep for
extension in your xsd set or I'd have found optExtType.
Eric