RE: DCAT Sprint - Tuesday 5th February 21:00 UTC - feature: dcat:distibution.

Thanks Alejandra.

 

Could we work with a set of proposed resolutions and discuss those?

 

My proposals would be – but feel free to shoot them down:

 

* https://github.com/w3c/dxwg/issues/267: model this as a Service, not as a Distribution.
* https://github.com/w3c/dxwg/issues/259 and https://github.com/w3c/dxwg/issues/54; add new properties dcat:compressionMediaType, dcat:compressionFormat and use dcat:mediaType and dct:format for the most relevant ‘inner format’. (But note backwards compatibility issues!)
* https://github.com/w3c/dxwg/issues/482: use dcat:accessURL or dcat:landingPage

 

A set of such proposed resolutions might make the discussion easier.

 

Makx.

 

 

From: Alejandra Gonzalez-Beltran <alejandra.gonzalez.beltran@gmail.com> 
Sent: 31 January 2019 14:02
To: Makx Dekkers <mail@makxdekkers.com>
Cc: Peter.Winstanley@gov.scot; david.browning@refinitiv.com; public-dxwg-wg@w3.org
Subject: Re: DCAT Sprint - Tuesday 5th February 21:00 UTC - feature: dcat:distibution.

 

Indeed the objective is to reach consensus on how to resolve the issues! 

 

I created a project with the subset of issues around distribution packaging and files composition that you suggested:

 

https://github.com/w3c/dxwg/projects/6

 

On Thu, 31 Jan 2019 at 11:22, Makx Dekkers <mail@makxdekkers.com <mailto:mail@makxdekkers.com> > wrote:

Alejandra,

 

I had understood that the two-hour sprint was to actually discuss and agree solutions to issues, not to plan work to be done after the meeting. Of course the discussion may lead to agreement that ‘more work needs to be done’ after the meeting, but I would hope that we can reach consensus on resolutions. If we can’t, I don’t really see the point of sprinting.

 

Makx.

 

 

 

 

From: Alejandra Gonzalez-Beltran < <mailto:alejandra.gonzalez.beltran@gmail.com> alejandra.gonzalez.beltran@gmail.com> 
Sent: 31 January 2019 12:09
To:  <mailto:Peter.Winstanley@gov.scot> Peter.Winstanley@gov.scot
Cc:  <mailto:mail@makxdekkers.com> mail@makxdekkers.com;  <mailto:david.browning@refinitiv.com> david.browning@refinitiv.com;  <mailto:public-dxwg-wg@w3.org> public-dxwg-wg@w3.org
Subject: Re: DCAT Sprint - Tuesday 5th February 21:00 UTC - feature: dcat:distibution.

 

We decided that the first topic is Distributions, and indeed, the intention is not to resolve all the issues in two hours but to have an overall view of what are the requirements for Distributions and decide on the meeting what we should tackle first and how to distribute the load among us if possible.

 

As Peter suggests, we can also discuss what to prioritise in advance to the meeting.

 

Thanks,

 

Alejandra

 

On Thu, 31 Jan 2019 at 10:51, <Peter.Winstanley@gov.scot <mailto:Peter.Winstanley@gov.scot> > wrote:

Agreed.
What issues from the list Dave provided do you think should be in the first meeting?  I think it makes sense to pick ones where we are most likely to succeed in making progress.

-----Original Message-----
From: Makx Dekkers <mail@makxdekkers.com <mailto:mail@makxdekkers.com> > 
Sent: 31 January 2019 10:48
To: Winstanley FP (Peter) <Peter.Winstanley@gov.scot <mailto:Peter.Winstanley@gov.scot> >; david.browning@refinitiv.com <mailto:david.browning@refinitiv.com> ; public-dxwg-wg@w3.org <mailto:public-dxwg-wg@w3.org> 
Subject: RE: DCAT Sprint - Tuesday 5th February 21:00 UTC - feature: dcat:distibution.

Hi Peter,

I am happy to follow your lead on this. It's just that I think we can't possibly solve 15 issues in two hours, so pre-selecting issues based on a combination of importance (high) and complexity (not too high) would indeed make sense.

Makx.

-----Original Message-----
From: Peter.Winstanley@gov.scot <mailto:Peter.Winstanley@gov.scot>  <Peter.Winstanley@gov.scot <mailto:Peter.Winstanley@gov.scot> >
Sent: 31 January 2019 11:24
To: mail@makxdekkers.com <mailto:mail@makxdekkers.com> ; david.browning@refinitiv.com <mailto:david.browning@refinitiv.com> ; public-dxwg-wg@w3.org <mailto:public-dxwg-wg@w3.org> 
Subject: RE: DCAT Sprint - Tuesday 5th February 21:00 UTC - feature: dcat:distibution.

Hi Makx
We are being a bit loose with the terminology here, but the gist is that we need to have something equivalent to the face to face where we do collaborative work on some items, but we don't have time for the face to face so are doing the virtualised next best thing.

If we have a longer meeting, use some collaborative workspace that allows us all to contribute in parallel (e.g. Google doc) then we should be able to make more progress in a short time (like a Kaizen Blitz if you want another model) 

