- From: <giles.hogben@jrc.it>
- Date: Tue, 12 Jul 2005 21:48:25 +0200
- To: rigo@w3.org, lorrie@cs.cmu.edu, public-p3p-spec@w3.org
I've thought out more fully how my proposal for categories would work using XSD, and I have a proposal for further simlification which I'd like your thoughts on:
First note that categories are NOT used in P3P policies except with dynamic.miscdata and dynamic cookies elements therefore they have no meaning in a policy schema except for these elements. However the aim is that rules (e.g. APPEL) agents can use them to match broad groups of data elements. So what I'm thinking now is that instead of messing up the schema with the category assignments which are never used by the policy, we could do as follows:
1. In the XSD schema, have only the categories that are used - so it would basically look like the tree in B. below:
This would have no problems with backward compatibility whatsoever and would achieve the desired simplification.
The elements would look like:
<navigation><dynamic><miscdata/></dynamic></navigation>
OR
<user><home-info><postal><name/></postal></home-info></user>
2. We add a separate categories XML file which is NOT an XSD schema but defines which categories an APPEL like system may associate with which data elements in a policy (**or we could even leave it up to an APPEL spec to do this instead of us, having just a recommendation and example in the spec**). Example of what the file would look like in A. below
The key point to note is that the category assignments for non-dynamic elements are only used by APPEL so there is no need for them to be part of the XSD.
One further small comment is that it makes sense to rename the Name under business to orgname because it has a different substructure. This is the only example of where an element with the same name cannot simply be attached by reference so it makes sense to change it.
Let me know what you think and if you agree, I'll implement it this way,
Regards
Giles
**********************************************************
A. Category assignment file (NOT an XSD) defines what can be written in an APPEL like rule to match what data elements - the agent would take the LEAF of the policy data element (<name/> in the above) and see which categories it was included in below to see whether it matched the rule.
<navigation>
<dynamic/>
<miscdata/>
<cookies/>
<uri/>
<timestamp/>
<other.httpmethod/>
<other.bytes/>
<other.statuscode/>
<referrer/>
<clickstream/>
<clientevents/>
</navigation>
<uniqueid>
<business/>
<user/>
<thirdparty/>
<dynamic/>
<miscdata/>
<cookies/>
<id/>
<password/>
<key/>
<format/>
<login/>
<cert/>
</uniqueid>
<online/>
<home-info/>
<business-info/>
<contact-info/>
<computer/>
<dynamic/>
<miscdata/>
<cookies/>
<clickstream/>
<http/>
<hostname/>
<fullip/>
<useragent/>
</online>
<interactive>
<dynamic/>
<miscdata/>
<cookies/>
<searchtext/>
<interactionrecord/>
</interactive>
Etc...
*************************************
B. Revised tree structure of XSD data schema
**************************************
datatype
|
+navigation
| +dynamic
| +miscdata
| +cookies
+uniqueid
| +dynamic
| +miscdata
| +cookies
+demographic
| +dynamic
| +miscdata
| +cookies
+physical
| +dynamic
| +miscdata
| +cookies
+online
| +dynamic
| +miscdata
| +cookies
+computer
| +dynamic
| +miscdata
| +cookies
+interactive
| +dynamic
| +miscdata
| +cookies
+dynamic
| +clickstream
| | +uri
| | | +authority
| | | +stem
| | | +querystring
| | +timestamp
| | | +ymd.year
| | | +ymd.month
| | | +ymd.day
| | | +hms.hour
| | | +hms.minute
| | | +hms.second
| | | +fractionsecond
| | | +timezone
| | +clientip
| | | +hostname
| | | +partialhostname
| | | +fullip
| | | +partialip
| | +other.httpmethod
| | +other.bytes
| | +other.statuscode
| +http
| | +referer
| | | +authority
| | | +stem
| | | +querystring
| | +useragent
| +clientevents
| +searchtext
| +interactionrecord
|
+user
| +name
| | +prefix
| | +given
| | +middle
| | +family
| | +suffix
| | +nickname
| +bdate
| | +ymd.year
| | +ymd.month
| | +ymd.day
| | +hms.hour
| | +hms.minute
| | +hms.second
| | +fractionsecond
| | +timezone
| +login
| | +id
| | +password
| +cert
| | +key
| | +format
| +gender
| +jobtitle
| +home-info
| | +postal
| | | +name
| | | | +prefix
| | | | +given
| | | | +middle
| | | | +family
| | | | +suffix
| | | | +nickname
| | | +street
| | | +city
| | | +stateprov
| | | +postalcode
| | | +organization
| | | +country
| | +telecom
| | | +telephone
| | | | +intcode
| | | | +loccode
| | | | +number
| | | | +ext
| | | | +comment
| | | +fax
| | | | +intcode
| | | | +loccode
| | | | +number
| | | | +ext
| | | | +comment
| | | +mobile
| | | | +intcode
| | | | +loccode
| | | | +number
| | | | +ext
| | | | +comment
| | | +pager
| | | +intcode
| | | +loccode
| | | +number
| | | +ext
| | | +comment
| | +online
| | +email
| | +uri
| +business-info
| +postal
| | +name
| | | +prefix
| | | +given
| | | +middle
| | | +family
| | | +suffix
| | | +nickname
| | +street
| | +city
| | +stateprov
| | +postalcode
| | +organization
| | +country
| |telecom
| | +telephone
| | | +intcode
| | | +loccode
| | | +number
| | | +ext
| | | +comment
| | +fax
| | | +intcode
| | | +loccode
| | | +number
| | | +ext
| | | +comment
| | +mobile
| | | +intcode
| | | +loccode
| | | +number
| | | +ext
| | | +ext
| | | +ext
| | | +comment
| | +pager
| | +intcode
| | +loccode
| | +number
| | +ext
| | +comment
| |online
| | +email
| | +uri
| +employer
| +department
+thirdparty
| +name
| | +prefix
| | +given
| | +middle
| | +family
| | +suffix
| | +nickname
| +bdate
| | +ymd.year
| | +ymd.month
| | +ymd.day
| | +hms.hour
| | +hms.minute
| | +hms.second
| | +fractionsecond
| | +timezone
| +login
| | +id
| | +password
| +cert
| | +key
| | +format
| +gender
| +jobtitle
| +home-info
| | +postal
| | | +name
| | | | +prefix
| | | | +given
| | | | +middle
| | | | +family
| | | | +suffix
| | | | +nickname
| | | +street
| | | +city
| | | +stateprov
| | | +postalcode
| | | +organization
| | | +country
| | +telecom
| | | +telephone
| | | | +intcode
| | | | +loccode
| | | | +number
| | | | +ext
| | | | +comment
| | | +fax
| | | | +intcode
| | | | +loccode
| | | | +number
| | | | +ext
| | | | +comment
| | | +mobile
| | | | +intcode
| | | | +loccode
| | | | +number
| | | | +ext
| | | | +comment
| | | +pager
| | | +intcode
| | | +loccode
| | | +number
| | | +ext
| | | +comment
| | +online
| | ?email
| | +uri
| +business-info
| +postal
| | +name
| | | +prefix
| | | +given
| | | +middle
| | | +family
| | | +suffix
| | | +nickname
| | +street
| | +city
| | +stateprov
| | +postalcode
| | +organization
| | +country
| |telecom
| | +telephone
| | | +intcode
| | | +loccode
| | | +number
| | | +ext
| | | +comment
| | +fax
| | | +intcode
| | | +loccode
| | | +number
| | | +ext
| | | +comment
| | +mobile
| | | +intcode
| | | +loccode
| | | +number
| | | +ext
| | | +comment
| | +pager
| | +intcode
| | +loccode
| | +number
| | +ext
| | +comment
| +online
| | +email
| | +uri
| +employer
| +department
|
+business
+orgname
|department
+cert
| +key
| +format
+contact-info
+postal
| +orgname
| +name
| +street
| +city
| +stateprov
| +postalcode
| +organization
| +country
+telecom
+telephone
| +intcode
| +loccode
| +number
| +ext
| +comment
+fax
| +intcode
| +loccode
| +number
| +ext
| +comment
+mobile
| +intcode
| +loccode
| +number
| +ext
| +comment
+pager
| +intcode
| +loccode
| +number
| +ext
| +comment
+online
+email
+uri
Received on Tuesday, 12 July 2005 19:48:35 UTC