W3C home > Mailing lists > Public > public-dwbp-wg@w3.org > October 2015

Re: a first proposal for Issue-205

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Wed, 28 Oct 2015 13:57:50 +0100
Message-ID: <5630C64E.7000106@few.vu.nl>
To: <public-dwbp-wg@w3.org>

Thanks a lot, Riccardo!

I'd suggest a small amendment: I we don't need dqv:hasDimension as a subproperty of skos:broader. This would de-facto classify dqv:Metrics as dqv:Concepts. While I'm generally not so fussy about dual-typing things as skos:Concepts and other classes, here I'm not sure this will bring us anything positive.

My take is that using SKOS hierarchies in our context would rather pay off as an option to organize the categories or the dimensions between them.
For example:

ex:linguisticCompleteness skos:broader ex:completeness.

This would bring us quite close to the patter used for motivations by the Web Annotation model [1].
There the SKOS relations hold between (extensions of) motivations. And our own dqv:hasDimension/dqv:hasCategory would have for dqv:Metric a role analogous to that of oa:motivatedBy for oa:Annotation.

This pattern also allow to later reconcile different categories or dimensions coming from different instanciations of DQV. Continuing my toy example:

ex1:linguisticCompleteness skos:closeMatch ex2:languageCoverage

In the end I'm fairly sure following a very similar patter to that of Web Annotation will pay off, as both DUV and DQV are already re-using bits of the Annotation Model. But I don't know precisely when and how :-)

A final comment: the Web Annotation model is still officially a moving target. But they're progressing quite fast, and the Motivation part of the model has been stable for quite a while so I wouldn't refrain from getting inspiration from it. In fact this SKOS-based pattern has been used in many other data models...



[1] http://www.w3.org/TR/annotation-model/#extending-motivations

On 10/27/15 6:28 PM, Riccardo Albertoni wrote:
> Dear all,
> Following the discussion we had  last friday's call concerning issue-205, https://www.w3.org/2013/dwbp/track/issues/205,
> a first   proposal we might discuss  in order to turn  metrics,  dimensions and categories into a skos hierarchy  is the following
> Proposal 1: Let’s define
> -dqv:hasDimension and  dqv:hasCategory as subproperties (rdfs:subPropertyOf)  of skos:broader;
> -dqv:Category,  dqv:Dimension, dqv:Metric  as subclasses of (rdfs:subClassOf) skos:Concept.
> In this way, we have that every  user-defined   category/ dimension/ metric hierarchy  is automatically mapped into a SKOS hierarchy. At the same time,  this proposal  remains “back-compatible” with DAQ,  since we  have  dqv:Category,  dqv:Dimension, dqv:Metric  still mapped into their corresponding   DAQ's metric, dimension, and category.
> What do you think? Does this work? any refinement?
> Cheers,
> Riccardo
> --
> ----------------------------------------------------------------------------
> Riccardo Albertoni
> Istituto per la Matematica Applicata e Tecnologie Informatiche "Enrico Magenes"
> Consiglio Nazionale delle Ricerche
> via de Marini 6 - 16149 GENOVA - ITALIA
> tel. +39-010-6475624 - fax +39-010-6475660
> e-mail: Riccardo.Albertoni@ge.imati.cnr.it <mailto:Riccardo.Albertoni@ge.imati.cnr.it>
> Skype: callto://riccardoalbertoni/
> LinkedIn: http://www.linkedin.com/in/riccardoalbertoni
> www: http://www.ge.imati.cnr.it/Albertoni
> http://purl.oclc.org/NET/riccardoAlbertoni
> FOAF:http://purl.oclc.org/NET/RiccardoAlbertoni/foaf
Received on Wednesday, 28 October 2015 12:58:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 28 October 2015 12:58:28 UTC