- From: Rob Atkinson <rob@metalinkage.com.au>
- Date: Mon, 12 Jun 2017 11:33:12 +0000
- To: kcoyle@kcoyle.net, public-dxwg-wg@w3.org
- Message-ID: <CACfF9Ly8J5oMBADKYzBNri4vWVCF8aJCB+MY4mQGfYVRe=keVw@mail.gmail.com>
I can see a bit of an impedance mismatch in the process here - two valid ways of simplifying the landscape that are perhaps incompatible, signing off of items quickly and efficiently vs. reducing the number of items by analysis and design. In AGILE methodology, its considered good to address the biggest design risks early. I think DCAT 1.1 scope is the elephant in the room here Is DCAT in need of fixes, additional functional scope, or evolving into a more extensible model? >From what I can see, probably all three - but making sure you know how to handle the extensibility of the scope elegantly will allow us to more easily triage for example - from last weeks discussion, versioning is a sufficiently complex domain there needs to be an extension mechanism for domain specific versioning models. But we also probably want in built support for a very simple versioning semantics. So we could perhaps scope DCAT 1.1 to support a single trivial versioning and a canonical way to specify an ObjectProperty with more detailed version model - and a way to declare what version model is being used. One could postulate a profile of DCAT with version provenance etc, using PROV-O or something. Such a profile would be additive with other profiles (i.e. DCAT instances may conform to multiple DCAT profiles). This proto-solution is not necessarily perfect - by I suggest that a Use Case around DCAT profile management is the most critical to get agreed - because we can then triage all the other Use Cases against whether they extend this or require DCAT 1.1 core changes. Accordingly, from a design perspective i think we should try to distill ID26 and ID30 into a coherent Use Case around using DCAT to identify relevant DCAT profiles with extensions to cover specific topics. We can then cast versioning, services, data structure, content description and most of the critical, but complex problems, as sub Use Cases, and simplify DCAT 1.1 requirements to extension points and identification of the profile used. Rob On Sat, 10 Jun 2017 at 03:11 Karen Coyle <kcoyle@kcoyle.net> wrote: > Andrea, thank you. I think it might be overwhelming to consider them all > at the meeting, but if it turns out in our discussion that we can't > discuss them individually we can set aside some time at a future meeting > to look at them as a group. Perhaps you can speak to any dependencies > they have when we have our discussion. > > kc > > On 6/8/17 1:31 AM, andrea.perego@ec.europa.eu wrote: > > Dear Karen, > > > > This is just to point out use cases somehow related to the ones you > propose, that may then be discussed together during the call - also for > grouping (and, possibly, merging) purposes. > > > > > > 1. ID6 - DCAT Distribution to describe web services > > > > > https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#DCAT_Distribution_to_describe_web_services > > > > Related use cases: > > > > ID18: Modeling service-based data access > > > > > https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Modeling_service-based_data_access > > > > ID21: Machine actionable link for a mapping client > > > > > https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Machine_actionable_link_for_a_mapping_client > > > > ID22: Template link in metadata > > > > > https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Template_link_in_metadata > > > > > > 2. ID13 - Modeling agent roles > > > > > https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Modeling_agent_roles > > > > This can be actually related to ID31 - depending on whether the funding > source is denoted (a) by the organisation or (b) by the project providing > the funding. > > > > > > 3. ID31 - Modeling funding sources > > > > > https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Modeling_funding_sources > > > > Related use cases: > > > > ID10: Requirements for data citation > > > > > https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Requirements_for_data_citation > > > > > > Cheers, > > > > Andrea > > > > ---- > > Andrea Perego, Ph.D. > > Scientific / Technical Project Officer > > European Commission DG JRC > > Directorate B - Growth and Innovation > > Unit B6 - Digital Economy > > Via E. Fermi, 2749 - TP 262 > > 21027 Ispra VA, Italy > > > > https://ec.europa.eu/jrc/ > > > > ---- > > The views expressed are purely those of the writer and may > > not in any circumstances be regarded as stating an official > > position of the European Commission. > > > > > >> -----Original Message----- > >> From: Karen Coyle [mailto:kcoyle@kcoyle.net] > >> Sent: Wednesday, June 07, 2017 10:00 PM > >> To: public-dxwg-wg@w3.org > >> Subject: Use cases for June 12 discussion > >> > >> At our last meeting we had an obvious use case that we could discuss and > >> vote on regarding versioning. We need 3-4 other use cases to focus on > >> for the next meeting. We need to dispose of some use cases at each > >> meeting. I am currently tending to prioritize the use cases pertaining > >> specifically to DCAT 1.1 as that is likely to be our first deliverable. > >> In looking at the use cases I see these that appear to be good > >> candidates for our next meeting: > >> > >> ID6 - DCAT Distribution to describe web services > >> > >> https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#DCAT_Distr > >> ibution_to_describe_web_services > >> > >> ID13 - Modeling agent roles > >> > >> https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Modeling_ > >> agent_roles > >> > >> ID31 - Modeling funding sources > >> > >> https://www.w3.org/2017/dxwg/wiki/Use_Case_Working_Space#Modeling_ > >> funding_sources > >> > >> I welcome any suggestions or substitutions to this list, especially if > >> the UCR group has done any thinking on re-organization that would change > >> the priorities. Meanwhile, I will put these tentatively on the agenda. > >> > >> kc > >> for team DXWG > >> -- > >> Karen Coyle > >> kcoyle@kcoyle.net http://kcoyle.net > >> m: 1-510-435-8234 (Signal) > >> skype: kcoylenet/+1-510-984-3600 <+1%20510-984-3600> > > > > -- > Karen Coyle > kcoyle@kcoyle.net http://kcoyle.net > m: 1-510-435-8234 (Signal) > skype: kcoylenet/+1-510-984-3600 <+1%20510-984-3600> > >
Received on Monday, 12 June 2017 11:34:01 UTC