Meeting minutes
Persistent ID for current minutes: https://
Meeting minutes: https://
Previous minutes: https://
Admin
migration to repo to w3c-cg/dpv on github
w3c/
DPV 2.4
proposed work program
https://
India's DPDP
w3c/
EHDS
w3c/
no updates
DE-GDNG
w3c/
no updates
AI Use Transparency
w3c/
update on github issue -- another contributor has also expressed support; please review and express support / decision on github, we will take this up again next week as concepts to be added
AI model openness
w3c/
AI Documentation (e.g. Datasheets and Model Cards)
w3c/
yes add these concepts in AI extension
AI Documentation proposal from Fabian: AI Act
https://
https://
w3c/
to be updated on the issue, to be reviewed by Delaram for pending concepts
(mailing list thread) DPV TOM extension with more PETs https://lists.w3.org/Archives/Public/public-dpvcg/2026Mar/0009.html
continuation of the thread on the mailing list ;
Beatriz: we already had a meeting this week, they are looking to use DPV and ODRL together. We had initial thoughts on how to make that happen, and we will have follow-up meetings for concrete proposals, but nothing just yet.
New issues / updated issues
native language labels in spreadsheets
w3c/
modelling AISI concepts for jurisdictions
w3c/
Harsh: what is AISI in Korean law? What is it supposed to do?
Art: I think its Art.32, it seems that when there is a security concern, then the AI Provider has to report it to the ministry of ICT, and they mention AISI as a 'supporting' body. So in this sense, its not an authority, but a support body https://
Art: Question on URL encoding. Should we use the URL with native scripts (Unicode) or one that encoded as ASCII (Punycode / https://
Harsh: Use the Unicode. If we use ASCII one, it will lost its meaning that can be useful for people who can read the native scripts. RDF should handle the Internationalized IRI fine. Let the serialization manage the final URL.
Art: Agree.
AOB
Art: PR from Art to remove stale CSVs
Muhsin: link to minutes does not resolve
Harsh: <issue with w3id/github cg resolution>
DPDP meeting
discussion of DPDP in the same room after DPVCG meeting agenda
Beatriz: consent manager
Ajay: consent management, consent holder (citizen who is giving consent) can switch from one consent manager to another, consent receipt should be portable i.e. move from one manager to another, citizens are free to use any consent manager
Ajay: the second thing is that consent records and receipts should be interoperable; which is the law; but the law does not prescribe a specific standard -- just that it has to be compatible; so it relies on the implementations. Goal is to have a standard for interoperable consent records and receipts.
Harsh: we have work on ISO 27560 which helps with this; and we are also involved in the revision of this standard; and we have a DPV implementation guide for consent records -- so we need to create a guide for the requirements of DPDP
Art: Don't have a specific focus but want to learn the process as I want to do similar things for the Thai data protection law; specifically those parts that concern cross-border data transfer
Harsh: what does your organisation do for DPDP (to Ajay)
Ajay: we are not an official consent manager as approved by the govt, but we build consent management solutions for our clients