DPVCG Meeting Call

Meeting minutes: https://w3id.org/dpv/meetings

purl for this meeting: https://w3id.org/dpv/meetings/meeting-2024-04-10

w3id urls

<ghurlbot> Issue 133 w3id update for dpv2 (by coolharsh55)

harsh: the issues with the urls have been fixed and the changes are live, see https://harshp.com/dpv-x/status-check ; the existing 5 errors are related to either pages not currently existing (e.g. AI Act) or mistakes in the urls to check (response is 200 success). This will be updated to fix these issues.

ISWC resource paper

<ghurlbot> Issue 131 DPV Resource Paper (by coolharsh55)

harsh: not much work done here, with beatriz - do we think this is feasible and doable for the week ahead?

beatriz: doing citation analysis, depends on whether we can write the paper

harsh: I have materials from funding proposals etc. - I can put these together for the paper, so yes, for writing we should be okay

harsh: would be good to have support for writing and citation analysis etc. - please contact me or beatriz

harsh: we're presenting DPV to the EU Commission next week, preparing for that includes polishing off things a bit (I've been slow on doing the technical stuff) - so that will also help with the paper

dpvcg.org

<ghurlbot> Issue 132 Landing page for DPV (by coolharsh55)

harsh: obtained the domain

georg: we should put materials on the website for each concept like a guideline to show how the DPVCG is being used

harsh: agreed, but this is difficult to do in the short term for next week's meeting

georg: the EU COM is going to be making decisions in Q4 2024 on this - so should be done to showcase what can be done

georg: this includes showing what is possible e.g. automated contracts, work on the actual data rather than just the data

harsh: for smart contracts or digital contracts, the existing standard is ODRL and we've been conscious about not overlapping with it so as to support existing standards. The new v3 is under development, beatriz would know about how to relate both dpv and odrl

beatriz: ODRL v3 won't have anything specific for laws, but the good part is that there will be profiles and mechanisms to support such uses through a "ODRL Community Vocabulary"

harsh: we can provide concepts such as extensions to Policy for ConsentRequest, ConsentOffer, ConsentAgreement ;; beatriz please send email on how to contribute this

AI and AI Act

<ghurlbot> Issue 106 Propose concepts from the AI Act (by coolharsh55)

<ghurlbot> Issue 126 AI Extension to provide AI-specific concepts (by coolharsh55)

delaram: no updates

harsh: going through spreadsheet - separated tabs to create the HTML (will do it later today)

harsh: IntendedPurpose - how to model this? Parent is listed dpv:Purpose

delaram: this is not correct - it doesn't fit the dpv:Purpose description as it is broader than the notion of purpose

harsh: so this would be analogous to dpv:Process - my only concern is that people will see 'purpose' in IntendedPurpose and use dpv:hasPurpose with it. So we should also provide aiact:hasIntendedPurpose with it which is a sub-property of dpv:hasProcess and explicitly put in the definition that it is separate from dpv:Purpose

discussion on this topic

georg: conclusion of the discussion is that IntendedPurpose is different from dpv:Purpose as it is broader

harsh: IntendedPurpose with additional details with the instance as the subject e.g. IntendedPurpose hasContext SomeDetails

harsh: see examples of the two approaches as - 1) when we have parent as dpv:Purpose

:X a aiact:IntendedPurpose . # subclass of dpv:Purpose
    skos:broader ex:ProviderIntendedPurpose ;
    dpv:hasPurpose "X" ; ←- can't do purpose of purpose
    dpv:hasContext "X";
    dpv:hasRule "X";
    dpv:hasDocumentation "X" .

harsh: and 2) when we have parent as dpv:Process

:X a aiact:IntendedPurpose ;  # subclass of dpv:Process
    skos:broader ex:ProviderIntendedPurpose ;
    dpv:hasPurpose "X" ;
    dpv:hasContext "X";
    dpv:hasRule "X";
    dpv:hasDocumentation "X" .

harsh: For extending the process or purpose, we can add a usage note as: "This concept is describing a group of concepts similar to how dpv:Process can combine Purpose, Personal Data, Legal Basis, Context, etc. To represent these contextual information for describing the 'intent' of the purpose, additional concepts should be associated with an instance using appropriate relations. For example, an instance of aiact:IntendedPurpose is further described using: dpv:hasDocument to point to the technical documentation or manual."

Next meeting

The next meeting will be in 1 week on WED 17 April 15:00 WEST / 16:00 CEST. Agenda continued from today.