- From: Piero Bonatti <pieroandrea.bonatti@unina.it>
- Date: Wed, 12 Dec 2018 08:23:05 +0100
- To: public-dpvcg@w3.org
Rigo, below you find some illustrative examples On 11/12/18 18:53, Rigo Wenning wrote: > Piero, > > On Tuesday, December 11, 2018 8:04:08 AM CET Piero Bonatti wrote: >> The hierarchical organization of classes automatically caters for "all >> sub-purposes of..." statements (a purpose includes automatically all of >> its sub-purposes). In order to select a list of subpurposes we simply >> take their union. So far this approach has not shown any drawbacks in >> our use cases. > > I will need to see some angle brackets to start to play with this. > > --Rigo Consider a policy P1 with data category Demographic and purpose ObjectUnionOf( Admin Develop ) // union of purposes 1) if P1 expresses a subject's consent, then it allows to use the subject's demographic data both for administration purposes and for development purposes. 2) if P1 expresses a business policy, then the controller intends to use the subject's demographic data both for administration purposes and for development purposes. Consider a policy P2 with data category Demographic and purpose ObjectIntersectionOf( PhoneContact Delivery ) // intersection of purposes 3) if P2 expresses a subject's consent, then it allows to use the subject's demographic data to contact the subject by phone in order to deliver some good. 4) if P2 expresses a business policy, then the controller intends to use the subject's demographic data to contact the subject by phone in order to deliver some good. Summarizing: union is good to cover a selected list of different purposes (while AnyPurpose would cover *all* possible purposes). Intersection is good to compose refined purposes from the basic ones. Hope this helps Piero
Received on Wednesday, 12 December 2018 07:22:31 UTC