Meeting minutes
Persistent ID for current minutes: https://
Meeting minutes: https://
Previous minutes: https://
Admin
w3c-cg/dpv -\ new repo and redirects (HTML, w3id, browser extension) w3c-cg/
w3id redirect: Beatriz submitted a PR for redirection of w3c-cg repo url which should be merged soon
DPV 2.4
finalisation of release https://
ODRL mapping
Beatriz: created new issue for automatically generating the mapping for ODRL, i.e., w3c-cg/
Harsh: we can add this for 2.4 if possible
Proposals
objective of proposals is to provide members a space to 'host' their submissions with a formal url and acknolwedgement by DPV. This is not mandatory e.g. issues and PRs can still be used. This is to allow people to 'show' contributions e.g. in project deliverables and reports that the group has 'accepted' the proposal and is working with it.
to confirm: 1) proposals are on dev branch 2) w3id.org/dpv/proposals IRI which redirects to dev.dpvcg.org/proposals 3) we host the proposal documents, contributors can update on request
Beatriz: +1
Delaram: +1 also agree that there should be some maturity on the proposal, an d then when things get moved to the DPV not sure if we should keep the proposal and explain how it was integrated in the DPV
Harsh: add a note at the top of the proposal document once the proposal is accepted and integrated into DPV. We should keep the url as it would be in some publication or report and otherwise it will give a 404.
ACTION: beatriz to add w3id.org/dpv/proposals IRI which redirects to dev.dpvcg.org/proposals
proposed: AI Act Art.10 concepts from Fabian / Harsh https://
proposed: AI quality vocabulary concepts from Delaram/Beyza/Fabian/Harsh
Mappings from GDPR and NIS2
Ruhi: have updated them
Harsh: thanks, will also include them in 2.4
Harsh: Also good idea to do this for EHDS
Beatriz: We have a table, but not sure if we should add it to 2.4
Harsh: If the table is for concepts up to 2.4, yes, we should include. If it is also including concepts you are going to propose, then better to put it in 2.5
DPV 2.5
scheduled draft November, release early Jan
work program -\ priorities
no specific topics identified at this point, agenda will be based on existing work and updates
AOB
Harsh: found a mention of DPV in a diagram ; but no website or link about. Therefore haven't added it our adoption tracker. I think we should at least have some documentation that shows how / where DPV is used before updating the tracker.
Demo from Muhsin (about the use of DPV for recording AI output uses) -\ upcoming concepts in 2.4
Muhsin: we have a Chrome extension for Google Docs to record text that is generated by AI, the level of AI generation. It keeps track of what has been modified in the backend. This can be exported with a nice visualisation. The output is an annotated document that shows which text was AI generated, which was modified, and metadata about 'events'. There is also a log of whether the AI suggestions were accepted, were modified, etc. This is available right now. We are working on a beta next week. We are making a list on people who are interested and who have opinions.
Harsh: How do you use the concepts from DPV here? We had discussions on tracking the AI outputs, so want to see how DPV concepts look in the demo.
Muhsin: metadata is in JSON format, not fully aligned with DPV yet, but it will be with the release / final version
Sal: Can this be used for coding as well?
Muhsin: Haven't tested for coding yet, current focus is on text, but it could work for coding as well
Ruhi: what is the rate of error e.g. if we accuse a student of cheating or using AI, and we use other AI checking websites they have high error rates. What would it be if we used this for student assignment submissions?
Muhsin: This is recording while writing rather than evaluating a submission i.e. this is not detection. We are working on tamper-proofing it.
Harsh: Maybe a good idea to send an email to the mailing list explaining your work and what you want participants to do, and also how this is using the DPV concepts.