This is a hypertext version of a P3P1.0 DTD. All links points to other hypertext documents. Actual DTDs, can be found at:
<!-- This is the P3P 1.0 proposal DTD. The proposal DTD imports two other DTDs: practices (privacy practice disclosures), and categories (used to describe data elements and sets). This is done such that schemas can be more easily changed and migrated independently of each other. The DTD's provided in this document are provided for normatively defining the P3P1.0 name space and as an exercise in ensuring the robustness of the data structures. However, it is known to be incomplete. The normative notation for this specification is the ABNF found in the specification.
URL: http://www.w3.org/TR/WD-P3P10-syntax-19980702/proposal.dtd
Draft: $Date: 1998/07/02 21:43:19 $
Authors: Joseph Reagle <reagle@w3.org>
Further information about P3P 1.0 is available at:
Typical usage: <?XML version="1.0" encoding="UTF-8" ?> <!DOCTYPE proposal SYSTEM "http://www.w3.org/TR/WD-P3P10-syntax-19980702/proposal.dtd"> <PROP> ... </PROP> -->
<!--================== Imported Names =======================-->
<!entity % URI "CDATA" -- a Uniform Resource Identifier, per P3P1.0 spec -->
<!entity % dataelement "CDATA" -- a string with syntax as specified by section 4 of P3P1.0 -->
<!--======= Import TXD and Qualifier DTD =======-->
<!entity % practices PUBLIC "http://www.w3.org/TR/WD-P3P10-syntax-19980702/practices.dtd"> %practices;
<!entity % categories PUBLIC "http://www.w3.org/TR/WD-P3P10-syntax-19980702/categories.dtd"> %TXD;
<!--======= The Proposal =======-->
<!ELEMENT PROP (USES+, DISCLOSURE) > <!ATTLIST PROP agreeID CDATA #REQUIRED -- agreementID realm %URI #REQUIRED -- realm of proposal -- entity CDATA #REQUIRED -- responsible organization -- assure %URI #REQUIRED -- assurance party -- propURI %URI #IMPLIED -- where to fetch proposal -- postURI %URI #IMPLIED -- where to post data -- optional ("0" | "1") "0" -- optional proposal -- >
<!ELEMENT USES (STATEMENT+) >
<!ELEMENT STATEMENT (DATA+) > <!ATTLIST STATEMENT %qualifier; -- purpose, recipient, id -- action ("r" | "rw" ) "r" -- read or read&write -- consq CDATA #IMPLIED -- consequence to user -- >
<!--======= The data request and transfer structure =======-->
<!ELEMENT DATA ( ((WITH, PREFIX)? | REF?)+ ) >
<!ELEMENT WITH EMPTY>
<!ELEMENT PREFIX (REF+ | PREFIX+)> <!ATTLIST PREFIX name %dataelement #REQUIRED -- prefix name -- template ("1" | "0") "0" -- template -- short CDATA #IMPLIED -- short name -- >
<!ELEMENT REF EMPTY> <!ATTLIST REF name %dataelement #REQUIRED -- data element name -- value CDATA #IMPLIED -- data element value -- optional ("1" | "0") "0" -- optional data element -- %createattrs; -- other attributes) -- %categories; -- categories -- >
<!-- These are optional attributes used in the creation or use of new data sets, types, or elements -->
<!entity % createattrs 'dataschema %URI #IMPLIED -- data schema -- type CDATA #IMPLIED -- defined by spec typeschema %URI #IMPLIED -- data type schema -- template ("1" | "0") #IMPLIED -- data type template -- short CDATA #IMPLIED -- short name -- long CDATA #IMPLIED -- long name -- ' >