Meeting minutes
(continuation) resolution of proposed terms to DPV
document: https://
… user agent: needs more discussion on where to place within the DPV hierarchy
… HTTP request: rejected as too broad, non-specific as personal data (PD)
… user agent string: rejected, means same as or contains same information as user agent
… Request target (or HTTP request): needs more specific description; see proposed term related to "UsageHistory" or activity
… IP address: already exists
… HTTP cookies: relates to technology and not personal data; we have a separate discussion on how to associate technologies
… Actions on website: will be classified as browsing behaviour
… Unique Device Identifier (UDID): comes under Device Based and UID
… Payment card number: we have credit card number (but as financial account identifier). We add a generic payment card number as parent class to that.
ISSUE: how to specify associated properties such as card's expiry date or CVV such that "card details" will cover all of these?
<trackbot> Created ISSUE-40 - How to specify associated properties such as card's expiry date or cvv such that "card details" will cover all of these?. Please complete additional details at <https://
document: Customer's orders and suggestions, incidents, complaints: Add term as Feedback with specific categories as sub-classes
… Browser plugins: is too specific, we will have Device Software and sub-classes for operating system and apps
… last login: Too specific, we will have Authentication History
<harsh> Next meeting: next week 10:00am (Dublin, London) / 11:00am (CET) continuation on resolution of proposed terms