DXWG plenary 2018-05-15

PWinstanley: publicity required,
… davebrowning propose strategy:
… 1. wider geographical reach
… 2. emphasise proposed changes to draw attention to key points

<PWinstanley> https://‌docs.google.com/‌spreadsheets/‌d/‌1_f5CAZv7rgUjJH5YXkmD6w5xS6GX5X2AmEp_LMptAfQ/‌edit#gid=0

PWinstanley: look at engagement strategy spreadsheet
… divide and conquer
… PWinstanley has started linking issues to sections, to provide more narrative
… all participants should blog/post/tweet/share with lists to get widest coverage

PWinstanley: will circulate to ICEGOV participants

<PWinstanley> SimonCox: PWinstanley said he'd started creating links between issues and sections

<PWinstanley> * axiomatisation issues in revision Issue 110 The axiomatization of DCAT 2014 [section 6.1] Issue 119 The axiomatization of dcat

<PWinstanley> Issue 119 The axiomatization of dcat:themeTaxonomy [section 6.3.9]

PWinstanley: we have issues and links within document, e.g. axiomatization mentioned in section 6.1, 6.3.9 but not joined up, will be easier to canvas if we have little checklists
… need to develop message to focus people's feedback:
… e.g. do you agree with X?, could there be an improvement with Y,? etc
… complex document, different audiences will have different foci

alejandra: changes until now are not large, but many potential changes flagged
… at this point we want to publicise links from DCAT issues to UCR document
… though UCR is also complex! What is audience? Who do we expect to be engaged?
… q+ to clarify what is preferred feedback route?

PWinstanley: "DCAT is ideal for government data" needs to be generalized

Jaroslav_Pullmann: later changes about Services, Distribution are not in FPWD
… should we also point to subsequent direction around catalof scope?

note that current throughts, as discussed in F2F3, can be seen here https://‌rawgit.com/‌w3c/‌dxwg/‌dcat-service-simon/‌dcat/‌index.html

See figure 1. https://‌rawgit.com/‌w3c/‌dxwg/‌dcat-service-simon/‌dcat/‌index.html#vocabulary-overview

<Zakim> SimonCox, you wanted to clarify what is preferred feedback route?

Jaroslav_Pullmann: need to emphasize Github issues

PWinstanley: different routes for feedback:
… 1. email list - public-dxwg, and comments-dxwg
… 2. but also request responses into Github issues!

<alejandra> There is this list: public-dxwg-comments@w3.org

<alejandra> it was used for the UCR document when we asked for feedback

PWinstanley: 3. can also respond through their DXWG member

AndreaPerego: since we must respond to all comments, we need to keep track of them

PWinstanley: use of Github issues is unusually large, so the public comments are not separated out so clearly.
… keeping authoritative public record not so easy :-( - or rather, it is more scattered
… important to keep evidence of responses, on spreadsheet provided by davebrowning

Jaroslav_Pullmann: is there agreed text?

PWinstanley: suggest tailoring message for different audiences
… particularly for personalised audiences

Jaroslav_Pullmann: but we need to not miss important points?

Action: pw to draft skeleton messages

<trackbot> Created ACTION-116 - Draft skeleton messages [on Peter Winstanley - due 2018-05-22].

report on f2f3

<PWinstanley> https://‌lists.w3.org/‌Archives/‌Public/‌public-dxwg-wg/‌2018May/‌0139.html

PWinstanley: kcoyle posted consolidated list of points and agreements from f2f3
… we are beginning to create skeleton document for profile guidance

<PWinstanley> https://‌docs.google.com/‌document/‌d/‌15OfNXU9AJ-cZysc7uYP-Gks5dDa8n2B5IN6rWa3kRpo/‌edit#heading=h.7qilxn1v1shj

PWinstanley: which was main focus of f2f3
… much discussion on profiledesc vocabulary - does the group grok this?
… profiledesc is _not_ DCAT specific, so does it belong in profile guidance document?
… plan is to discuss profiledesc at meeting on 2018-05-29, so everyone needs to be up to speed with profiledesc proposal so it can be discussed in plenary

<AndreaPerego> +1 from me

<Jaroslav_Pullmann> +1

<alejandra> +1

<adamsisco> +1

<PWinstanley> +1

https://‌github.com/‌w3c/‌dxwg/‌tree/‌gh-pages/‌profiledesc

organization of profile guidance team

PWinstanley: team = RObAtkinson, kcoyle, Antoine Isaac
… is this OK?

<AndreaPerego> +1

<PWinstanley> +1

<adamsisco> +1

<alejandra> +1

SimonCox: does this include anyone who has worked on published DCAT application-profiles?
… validation of profiles guidance needs to be consistent with existing known profiles?

<AndreaPerego> I would be happy to contribute.

PWinstanley: their input can be in group or reviewing outputs adfterwards

Jaroslav_Pullmann: also need Lars and Ruben who are looking at profile negotiation aspect

PWinstanley: these are not exclusive groups. What we are discussing is who *drives* the profile guidance issue, and then verifies that it meets plenary requirements
… AndreaPerego will contribute, Lars will contribute, just not *driving* the topic

rrsagent: draft minutes v2
… have been talking with Ruben, will he be able to put time in?
… goal at the moment is to form team who will ensure that progress is made

technical requirement for profile negotiation is simple: that a Profile has an IRI! (says lLars)

s/ILars/Lars/

<PWinstanley> https://‌www.w3.org/‌2017/‌dxwg/‌track/‌actions/‌open

open actions

action #7 alejandra: to create a release for last commit for FPWD

<trackbot> Error finding '#7'. You can review and register nicknames at <https://‌www.w3.org/‌2017/‌dxwg/‌track/‌users>.

issues tagged for Andrea to stay open

Jaroslav_Pullmann: unclear how to move new UCs from Github into UCR document
… do editing in GH, branch?
… discuss with kcoyla
… need to check if GH issues tagged 'Requirement' are not orphaned from logged UCs

Times up!

RRSAgent: generate minutes v2

next meeting 2018-05-22 to be chaired by SimonCox

<AndreaPerego> Thanks, bye bye

RRSAgent: generate minutes v2

<PWinstanley> bye

<Jaroslav_Pullmann> bye!

– DRAFT –
DXWG plenary 2018-05-15

15 May 2018

Meeting Minutes

review agenda

approve minutes from last meeting

approve minutes from f2f3

DCAT FPWD

report on f2f3

organization of profile guidance team

open actions

Summary of Action Items

Summary of Resolutions

Diagnostics