<SimonCox> rrsagent: draft minutes
<SimonCox> agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2018.06.14
<scribe> scribe: Jaroslav_Pullmann
<SimonCox> scribe: Jaroslav Pullmann
<SimonCox> scribenick: Jaroslav_Pullmann
<alejandra> meeting: DXWG DCAT subgroup teleconference 14 June 2018 8:30 UTC
<alejandra> +q
UNKNOWN_SPEAKER: are there minutes we shoul agree on?
<SimonCox> agenda confirmed
<SimonCox> – https://www.w3.org/2018/06/07-dxwgdcat-minutes
<SimonCox> +1
<riccardoAlbertoni> +1
+0 (present only via IRC)
<alejandra> 0 (was absent, only checking irc)
RESOLUTION: minutes approved
<riccardoAlbertoni> +q
<riccardoAlbertoni> https://rawgit.com/w3c/dxwg/dcatQualityRelatedInformationIssue57Riccardo/dcat/index.html#quality-information
<SimonCox> see https://rawgit.com/w3c/dxwg/dcatQualityRelatedInformationIssue57Riccardo/dcat/index.html#quality-information
riccardoAlbertoni: added small
chnages (see link)
... no assumption about the placement of the quality node in
the architecture
... feedback from Antoine suggesting re-naming of entities
(applied)
... adressing issue https://github.com/w3c/dxwg/issues/57
<Zakim> SimonCox, you wanted to ask about normative/non-normative status
riccardoAlbertoni: status (normative or not) to be discussed
<alejandra> +q
<SimonCox> ah - DQV is not a W3C recommendation, only a Note!
riccardoAlbertoni: at the moment
a guideline
... should not be normative (at moment)
<SimonCox> Will DQV become a Rec at some point?
<riccardoAlbertoni> +q
alejandra: what is the expected evolution and relation to other issues?
<SimonCox> alejandra: does this proposal resolve both #57 and #58?
<alejandra> is DQV going to become a recommendation? what is the schedule?
riccardoAlbertoni: DQV produced
by Data on the Web Best Practices Group as note
... no plans (those times) to become a recommendation
<SimonCox> alejandra: doesn't 'we go with DQV' resolve #58?
riccardoAlbertoni: ... Andrea is
aware work done on DQV
... DQV is capable of covering the requirements so far (e.g.
quality testing)
... we'll need further discussions to see whether all the req.
are covered
... issue 57 is being closed by current proposal
<alejandra> all the quality related issues are these: https://github.com/w3c/dxwg/labels/quality
riccardoAlbertoni: issue https://github.com/w3c/dxwg/issues/58 is going to be tackled next
<SimonCox> Proposed: accept https://github.com/w3c/dxwg/pull/245'Providing quality information` as satisfying https://github.com/w3c/dxwg/issues/57
<riccardoAlbertoni> +1
<SimonCox> +1
<alejandra> +1
+1
RESOLUTION: accept https://github.com/w3c/dxwg/pull/245'Providing quality information` as satisfying https://github.com/w3c/dxwg/issues/57
<SimonCox> proposed: section https://github.com/w3c/dxwg/pull/245 is non-normative because DQV is not a standard or recommendation
<SimonCox> +1
<alejandra> should this be clarified on the document?
riccardoAlbertoni: usage of DQV (note) should be clarified in DCAT (recommendation)
<alejandra> I see mentions that DQV is not normative ('DQV does not define a normative list of quality dimensions.')
<SimonCox> Friendly amendment - explain why it is non-normative in a Note in the document
<alejandra> but I think it would be good to clarify the reason why DQV is not normative for DCAT
<SimonCox> ACTION: riccardoAlbertoni to add note about status of DQV
<trackbot> Sorry, but no Tracker is associated with this channel.
SimonCox: add section on stating being non-normative because a note
<alejandra> +q
<SimonCox> another section (e.g. 7.2) on service quality
<SimonCox> ??
<riccardoAlbertoni> +q
<SimonCox> responding to https://github.com/w3c/dxwg/issues/252
riccardoAlbertoni: DQV was mainly
about datasets and distribution
... now moving towards services
... documenting Quality of Service
<SimonCox> when 7.2 has been written we can close #252, and then #58
<SimonCox> downloadURL https://github.com/w3c/dxwg/issues/126 accessURL https://github.com/w3c/dxwg/issues/124 types and endpointURL https://github.com/w3c/dxwg/issues/249
SimonCox: there was a consistency
issue (in naming)
... for reasons of alignment endpointURL was proposed for
service-based access
... no need to change the axiomatization of the xURLs
<alejandra> +q
alejandra: agreed with your view,
update the scope note
... discuss withh Andrea the reasons for modelling as object
property
... ... referring to issue #249
... remain compatible with the xURL pattern
<SimonCox> the current state of discussion is https://github.com/w3c/dxwg/issues/249#issuecomment-396748878
<SimonCox> Proposed: no change to domain/range axiomatization of downloadURL and accessURL; endpointURL to be axiomatized similarly; add property-chain axiom relating accessURL to endpointURL; improve usage notes related to all the xxxURL properties
<SimonCox> this would allow us to close #126, #124, #249
<SimonCox> +1
<riccardoAlbertoni> +1
<alejandra> +1
+1
RESOLUTION: no change to domain/range axiomatization of downloadURL and accessURL; endpointURL to be axiomatized similarly; add property-chain axiom relating accessURL to endpointURL; improve usage notes related to all the xxxURL properties - this would allow us to close #126, #124, #249
<SimonCox> https://github.com/w3c/dxwg/issues/253
<SimonCox> only very small change - dcat:distribution rdfs:subPropertyOf dct:relation .
<alejandra> +q
alejandra: this use case is
important, often seen
... dct:relation is may be too generic - how does it play with
dcat:distribution?
... people may not use distribution any more
<SimonCox> Maybe too much risk of discouraging use of dcat:distribution?? More thought needed.
<SimonCox> Also: need to constrain the range of dct:relation in context of dcat:Dataset
SimonCox: summarizing the essence
of the proposal
... introducing a generic super property will prevent people to
wrongly describe relations of files, when unknown
<SimonCox> https://github.com/w3c/dxwg/issues/61
<alejandra> https://github.com/w3c/dxwg/wiki/Data-Citation
alejandra: solution on the way,
started a wiki page
... considering mappings between Data-cite and DCAT
... work in progress
<SimonCox> work in progress, watch this space
SimonCox: will miss next
call,
... Dave Browning will chair
<riccardoAlbertoni> thanks for the interesting discussion Bye
bye & thanks!
<SimonCox> rrsagent: draft minutes v2
<alejandra> thanks, and bye!
<SimonCox> rrsagent: create minutes
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/evoluation/evolution/ Succeeded: s/doen/done/ Succeeded: s/no/now/ Succeeded: s/writeen/written/ Succeeded: s/wit/with/ Succeeded: s/refering/referring/ Succeeded: s/wit/with/ Succeeded: s/riccardoAlbertoni: DQV was about (static) datasets and distribution/riccardoAlbertoni: DQV was mainly about datasets and distribution/ Succeeded: s/remian/remain/ Succeeded: s/onbe/only/ Succeeded: s/constraint/constrain/ Succeeded: s/Dvae/Dave/ Present: Jaroslav_Pullmann SimonCox riccardoAlbertoni alejandra Regrets: Andrea DaveBrowning PWinstanley Found Scribe: Jaroslav_Pullmann Found Scribe: Jaroslav Pullmann Found ScribeNick: Jaroslav_Pullmann Scribes: Jaroslav_Pullmann, Jaroslav Pullmann Agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2018.06.14 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: riccardoalbertoni 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]