Copyright
©
2015
2016
W3C
®
(
MIT
,
ERCIM
,
Keio
,
Beihang
).
W3C
liability
,
trademark
and
document
use
rules
apply.
Datasets
published
on
the
Web
are
accessed
and
experienced
by
consumers
in
a
variety
of
ways,
but
little
information
about
these
experiences
is
typically
conveyed.
Dataset
publishers
many
times
lack
feedback
from
consumers
about
how
datasets
are
used.
Consumers
lack
an
effective
way
to
discuss
experiences
with
fellow
collaborators
and
explore
referencing
material
citing
the
dataset.
Datasets
as
defined
by
DCAT
are
a
collection
of
data,
published
or
curated
by
a
single
agent,
and
available
for
access
or
download
in
one
or
more
formats.
The
Dataset
Usage
Vocabulary
(DUV)
(
DUV
)
is
used
to
describe
consumer
experiences,
citations,
and
feedback
about
the
dataset
from
the
human
perspective.
By specifying a number of foundational concepts used to collect dataset consumer feedback, experiences, and cite references associated with a dataset, APIs can be written to support collaboration across the Web by structurally publishing consumer opinions and experiences, and provide a means for data consumers and producers advertise and search for published open dataset usage.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This
is
a
draft
document
which
may
be
merged
with
the
Data
Quality
Vocabulary
or
remain
second
iteration
of
the
vocabulary,
developed
following
extensive
consultation
among
and
outside
the
working
group
who
now
regard
it
as
a
standalone
document.
Feedback
nearing
completion.
Comment
and
feedback
is
sought
on
before
the
overall
direction
being
taken
as
much
as
next
iteration
which
is
likely
to
be
the
specific
details
of
final
version
for
the
proposed
vocabulary.
foreseeable
future.
This
document
was
published
by
the
Data
on
the
Web
Best
Practices
Working
Group
as
a
First
Public
Working
Draft.If
Draft.
If
you
wish
to
make
comments
regarding
this
document,
please
send
them
to
public-dwbp-comments@w3.org
(
subscribe
,
archives
).
All
comments
are
welcome.
Publication
as
a
First
Public
Working
Draft
does
not
imply
endorsement
by
the
W3C
Membership.
This
is
a
draft
document
and
may
be
updated,
replaced
or
obsoleted
by
other
documents
at
any
time.
It
is
inappropriate
to
cite
this
document
as
other
than
work
in
progress.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy . The group does not expect this document to become a W3C Recommendation. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy .
This
document
is
governed
by
the
1
August
2014
September
2015
W3C
Process
Document
.
This section is non-normative.
This
vocabulary
is
meant
to
fill
a
niche
that
helps
standardize
the
way
Web
published
dataset
usage
be
conveyed
and
shared.
At
this
time
there
is
no
clear
standard
way
to
describe
dataset
usage
on
the
Web.
Without
a
means
to
systematically
describe
dataset
usage,
searching
and
conveying
techniques
are
application
specific
and
discovery
and
collaboration
across
the
Web
is
more
difficult.
This
vocabulary
also
recommends
and
requires
data
publishers
to
provide
a
mechanism
of
receiving
data
usage
information
from
data
consumers
in
the
form
of
feedback,citation
feedback,
citation
and
data
correction.
The
namespace
for
DCAT
DUV
is
.
However,
it
should
be
noted
that
http://www.w3.org/ns/dcat#
http://www.w3.org/ns/duv#
DCAT
DUV
makes
extensive
use
of
terms
from
other
vocabularies,
in
particular
Dublin
Core
.
DCAT
vocabularies.
DUV
itself
defines
a
minimal
set
of
classes
and
properties
of
its
own.
A
full
set
of
namespaces
and
prefixes
used
in
this
document
is
shown
in
the
table
below.
Prefix | Namespace |
---|---|
biro | http://purl.org/spar/biro/ |
cito | http://purl.org/spar/cito/ |
cnt | http://www.w3.org/2011/content |
dcat | http://www.w3.org/ns/dcat# |
dct | http://purl.org/dc/terms/ |
dctype | http://purl.org/dc/dcmitype/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
vann | http://purl.org/vocab/vann# |
xsd | http://www.w3.org/2001/XMLSchema# |
The DUV is intended for data producers and publishers interested in tracking, sharing, and persisting consumer dataset usage. It is also intended for collaborators who require an exchange medium to advertise and interactively convey dataset usage.
The scope of the DUV is defined by the Data on the Web Best Practices (DWBP) Use Case document [ DWBP-UCR ] based on the data usage requirements about datasets. These requirements include: citing data on the Web, tracking the usage of data, sharing feedback and rating data. These requirements were derived from fourteen real world use cases examples provided in the use case document.
The
DUV
is
a
“glue”
vocabulary
reusing
and
extending
existing
vocabulary
classes
and
properties
to
support
citation,
feedback,
and
usage.
This
section
provides
our
rationale
and
approach
for
vocabulary
selection
and
re-use.
reuse.
Core
to
the
dataset
usage
vocabulary
is
the
“dataset”.
The
DUV
uses
the
Data
Catalog
(DCAT)
vocabulary
Vocabulary's
dcat:Dataset
class
and
all
properties
associated
with
the
class.
class
[
VOCAB-DCAT
].
From
a
data
usage
perspective
the
DUV
can
be
considered
an
extension
of
the
dcat:Dataset.
The
Web
Annotation
Vocabulary
[
OA
]
is
used
to
describe
duv:Feedback
as
a
subclass
inheriting
the
behavior
of
oa:Annotation.
A
crucial
part
of
the
Web
Annotation
Model
are
“motivations”
that
describe
the
role
of
particular
Annotation.
Each
duv:Feedback
must
have
at
least
one
oa:motivated_by
property
with
a
relationship
to
an
instance
of
oa:Motivation.
A
subset
of
the
Motivation
instances
are
important
to
describe
feedback
to
data
publishers,
and
blogs
between
dataset
consumers.
In
addition
to
supporting
duv:Feedback
duv:Feedback,
because
the
Web
Annotation
vocabulary
provides
a
generic
way
of
annotating
any
Web
resource,
it
is
recommended
that
Web
Annotation
vocabulary
be
used
to
annotate
the
duv:Dataset
for
uses
beyond
the
scope
of
the
DUV.
DUV
.
The
Provenance
Ontology
(Prov-O)
is
Semantic
Publishing
and
Referencing
[
SPAR
]
Ontologies
provides
a
vocabulary
suite
of
vocabularies
used
by
data
providers
to
pass
details
about
the
data
history
related
entities
to
data
users.
Properties
associated
with
prov:Activity
provide
relationships
(prov:used,
prov:hasGenerated)
from
a
historical
perspective
using
past
tense
forms
of
words
and
phrases.
The
developed
reference
citations,
bibliographic
records,
and
duv:WebThing
reuses
these
properties
by
creating
subProperties
from
Prov-O
to
describe
usage
from
a
present
tense
perspective.
Both
the
publication
process
along
with
other
related
activities.
The
DUV
directly
relies
upon
Citation
Typing
Ontology
(CiTO)
[
CITO
],
the
FRBR-aligned
Bibliographic
Ontology
[
FaBIO
],
and
Dublin
Core
[
DC-TERMS
]
vocabularies
are
used
to
describe
citations
and
references
between
datasets
and
cited
sources.
6.
Examples
This
section
shows
some
examples
to
illustrate
the
application
of
the
Dataset
Usage
Vocabulary.
Example
1
-
Usage:
A
2-D
plot
application
developed
by
Laufer
can
be
used
to
create
temperature
plots
and
consumes
temperature
readings
from
a
dataset
In
addition
to
produce
ontologies
the
plot.
A
data
logger
used
to
provide
temperature
readings
uses
a
configuration
file
research
community
provided
basic
criteria
for
operation
of
the
citing
data
logger.
Example
1
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix duv: <http://www.w3.org/ns/duv#> .
@prefix : <http://example.org#> .
:laufer
a foaf:Agent, foaf:Person;
foaf:givenName "Laufer";
foaf:mbox <mailto:laufer@example.org>
duv:develops :xyplotter;
.
:xyplotter
a duv:Application;
rdfs:label "2dplotter" ;
duv:consumes :dataset-03312004
duv:developedBy :laufer ;
.
:insitu-measurement-data-logger
a duv:WebThing;
rdfs:label "surface meteorology data logger" ;
duv:consumes :configfile ;
.
:configfile-csv
a dcat:Distribution;
.
:configfile
a dcat:Dataset ;
dct:title "configuration settings" ;
dcat:distribution :configfile-csv ;
.
:dataset-Jan-Mar-2004-csv
a dcat:Distribution;
.
:dataset-03312004
a dcat:Dataset;
dct:title "Mars Quarterly Temperature Plot";
dcat:distribution :dataset-Jan-Mar-2004-csv;
.
Example
2
-
Feedback:
Laufer
provides
feedback
about
on
the
temperature
readings
dataset.
Example
2
Web
[
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix dct: <http://purl.org/dc/terms#> .
@prefix oa: <http://www.w3.org/ns/oa#> .
@prefix duv: <http://www.w3.org/ns/duv#> .
@prefix : <http://example.org#> .
MSUDataCite
:laufer
a duv:Person ;
foaf:givenName "Laufer" ;
foaf:mbox <mailto:laufer@example.org> ;
.
]
[
:dataset-03312004
a dcat:Dataset ;
dct:title "Mars Quarterly Temperature Plot" ;
.
EmoryUCite
:comment1
a duv:Feedback ;
oa:hasBody "Written in MS-DOS text format." ;
oa:hasTarget :dataset-03312004 ;
oa:annotatedBy :laufer ;
.
].
These
resources
helped
scope
the
DUV
citation
model
into
the
minimal
requirements
for
electronic
data
publication.
Finally,
data
citation
principles
being
adopted
[
:comment2
a duv:Feedback;
duv:hasRating "3 Star";
oa:hasBody "Linked Data Rating";
oa:hasTarget :dataset-03312004;
.
FORCE11-Citation
Example
3
-
Citation:
A
technical
report
:paperA
identified
by
a
DOI
cites
]
are
also
being
considered
to
ensure
the
dataset.
The
:dataset-03312013
DUV
is
also
identified
consistent
with
guidelines
developed
by
a
digital
object
identifier
(DOI).
other
data
citation
communities.
This section is non-normative.
This section depicts the vocabulary as a conceptual model. Shaded boxes are used to identify each class. Labeled open arrows identify example properties between the classes. Unlabeled shaded arrows are used to show inheritance with the parent class identified by the arrow head.
RDF Class: |
|
---|---|
Definition |
|
rdfs:isDefinedBy |
|
Label |
|
rdfs:subClassOf | duv:UserFeedback |
RDF Class: |
|
---|---|
Definition |
|
rdfs:isDefinedBy |
|
Label |
|
RDF
|
|
---|---|
Definition |
A
|
|
|
Label |
usage
tool
|
RDF
|
|
---|---|
Definition |
|
|
|
rdfs:isDefinedBy | http://www.w3.org/ns/duv |
Label | user feedback |
rdfs:subClassOf | oa:Annotation |
RDF
|
|
---|---|
Definition |
|
Domain | foaf:Agent |
Range | skos:Concept |
Label |
|
RDF Property: |
|
---|---|
Definition | Text content of an annotation body. |
vann:usageNote | cnt:ContentAsText (subject) cnt:chars (predicate) rdfs:Literal (object) |
Label | chars |
RDF Property: |
|
---|---|
Definition |
|
vann:usageNote |
dcat:Dataset
(subject)
dct:created
(predicate)
rdfs:Literal
(object)
dcat:Distribution (subject) dct:created (predicate) rdfs:Literal (object) |
Label | created |
RDF Property: |
|
---|---|
Definition |
|
vann:usageNote |
dcat:Distribution (subject) dct:creator (predicate) foaf:Agent (object) |
Label | creator |
RDF Property: |
|
---|---|
Definition |
|
vann:usageNote |
dcat:Dataset (subject) disco:fundedBy (predicate) foaf:Agent (object) dcat:Distribution (subject) fundedBy (predicate) foaf:Agent (object) |
Label |
|
RDF Property: | oa:hasBody |
---|---|
Definition | Body of the comment associated with either feedback or associated with citation. |
rdfs:isDefinedBy |
|
vann:usageNote |
duv:UserFeedback
(subject)
oa:hasBody
(predicate)
cnt:ContentAsText
(object)
oa:Annotation (subject) oa:hasBody (predicate) cnt:ContextAsText (object) |
Label | has body |
RDF Property: |
|
---|---|
Definition |
|
vann:usageNote |
cito:CitationAct
(subject)
cito:hasCitedEntity
(predicate)
dcat:Dataset
(object)
cito:CitationAct (subject) cito:hasCitedEntity (predicate) dcat:Distribution (object) |
Label | has cited entity |
RDF Property: | cito:hasCitingEntity |
---|---|
Definition | Citation that references a dataset or a distribution. |
|
|
|
|
RDF Property: |
|
---|---|
Definition |
|
|
dcat:Dataset |
Range |
|
|
|
|
|
RDF
|
|
---|---|
Definition |
|
|
|
Range | duv:Usage |
Label |
|
|
|
RDF Property: |
|
---|---|
Definition |
|
Domain | dcat:Distribution |
Range |
|
Label | has target |
rdfs:isDefinedBy | http://www.w3.org/ns/duv |
RDF Property: |
|
---|---|
Definition |
|
Domain | dcat:Distribution |
Range |
|
Label | has distribution usage |
rdfs:isDefinedBy | http://www.w3.org/ns/duv |
RDF
|
|
---|---|
Definition |
|
|
|
vann:usageNote |
dcat:Dataset
(subject)
duv:hasDistributor
(predicate)
foaf:Agent
(object)
dcat:Distribution (subject) duv:hasDistributor (predicate) foaf:Agent (object) |
Label |
|
RDF Property: |
|
---|---|
Definition |
|
Range |
|
vann:usageNote |
dcat:Dataset
(subject)
duv:hasProducer
(predicate)
foaf:Agent
(object)
dcat:Distribution (subject) duv:hasProducer (predicate) foaf:Agent (object) |
Label | has producer |
RDF Property: |
|
---|---|
Definition |
|
Domain | RatingFeedback |
Range |
|
Label | has rating |
rdfs:isDefinedBy | http://www.w3.org/ns/duv |
RDF Property: |
|
---|---|
Definition |
|
rdfs:isDefinedBy |
|
|
duv:UserFeedback (subject) oa:hasTarget (predicate) dcat:Distribution (object) oa:Annotation (subject) oa:hasTarget (predicate) cito:CitationAct (object) |
|
|
RDF
|
|
---|---|
Definition |
|
|
|
Range | duv:UsageTool |
Label |
|
rdfs:isDefinedBy | http://www.w3.org/ns/duv |
RDF
|
|
---|---|
Definition |
|
vann:usageNote |
dcat:Distribution (subject) dct:identifier (predicate) rdfs:Literal (object) |
Label |
|
RDF
|
|
---|---|
Definition |
|
rdfs:isDefinedBy |
|
|
oa:Annotation (subject) oa:motivatedBy (predicate) oa:Motivation (object) |
|
|
RDF Property: |
|
---|---|
Definition |
|
Domain | foaf:Agent |
Range |
|
Label |
|
rdfs:isDefinedBy |
|
RDF
|
|
---|---|
Definition |
|
|
|
Range | duv:Usage |
Label |
|
|
|
RDF Property: |
|
---|---|
Definition |
|
vann:usageNote |
dcat:Dataset
(subject)
prism:publicationDate
(predicate)
rdfs:Literal
(object)
dcat:Distribution (subject) prism:publicationDate (predicate) rdfs:Literal (object) |
Label |
|
RDF Property: |
|
---|---|
Definition |
|
vann:usageNote |
dcat:Distribution (subject) dct:publisher (predicate) rdfs:Literal (object) |
Label |
|
RDF Property: |
|
---|---|
Definition |
|
|
|
|
|
vann:usageNotes |
|
| refers to dataset |
RDF Property: |
|
---|---|
Definition |
|
|
|
|
|
vann:usageNotes |
|
| refers to distribution |
RDF Property: |
|
---|---|
Definition |
|
|
dcat:Distribution (subject) dct:title (predicate) rdfs:Literal (object) |
|
|
RDF
|
|
---|---|
Definition |
|
|
|
Range | skos:Concept |
Label |
|
RDF
|
|
---|---|
Definition |
|
vann:usageNote |
dcat:Distribution (subject) pav:version (predicate) rdfs:Literal (object) |
Label |
|
This section shows some examples to illustrate the application of the Dataset Usage Vocabulary.
Example 1 - Usage: A 2-D charting application developed to create temperature plots that consumes temperature readings from a dataset to produce the plot.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix dcat: <http://www.w3.org/ns/dcat#> . @prefix dct: <http://purl.org/dc/terms/> . @prefix duv: <http://www.w3.org/ns/duv#> . @prefix prov: <http://www.w3.org/nsprov#> . @prefix : <http://example.org#> . :plot-graphic a duv:Usage; rdfs:label "plots a 2d graphic"; duv:performedBy :xyplotter; duv:hasUsageType :application; duv:hasUsageTool :tool1; duv:refersTo :dataset-03312004; . :xyplotter a foaf:Agent; rdfs:label "2dplotter"; duv:classification :chart-software; . :tool1 a duv:UsageTool; rdfs:label ""; . :usageType a skos:ConceptScheme; skos:prefLabel "A set of concepts to classify the usage of datasets or distributions"; . :application a skos:Concept; skos:inScheme :usageType ; skos:prefLabel "Application"; . :usageAgent a skos:ConceptScheme; skos:prefLabel "A set of concepts to classify the possible roles of usage agents"; . :chart-software a skos:Concept; skos:inScheme :usageAgent ; skos:prefLabel "Chart Software"; . :dataset-03312004 a dcat:Dataset; dct:title "Quarterly Temperature Plot"; dcat:distribution :dataset-Jan-Mar-2004-csv; duv:hasUsage: :plot-graphic; .
Example 2 - Feedback: Laufer provides feedback about the temperature readings dataset.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix dcat: <http://www.w3.org/ns/dcat#> . @prefix dct: <http://purl.org/dc/terms#> . @prefix oa: <http://www.w3.org/ns/oa#> . @prefix duv: <http://www.w3.org/ns/duv#> . @prefix cnt: <http://www.w3.org/2011/content/> . @prefix : <http://example.org#> . :dataset-03312004 a dcat:Dataset ; dct:title "Quarterly Temperature Plot" ; duv:hasDatasetFeedback :comment1; duv:hasDatasetFeedback :comment2; . :comment1Content a cnt:ContentAsText ; cnt:chars "Written in MS-DOS text format." . :comment1 a duv:UserFeedback ; oa:hasBody comment1Content ; oa:hasTarget :dataset-03312004 ; dct:creator :laufer . :comment2 a duv:UserRatingFeedback; duv:hasRating :three_stars; oa:hasTarget :dataset-03312004; dct:creator :laufer ; . :laufer a foaf:Person ; foaf:Name "Laufer" ; . :feedbackRating a skos:ConceptScheme; skos:prefLabel "A set of concepts to rate datasets or distributions"; . :three_stars a skos:Concept; skos:inScheme :feedbackRating ; skos:prefLabel "Good dataset or distribution" ; .
Example 3 - Citation: A technical report :paperA identified by a DOI cites the dataset. The :dataset-03312013 is also identified by a digital object identifier (DOI).
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix dcat: <http://www.w3.org/ns/dcat#> . @prefix dct: <http://purl.org/dc/terms#> . @prefix oa: <http://www.w3.org/ns/oa#> . @prefix cito: <http://purl.org/spar/cito#> . @prefix fabio: <http://purl.org/spar/fabio#>. @prefix prism: <http://prismstandard.org/namespaces/basic/2.0/>. @prefix duv: <http://www.w3.org/ns/duv#> . @prefix : <http://example.org#> . :dataset-03312013 a dcat:Dataset; dct:identifier "doi:10.1038/ex2158"; dct:title "Quarterly Temperature Plot"@en ; dct:alternative "Qtrly Temp Plot"@en; dct:description "This plot features average surface temperatures measured by the Mars Land Rover. "@en ; dct:created "2013-03-31T15:18:00Z"^^xsd:dateTime ; dct:creator "Laufer" ; dct:license <http://creativecommons.org/licenses/by-sa/3.0/> ; dcat:keyword "Mars"; dct:language <http://www.lexvo.org/page/iso639-3/eng> ; cito:isCitedBy :citation1 ; . :thisCitation a cito:CitationAct; cito: :dataset-03312004; cito:hasCitedEntity :citation1; . :citation1 a duv:DataCitation; duv: :paperA; dct:title "Quarterly Temperature Plot"; dct:hasVersion "1.0"; dct:created "2013-03-31T15:18:00Z"^^xsd:dateTime; dct:identifier "doi:10.1038/ex2158"; dct:creator :laufer"; . :paperA a fabio:Work; prism:doi "doi:20.1055/ex7758"; dct:title "Mars Weather Technical Report"@en; .
This section shows some of the requirements that motivated the development of the Dataset Usage Vocabulary. These requirements were derived from the use cases described in Data on the Web Best Practices Use Cases & Requirements document.
It should be possible to track the usage of data.
Capability of tracking data usage can help enhancing reputation of the datasets. Records of data usage shows all the successful outcome of the data usage and all the entities associated with it such as the person, organisation, application, research projects that has used these datasets. It increases trust in the data. It also provides provence about how data versions over the time.
Use Case | R-TrackDataUsage Benefits |
Airborne Snow Observatory |
Data
is
used
in
decision
making
process
by
Water
Reservoir
Managers.
Capability
to
track
usage
of
data
will
lead
to
identification
of
all
the
decisions
and
policy
changes
made
by
authorities
based
on
this
data.
It
will
also
list
applications,
tools
and
frameworks
suitable
for
analysis
of
this
kind
of
data.
|
LandPortal | Data is used in Research; Policy Making, Journalism; Development; Investments; Governance; Food security; Poverty; Gender issues. Usage tracking will help in assessing the impact of published data. |
LusTRE |
Data
is
put
in
public
for
reuse
and
reference
in
nature
conservation
activities.
Information
about
use
of
this
data
|
Open Experimental Field Studies | Data is used in computational models and studies. Capabilities to track usage of data will enable data publishers to identify all the users communities making use of this data. It will also identify combined use of multiple datasets in one big study. This will identify related datasets which can be recommended to future users. |
RDESC | Data is published in Linked Data Format for discovery and recommendations of related datasets. Capability to keep track of its usage will list all the tools and application suitable to be used with this data. Because RDESC is not data publisher but more of a data facilitator, usage tracking will identify highly search dataset and the trends in the temporal, spatial and domain specific search queries. |
UKOpenResearchForum | Data is published with intelligent openness to support research projects. Capability to track data usage will provide adequate acknowledgement to data originator. |
Data consumers should have a way of sharing feedback and rating data.
User feedback is important to address data quality concerns about published dataset. Different users may have different experience with the same dataset so it is important to capture the context in which data was used and the profile of the user who uses it. R-UsageFeedback should also provide a way to communicate suggested corrections and update to the datasets by the users back to data publisher. Data publishers should have a review mechanism to incorporate submitted corrections.
Use Case | R-UsageFeedback Benefits |
Airborne Snow Observatory | Data grows rapidly each year. User feedback can reports issues of data completeness and correctness. |
DadosGovBr | Data came from various publishers. As a catalog, the site has faced several challenges, one of them was to integrate the various technologies and formulas used by publishers to provide datasets in the portal. User feedback can provided usabilities of those technologies and formulas. User feedback can be used to crowdsource discrepancies in the vocabularies used to describe datasets. |
LusTRE | Data multilingualism is one of the challenge for this use case. User feedback can be used to crowdsource multilingual text alignment. |
Experimental Field Studies | Data is used in computational models and studies. User feedback can be used to identify good quality data required for good quality research. completeness, time resolution and usability can be captured using user feedback. |
RDESC | RDESC curate different data source and publish metadata in Linked Data Format. User feedback is useful to assess metadata quality. Availability of the source datasets, Correctness of persistent URI, Correctness of the concepts defined in RDESC such as FOAF Agents, Organizations, Physical Properties and Usability of the search interface can be captured in user feedback. |
It should be possible to cite data on the Web.
Use Case | R-Citable Benefits |
Open Experimental Field Studies | Various experiments and fields studies are performed to generate data which is used in computational models and bigger studies.Capability to capture all the citations of the published data can justify the efforts used in publishing. Citation information can be used to identify all the user communities interested in data source. |
LATimes | On 27 March 2014, the LA Times published a story Women earn 83 cents for every $1 men earn in L.A. city government. It was based on an Infographic released by LA's City Controller, Ron Galperin. This report could only cite data portal of all the resource. It could not cite to exact dataset because tool long URI. |
RDESC | RDESC is a data curator so it uses data from different sources. But this usage is not communicated to data publishers because of lack of such mechanism provided by publishers. |
The editors wish to thank Silvio Peroni, University of Bologna, for his significant contribution to the DUV citation model. Silvio Peroni is a co-author of the Semantic Publishing and Referencing (SPAR) Ontologies.