<axelpolleres> James, are you new in the group?
<axelpolleres> if so, do you know how to join the call?
<axelpolleres> https://lists.w3.org/Archives/Public/public-dpvcg/2019Sep/0000.html
<scribe> scribe: harsh
<axelpolleres> scribe: harsh
axelpolleres: last calls was scheduled for 6th Aug, but no one attended, so there were no minutes recorded
Last meeting call was 18th June
<axelpolleres> PROPOSED: approve minutes from https://www.w3.org/2019/06/18-dpvcg-minutes
+1
<axelpolleres> +1
<axelpolleres> all other questions prior to publication have been resolved per email.
RESOLUTION: approve minutes from https://www.w3.org/2019/06/18-dpvcg-minutes
axelpolleres: progress so far - we advertised the spec via mailing lists, events, etc.
<axelpolleres> did we send the spec for feedback to the mydata last?
elmar: (going to My Data)
<axelpolleres> ACTION: elmar to advertise DPVCG at mydata and send it to the mydata global list.
<trackbot> Created ACTION-123 - Advertise dpvcg at mydata and send it to the mydata global list. [on Elmar Kiesling - due 2019-09-10].
elmar: My Data is 25-27 September
in Helsinki
... (discussion sessions in My Data and which would be suitable
for presenting DPV)
<axelpolleres> Elmar: involved in Mydata in two sessions. will contact Sille and others from Mydata.
<elmar> harsh has some slides on the vocabulary that he can share
axelpolleres: can we reuse slides for ODBASE ?
<elmar> elmar to Look for an open space in the myData program to advertise the vocabulary
<axelpolleres> axel: maybe check whether they have an openspace agein?
<elmar> ACTION: elmar to Look for an open space in the myData program to advertise the vocabulary
<trackbot> Created ACTION-124 - Look for an open space in the mydata program to advertise the vocabulary [on Elmar Kiesling - due 2019-09-10].
fajar: we can also present something at SEMANTiCS
<axelpolleres> Harsh and Fajar will be going to SEMANTiCS...
axelpolleres: who is going? (ans: Sabrina, Fajar, Harsh)
<axelpolleres> ACTION: Harsh/Fajar to advertise at SEMANTiCS.
<trackbot> Error finding 'Harsh/Fajar'. You can review and register nicknames at <https://www.w3.org/community/dpvcg/track/users>.
<elmar> ACTION: fajar to advertise at SEMANTiCS.
<trackbot> Created ACTION-125 - Advertise at semantics. [on Fajar Ekaputra - due 2019-09-10].
<axelpolleres> any other channels?
fajar: semantic web mailing list? (axel already announced it, not much response)
<axelpolleres> Axel snet an [ANN] mail to w3c sw-list
<axelpolleres> another mail would only make sense on the next version.
<axelpolleres> Bert, are you there?
<elmar> https://www.w3.org/community/dpvcg/
elmar: update details on homepage
<axelpolleres> ACTION: Axel ask bert to update the CGWebpage to advertise the drafts more prominently.
<trackbot> Created ACTION-126 - Ask bert to update the cgwebpage to advertise the drafts more prominently. [on Axel Polleres - due 2019-09-10].
axelpolleres: should we get back to regular meeting calls on biweekly schedule?
<Bert> Hi axelpolleres. Yes, I'm here, but I need to finish some important work. :-( Sorry, should have sent some email.
<axelpolleres> PROPOSED: get back to usual biweekly telco schedule until end of the year, or until we're finished, what happens earlier.
+1
<axelpolleres> +1
(everyeone agrees on call)
<Fajar> +1
<elmar> +1
RESOLUTION: get back to usual biweekly telco schedule until end of the year, or until we're finished, what happens earlier.
<axelpolleres> --> this means we stick for now with Tue 16:00 central Europe time...
<axelpolleres> harsh: none of the feedback has been incorporated yet.
<axelpolleres> axel: what do we have?
1) Martin's reviews on the paper, which can be incorporated into the spec
<axelpolleres> - martin's review on the paper/spec
2) diff between paper and text in spec to see what has changed, and update accordingly
<axelpolleres> - paragraph additional text from the paper at ODBASE that might also help the spec
We also had this feedback regarding correcting datatypes in spec - https://lists.w3.org/Archives/Public/public-dpvcg/2019Jul/0029.html
<axelpolleres> ACTION: Axel to ask simon steyskal are your comments still open on the spec
<trackbot> Created ACTION-127 - Ask simon steyskal are your comments still open on the spec [on Axel Polleres - due 2019-09-10].
axelpolleres: we also had some comments from Simon in July
fajar: keep an online list to collect all inputs to see whether they have been addressed
<axelpolleres> ACTION: fajar, will try to recollect all the inputs and (not-)addressed issues in the spec.
<trackbot> Error finding 'fajar,'. You can review and register nicknames at <https://www.w3.org/community/dpvcg/track/users>.
<elmar> ACTION: fajar will try to recollect all the inputs and (not-)addressed issues in the spec.
<trackbot> Created ACTION-128 - Will try to recollect all the inputs and (not-)addressed issues in the spec. [on Fajar Ekaputra - due 2019-09-10].
<axelpolleres> Axel: use the issues tracker on W3C.
axelpolleres: for each set of open comments or feedback, we should create an issue and track progress using that (W3C tracker)
<elmar> Should still use the issue tracker, but the Google Sheet would provide an overview
<axelpolleres> fajar will prepare the open things in a way that we can discuss them and discuss it with Harsh at SEMANTiCS... if HArsh and Fajar can send around a list at semantics to send around, we havee another week to have replies coming in on the mailinglist.
<axelpolleres> optimistically, by 1 but next telco (i.e. in a month) we can vote for resolutions of all open issues.
<axelpolleres> unless new issues/comments we could then have them incorporated, start internal reviewing mid october
<axelpolleres> internal reviews by end october in, incorporated/voted to publish by mid Nov?
+1
<Fajar> +1
<axelpolleres> goal publish before end November.
<elmar> +1
<Bud_> +1
<axelpolleres> ACTION: Axel to check in the next telcos, whethrer we're on track for that timplan.
<trackbot> Created ACTION-129 - Check in the next telcos, whethrer we're on track for that timplan. [on Axel Polleres - due 2019-09-10].
axelpolleres: for use-cases and
examples, we could use an existing use-case from a project and
document dpv application to that
... anyone willing to document one of the SPECIAL use-cases
using the DPV?
elmar: anyone still working with the project partners?
bud: is this an use-case that
covers everything or only one aspect e.g. legal base
... I can work with Eva to have an use-case on a limited
scenario
<axelpolleres> ACTION: bud to discuss with eva to start a use case document?
<trackbot> Created ACTION-130 - Discuss with eva to start a use case document? [on Bud P. Bruegger - due 2019-09-10].
<axelpolleres> would particularly involve picking a use case.
<axelpolleres> topicc: action list
<axelpolleres> https://www.w3.org/community/dpvcg/track/actions/open
<axelpolleres> CLOSE ACTION-116
<trackbot> Closed ACTION-116.
<axelpolleres> CLOSE ACTION-118
<trackbot> Closed ACTION-118.
<axelpolleres> CLOSE ACTION-119
<trackbot> Closed ACTION-119.
<Fajar> Link to the compiled issues: https://docs.google.com/spreadsheets/d/1fRtIy1Cmh6RpWrCB7Cs6XZn504pJqIMAeJ2BhoZsdvs/edit?usp=sharing
harsh: to talk to Mark about ACTION-87 and ACTION-114 regarding relevance, progress, or whether they should be closed
<axelpolleres> Axel: Ithink ACTION-114 and ACTION-87 were referring to Mark's reservation on relying to NACE alone in the spec. HE should be asked whether he wants to further address that before we close them.
<axelpolleres> close ACTION-81
<trackbot> Closed ACTION-81.
ACTION-36 to leave open until close of ACTION-130 as it relates to use-case
<axelpolleres> leave open closing of ACTION-36 until closing of ACTION-130
<axelpolleres> ACTION-36: leave open closing of ACTION-36 until closing of ACTION-130
<trackbot> Notes added to ACTION-36 Add points 1.-6. from https://lists.w3.org/archives/public/public-dpvcg/2018nov/0000.html to https://www.w3.org/community/dpvcg/wiki/special/proximus_use_case.
ACTION-87: talk to Mark about regarding relevance, progress, or whether they should be closed
<trackbot> Notes added to ACTION-87 Make a proposal alternatively use gics instead of nace..
ACTION-114: talk to Mark about regarding relevance, progress, or whether they should be closed
<trackbot> Notes added to ACTION-114 Make a concrete proposal along specification of data controller categories by sector in the spec..
<axelpolleres> ACTION-11: Axel will close it after having talked to Simon.
<trackbot> Notes added to ACTION-11 Reach out to industrial data spaces project (germany) and another austrian big data project (dma)..
nothing else (on call)
<axelpolleres> adjourned and talk in two weeks ... seems you couldn't hear me anymore, I can hear you
<axelpolleres> THanks!
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) WARNING: Replacing previous Present list. (Old list: elmar, harsh, bud) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ fajar Present: fajar WARNING: Fewer than 3 people found for Present list! Found Scribe: harsh Found Scribe: harsh Inferring ScribeNick: harsh WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting Agenda: https://lists.w3.org/Archives/Public/public-dpvcg/2019Sep/0000.html WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: ask axel bert bud elmar fajar harsh try will WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]