W3C home > Mailing lists > Public > www-p3p-dev@w3.org > October 2001

Re: APPEL and the dataschema element

From: Lorrie Cranor <lorrie@research.att.com>
Date: Mon, 1 Oct 2001 10:44:18 -0400
Message-ID: <00ec01c14a87$b37b7ee0$9816cf87@barbaloot>
To: "Giles Hogben" <giles.hogben@jrc.it>, "p3pdev" <www-p3p-dev@w3.org>
I  believe that if APPEL engines are to handle custom
dataschemas, then they must take stand-alone DATASCHEMA
elements as input, in addition to their other inputs. The
software that calls the APPEL engine would be responsible
for fetching the DATASCHEMA from wherever it might be located
and making it available to the APPEL engine.


----- Original Message -----
From: "Giles Hogben" <giles.hogben@jrc.it>
To: "p3pdev" <www-p3p-dev@w3.org>
Sent: Monday, October 01, 2001 10:37 AM
Subject: APPEL and the dataschema element

I have a question about how the inclusion of custom data schema elements
fits into the APPEL specification.

If a <DATA> element in an APPEL ruleset is to include elements outside of
the P3P data schema, then should it also include the schema it is referring
to as an inline schema.
If so, then it seems that the most recent change to the P3P spec causes a
conflict here. The p3p spec has just changed to state that DATASCHEMA
elements should be children of the POLICIES element. But APPEL at present
can only work at the level of single policies, so it cannot express the same
If not, then could somebody clarify what the policy is on use of custom data
elements wrt APPEL


Giles Hogben
Received on Monday, 1 October 2001 10:49:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:49:15 UTC