W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > December 2001

P3P: A reification use case #2

From: Brian McBride <bwm@hplb.hpl.hp.com>
Date: Thu, 20 Dec 2001 12:10:55 +0000
Message-Id: <5.1.0.14.0.20011220120529.02eb66a8@0-mail-1.hpl.hp.com>
To: RDF Core <w3c-rdfcore-wg@w3.org>
A second use case occurred in my P3P work.  In this case I have actually 
done it another way, but here is the possibilty.

P3P defines an extension mechanism, where it is possible to include in a 
P3P profile xml elements not defined in the P3P specification.  Such 
extensions are introduced by a special P3P element meaning "here be an 
extension" which takes an attribute defining whether or not a P3P processor 
must barf if it does not understand the extension.  If the extension is 
marked as mandatory, then  the P3P processor must 'understand' and process 
the extension.

In the RDF translation, these extension elements are translated into 
statements.

Reification could be used to annotate statements resulting from an 
extension to define whether they are optional or mandatory.

Brian 
Received on Thursday, 20 December 2001 09:53:25 EST

This archive was generated by hypermail pre-2.1.9 : Wednesday, 3 September 2003 09:43:03 EDT