Re: Ris: ISSUE-40: How to specify associated properties such as card's expiry date or cvv such that "card details" will cover all of these?

Hi Piero, yes, this is correct.

This was also the first (impulsive) choice we discussed, and we 
currently have this model in a few places in the DPV.

The issue itself arises as Card Number itself is declared as a 
"financial account identifier". So (IMO) we should take care to not 
imply that card details are account identifiers and instead carefully 
map them as Financial information or which Card Number is also an 
Account identifier.

tldr; Add class called PaymentCardDetails with subclass 
PaymentCardNumber (+subclass of AccountIdentifier) and 
PaymentCardExpiryDate etc.

Regards,
Harsh

On 11/11/2020 14:26, pieroandrea.bonatti@unina.it wrote:
> My first suggestion would be : Can't expiry and cvv be just subclasses 
> of card details?  Are there any reasons for doing otherwise? (PS: 
> apologies for not being able to participate in today 's call, probably 
> if I could my questions would have an answer)
> 
> 
> 
> -------- Messaggio originale --------
> Da: Data Privacy Vocabularies and Controls Community Group Issue Tracker 
> <sysbot+tracker@w3.org>
> Data: mer 11 nov 2020, 15:13
> A: public-dpvcg@w3.org
> Oggetto: ISSUE-40: How to specify associated properties such as card's 
> expiry date or cvv such that "card details" will cover all of these?
> 
>     ISSUE-40: How to specify associated properties such as card's expiry
>     date or cvv such that "card details" will cover all of these?
> 
>     https://www.w3.org/community/dpvcg/track/issues/40
> 
>     Raised by:
>     On product:
> 
> 
> 
> 
> 

-- 
---
Harshvardhan J. Pandit, Ph.D
Research Fellow
ADAPT Centre, Trinity College Dublin
https://harshp.com/

Received on Wednesday, 11 November 2020 16:35:35 UTC