W3C home > Mailing lists > Public > public-p3p-spec@w3.org > August 2004

Modification to Base Data Schema Spec

From: Giles Hogben <giles.hogben@jrc.it>
Date: Thu, 26 Aug 2004 14:07:01 +0200
To: <public-p3p-spec@w3.org>
Cc: "'Rigo Wenning'" <rigo@w3.org>
Message-ID: <000001c48b65$31d46f60$362abf8b@cs.jrc.it>
I made some modifications this document. In particular since creating the
P3P ontology, I realized that the BDS is not actually a class hierarchy - so
I have included this sentence to describe what it actually is:

Datatype sub-elements are organized into a class-like hierarchy of
increasing specificity. For an element b to be definied as an allowed child
of element a signifies that if an entity is stated to collect data of type
a, then it may also collect data of type b. The inverse relation however
does not hold. Transitivity also holds for this relation. That is, if  a
statement states that entity x may collect data of type a and b is an
allowed structure of a and c is an allowed structure of b, then it can be
assumed that x may collect data of type c. 


Received on Thursday, 26 August 2004 12:07:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:19 UTC