Meeting minutes
Repository: w3c/dpv
Agenda: https://
Meeting minutes: https://
Persistent ID for current minutes: https://
Note change in meeting link
v2.2
<ghurlbot> Issue 301 dpv 2.2 draft review (by coolharsh55)
Beta release
agreed to release a beta version as before following changes/fixes
Rule Fulfilment
<ghurlbot> Issue 351 DPV Rule Fulfilment Status - naming and alignment with ODRL (by coolharsh55)
HarshPandit: Proposed concepts (see issue #351)
GeorgKrog: agreed
HarshPandit: okay from Beatriz offline (email/github)
agreed on concepts
Agents
GeorgKrog: (paraphrased) use of Agents to perform tasks in workflows
ArthitSuriyawongkul: better to call it AgenticAISystem if its to be a subclass of AI System
ArthitSuriyawongkul: how is this different from AI Agent? For an Agent, you specify some goals or response to conditions and it goes off to do the work without response from the user. For my Agentic AI is that you define goals or results but not the how to achieve that, but the user is still waiting e.g. for an hour. So there is an element for waiting for the response.
HarshPandit: Agentic AI involves use of AI agents to execute tools/workflows
ArthitSuriyawongkul: so in thise sense Agentic is an adjective to the AI System to state AI agents are being used to achieve the tasks
next steps: look for normative definitions, otherwise discuss only adding the basic concepts for the vocabulary without additional specifics for v2.3
AI Development Phases
<ghurlbot> Issue 294 AI Model Development Phases (by coolharsh55)
HarshPandit: these are not well defined/standardised as compared to the ISO 5338 lifecycle; so should we model them and how do we select the concept?
DelaramGolpayegani: depends on which steps you want to take to develop the model; Should these concepts also consider whether it is a GenAI model and what are the steps to integrate that into the organisation
HarshPandit: these are processes as they involve e.g. data collection ...
ArthitSuriyawongkul: will this include the domain or user etc. before data collection. This is like a requirement.
DelaramGolpayegani: This is like requirements engineering in software development. How much of the lifecycle do we want to consider, and how many names/labels we want to include for different stages. This could be useful for looking at the value chain and seeing who is involved and when/where. E.g. to see who was involved in the earlier stages and tracing what happened/who is responsible. E.g. using PROV-O.
HarshPandit: sounds like the concepts are useful; so should these be done as part of existing lifecycle https://
DelaramGolpayegani: makes sense to start with lifecycle and see if it fits and then look for a different place if not; this will be helpful for the data governance and implementation of the AI Act
ArthitSuriyawongkul: reason to think about this is that the previous Biden gov executive order required documentation about stakeholders during the development of the AI requirements procedures; though this executive order is no longer around
DelaramGolpayegani: option to go for a sub-extension of AI for lifecycle
HarshPandit: no, because this fits in AI
next steps: develop a proposal based on ISO 5338 and aligned with common terminology used in AI domain
Use-Cases and Examples
<ghurlbot> Issue 12 Use-Cases and Examples showing how vocab can be used (by coolharsh55)
discussing making use-cases and examples being documented a necessary step for adding any new concept (continued discussion)
StratisKoulierakis: what counts as an example?
HarshPandit: e.g. data collection involves purpose, data subject e.g. customer, processing collect, etc.
StratisKoulierakis: and are these external examples from another source or created here to show how the vocabulary is used?
HarshPandit: the latter, these are the descriptions and examples in RDF showing in the HTML documents
accepted to make use-cases and examples a requirement for all new concepts
Development code
<ghurlbot> Issue 137 Move code for document/minute generation to another branch (by coolharsh55)
accepted changes to repo (moving code generator to dev branch)
AOB
Contribution Guidelines
HarshPandit: added external contribution section to contribution guide on Wiki https://
DPVCG referenced in EU policy
HarshPandit: detected reference/mention of DPVCG from 2020--2025 in the EU's Interoperability Europe documents referring to "Rolling ICT Standardisation". DPVCG is the only CG mentioned, along with ODRL as a standard. This means we are the state of the art for this topic and area! https://
Metadata Fields
<ghurlbot> Issue 359 [NEW]: Add versioning/deprecation information (by bact)
ArthitSuriyawongkul: meta fields like availableSinceVersion, deprecatedInVersion, supercededBy -- if they are useful/ worth the effort to have it e.g. within the metadata of the concept in RDF and shown in HTML; superceded by is provided in schema.org
HarshPandit: we have had cases or risks that the concepts are deprecated and people still use it because it is present; one option
next steps: Art and Harsh will discuss this for v2.3
Next Meeting
The next meeting will be on AUG-20 Thursday 13:30WEST/14:30CEST
Agenda will be finalising DPV v2.2 beta release, and starting work on v2.3 -- with a preference to identify topics for discussion where materials/arguments exist and so that we can revist what needs to be done for them.