You're right that there needs to be some triage and focus, and the initial list that Dave has provided is just the long list, from which we can decide on a short list of things to deal with in any one meeting.

I foresee that if the first one is productive that we will have a few others.

Hope this clarifies

Cheers

Peter

-----Original Message-----
From: Makx Dekkers <mail@makxdekkers.com <mailto:mail@makxdekkers.com> >
Sent: 31 January 2019 10:19
To: david.browning@refinitiv.com <mailto:david.browning@refinitiv.com> ; public-dxwg-wg@w3.org <mailto:public-dxwg-wg@w3.org> 
Subject: RE: DCAT Sprint - Tuesday 5th February 21:00 UTC - feature: dcat:distibution.

David, all,

Can you please outline how this 'sprint' works? I have never been involved in sprints so I looked for a definition and found one at https://en.wikipedia.org/wiki/Scrum_(software_development)#Sprint. That says it is usually for teams of three to nine people (so that works for us) but also that a sprint commonly takes two weeks. Your message seems to imply that the two-hour call *is* the sprint.

Other than that, I am not quite sure how we are going to handle 15 open issues in a two-hour call -- it means we'll have an average of eight minutes per issue which sounds unrealistic. It may be true that some (e.g.
https://github.com/w3c/dxwg/issues/125) will take less time but there are others that have seen a lot of discussion already and may take more that two hours each. 

Should we maybe select two or three issues that are the most important and that can be decided in less than an hour?

Makx.


-----Original Message-----
From: david.browning@refinitiv.com <mailto:david.browning@refinitiv.com>  <david.browning@refinitiv.com <mailto:david.browning@refinitiv.com> >
Sent: 31 January 2019 10:20
To: public-dxwg-wg@w3.org <mailto:public-dxwg-wg@w3.org> 
Subject: DCAT Sprint - Tuesday 5th February 21:00 UTC - feature:
dcat:distibution.

As discussed via doodle poll/DCAT subgroup meeting, the first DCAT sprint will take place next Tuesday 5th February 2100 UTC till 23:00 UTC.  This will be a working meeting looking at the outstanding issues (and any associated concerns raised in external or internal feedback) and will aim to pull together appropriate conclusions and text to be contributed to the working draft.  The current idea will be to work around a google doc that should allow effective collaboration from all participants, though other ideas are welcome.

The webex details for the meeting have already been sent out to the WG mail (https://lists.w3.org/Archives/Public/public-dxwg-wg/2019Jan/0617.html ).

The remaining open issues in github are listed at https://github.com/w3c/dxwg/issues?q=is%3Aissue+label%3Adcat%3ADistribution+ <https://github.com/w3c/dxwg/issues?q=is%3Aissue+label%3Adcat%3ADistribution+is%3Aopen> 
is%3Aopen.  If anyone (potential attendee or not) wants to add more please make sure they are tagged with dcat:distribution.

There are obvious topics around "informationally equivalent", packages/zips, positioning of distributions with respect to services as well as others that don't necessarily stand out from the detail - the meeting can decide how we work through this, what the priority is, what will benefit from discussion.

Note:  The regular DCAT meeting will still be held on Wednesday 6th February at 21:00 UTC for 1 hr as usual, to cover broader progress discussions, feedback handling etc

David Browning

________________________________

This e-mail is for the sole use of the intended recipient and contains information that may be privileged and/or confidential. If you are not an intended recipient, please notify the sender by return e-mail and delete this e-mail and any attachments. Certain required legal entity disclosures can be accessed on our website.<https://www.refinitiv.com/>



______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________

**********************************************************************
This e-mail (and any files or other attachments transmitted with it) is intended solely for the attention of the addressee(s). Unauthorised use, disclosure, storage, copying or distribution of any part of this e-mail is not permitted. If you are not the intended recipient please destroy the email, remove any copies from your system and inform the sender immediately by return.

Communications with the Scottish Government may be monitored or recorded in order to secure the effective operation of the system and for other lawful purposes. The views or opinions contained within this e-mail may not necessarily reflect those of the Scottish Government.


Tha am post-d seo (agus faidhle neo ceanglan còmhla ris) dhan neach neo luchd-ainmichte a-mhàin. Chan eil e ceadaichte a chleachdadh ann an dòigh sam bith, a’ toirt a-steach còraichean, foillseachadh neo sgaoileadh, gun chead. Ma ’s e is gun d’fhuair sibh seo gun fhiosd’, bu choir cur às dhan phost-d agus lethbhreac sam bith air an t-siostam agaibh agus fios a leigeil chun neach a sgaoil am post-d gun dàil.

Dh’fhaodadh gum bi teachdaireachd sam bith bho Riaghaltas na h-Alba air a chlàradh neo air a sgrùdadh airson dearbhadh gu bheil an siostam ag obair gu h-èifeachdach neo airson adhbhar laghail eile. Dh’fhaodadh nach  eil beachdan anns a’ phost-d seo co-ionann ri beachdan Riaghaltas na h-Alba. 
**********************************************************************


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________