Abstract

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 ) 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.

Status of This Document

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 the second third iteration of the vocabulary, developed following extensive consultation among and outside the working group who now regard it as nearing completion. Comment and feedback is sought before the next iteration which is likely to be the final version for the foreseeable future.

This document was published by the Data on the Web Working Group as a Working Draft. If you wish to make comments regarding this document, please send them to public-dwbp-comments@w3.org public-dwbp-wg@w3.org ( subscribe , archives ). All comments are welcome.

Publication as a 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 September 2015 W3C Process Document .

1. Introduction

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 and data correction.

View as: .

2. Namespaces

The namespace for DUV is http://www.w3.org/ns/duv# . However, it should be noted that DUV makes extensive use of terms from other vocabularies.   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.

Issue 1 All namespaces need to be verified. Issue-235
Prefix Namespace
biro http://purl.org/spar/biro/
cito http://purl.org/spar/cito/
cnt http://www.w3.org/2011/content 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/
disco http://rdf-vocabulary.ddialliance.org/discovery#
dqv http://www.w3.org/ns/dqv#
duv http://www.w3.org/ns/duv#
fabio http://purl.org/spar/fabio/
foaf http://xmlns.com/foaf/0.1/
frbr http://purl.org/vocab/frbr/ http://purl.org/vocab/frbr/core#
oa http://www.w3.org/ns/oa#
pav http://pav-ontology.github.io/pav/ prism http://prismstandard.org/namespaces/basic/2.2/ http://purl.org/pav
rdf http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs http://www.w3.org/2000/01/rdf-schema#
skos http://www.w3.org/2004/02/skos/core#
vann http://purl.org/vocab/vann# http://purl.org/vocab/vann/
xsd http://www.w3.org/2001/XMLSchema#

3. Audience

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.

4. Scope

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.

5. Relationship to other Vocabularies

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 reuse.

Core to the dataset usage vocabulary is the “dataset”. The DUV uses the Data Catalog Vocabulary's dcat:Dataset class and all properties associated with the class [ VOCAB-DCAT ]. From a data usage perspective the DUV can be considered an extension of 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, 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 dcat:Dataset for uses beyond the scope of the DUV .

The Semantic Publishing and Referencing [ SPAR ] Ontologies provides a suite of vocabularies used to related entities to reference citations, bibliographic records, and describe the publication process along with other related activities. The DUV directly relies upon Citation Typing Ontology [ 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. In addition to ontologies the research community provided basic criteria for citing data on the Web [ MSUDataCite ] [ EmoryUCite ]. These resources helped scope the DUV citation model into the minimal requirements for electronic data publication. Finally, data citation principles being adopted [ FORCE11-Citation ] are also being considered to ensure the DUV is consistent with guidelines developed by other data citation communities.

6. Vocabulary Overview

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.

Note Links to the classes and properties need to be added as a way to more easily reference the document. The class diagram for DUV

6.1 Citation Model

Note Does

The citation model was motivated by the reader more of an orientation UCR requirement R-Citable It should be possible to cite data on the model? What would be helpful? Web. The citation model is largely based on classes, properties, and recommended approaches taken from the SPAR Ontologies.  Ontologies. The remainder of the model is composed from the Open Annotation vocabulary, Dublin Core, FOAF and by newly introduced DUV properties.  properties.

The citation model is comprised of seeks to meet the following classes: needs of:

  1. Data publishers who need to provide basic bibliographic reference criteria for dcat:Dataset and dcat:Distributions (See Example 1) . To do this, DUV extensions are added to the DCAT model. Classes include: dcat:Dataset, dcat:Distribution, biro:BibliographicReference, fabio:Expression, cito:CitationAct, oa:Annotation, oa:Motivation, cnt:ContentAsText, skos:Concept, and foaf:Agent. Properties include: frbr:part, frbr:partOf, biro:references, dct:title, pav:version, prism:publicationDate, dct:issued, dct:created, dct:identifier, dct:creator, duv:agentClassification, dct:publisher, duv:hasDistributor, disco:fundedBy.
  2. Data publishers wanting to annotate dcat:Datasets/dcat:Distributions with bibliographic references that provide data additional insights to data consumers (See Example 2) . Classes include: dcat:Dataset, dcat:Distribution, biro:BibliographicReference, fabio:Expression. Properties include: biro:BibliographicReference, frbr:part, frbr:partOf, biro:references.
  3. Data consumers who want to understand the rationale as to why a dcat:Dataset and dcat:Distribution is being cited (See Example 3) . Classes include: fabio:Expression, cito:CitationAct, oa:Annotation, oa:Motivation, cnt:ContentAsText. Properties include: cito:hasCitingEntity, cito:hasCitedEntity, disco:fundedBy, cnt:chars, oa:hasTarget, oa:hasBody.   oa:hasBody.

Note that while the DUV reuses a limited set of [ SPAR ] classes and properties to support basic [ VOCAB-DCAT ] Dataset and Distribution citation requirements, the [ SPAR ] ontologies a richer set of classes and properties for more advanced representations. For example [ FaBIO ] fabvio:Work class has many subclasses (e.g. fabio:Policy) that help characterize referenced material.

Issue 2 6.2 Usage Model I did not understand duv:UsageTool . Why is this needed?

The description is cryptic to me. usage model was motivated by the UCR requirement R-TrackDataUsage It says “A synopsis should be possible to track the usage of data. Sharing and tracking data usage can help enhancing the utility of the datasets by providing help describing how the way datasets can be used by a tool consumer (See Example 5) . Usage could be considered as enabling descriptive information provided by the data publisher to help the consumer community make use of datasets and distributions. Based on the use cases, data usage can help provide guidance information about how to use a the dataset or distribution.” A tool and tools (See Example 6) that can be used with the dataset. As also stipulated by use cases is not a synopsis. So, this seems the need to confuse real-world entity (a tool) with a text, a description? Issue-234 Usage Model track usage metrics

The following classes constitute the Usage Model: dcat:Dataset, dcat:Distribution, duv:Usage, duv:UsageTool, foaf:Agent, and skos:Concept. foaf:Agent. Properties include: duv:hasDatasetUsage, duv:has:DistributionUsage, duv:hasUsage, duv:hasUsageType, duv:performedBy, duv:performs, duv:refersToDataset, duv:refersToDistribution, duv:agentClassification, duv:usageClassification. duv:refersTo, dct:uri, dct:title, dct:created, pav:version, dct:issued, and dct:description.

6.2 6.3 Feedback Model

The feedback model was motivated by UCR requirement R-UsageFeedback Data consumers should have a way of sharing feedback and rating data (See Example 4) . 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 for consumers to communicate suggested corrections or advice back to data publisher.

The following classes constitute the Feedback Model: dcat:Dataset, dcat:Distribution, oa:Annotation, oa:Motivation, duv:UserFeedback, dqv:UserQualityFeedback, duv:RatingFeedback, skos:Concept, cnt:ContentAsText. Properties include: duv:hasRating, oa:hasTarget, oa:hasBody, duv:hasDatasetFeedback, duv:hasDistributionFeedback, duv:hasFeedback, duv:hasFeedback, oa:motivatedBy, cnt:chars.

Issue 3 The rationale for duv:usageClassification , duv:agentClassification , need to be described more thoroughly or be reconsidered for scope. Issue-236
Note
This section will be non-normative and will contain links back to the vocabularies we mention.

7. Vocabulary Specification

7.1 Class: RatingFeedback

RDF Class: duv:RatingFeedback
Definition Predefined criteria used to express a user opinion about a dataset or distribution using a discrete range of values.
rdfs:isDefinedBy http://www.w3.org/ns/duv
Label rating feedback
rdfs:subClassOf duv:UserFeedback

7.2 Class: Usage

RDF Class: duv:Usage
Definition A helpful description of actions that can be performed on a given dataset or distribution.
rdfs:isDefinedBy http://www.w3.org/ns/duv
Label usage

7.3 Class: UsageTool

RDF Class: duv:UsageTool
Definition A synopsis describing the way a tool can use a dataset or distribution.
rdfs:isDefinedBy http://www.w3.org/ns/duv
Label usage tool
Issue 4 Stability of rev:Feedback class Issue-237

7.4 Class: UserFeedback

Sub class of: rev:Feedback rdfs:isDefinedBy http://www.w3.org/ns/duv
RDF Class: duv:UserFeedback
Definition User feedback on the dataset. Expresses whether the dataset was useful or not, for example.
Label user feedback
rdfs:subClassOf oa:Annotation
Issue 5 A number of properties have been created to accommodate support for dcat:Distribution and dcat:Dataset. To avoid having multiple classes for the domain and range properties were duplicated such as duv:hasDatasetUsage and duv:hasDistributionUsage. Issue-238

7.5 Properties

Property: agentClassification RDF Property: duv:agentClassification Definition  Extension vocabularies may wish to specialize this property to have a range corresponding to a specific   ConceptScheme to describe an agent. Domain foaf:Agent Range skos:Concept Label agent classification

Property: chars

RDF Property: cnt:chars
Definition Text content of an annotation body.
vann:usageNote cnt:ContentAsText (subject) cnt:chars (predicate) rdfs:Literal (object)
Label chars

Property: created

RDF Property: dct:created
Definition The creation date associated with the dataset or distribution
vann:usageNote dcat:Dataset (subject) dct:created (predicate) rdfs:Literal (object)
dcat:Distribution (subject) dct:created (predicate) rdfs:Literal (object)
Label created

Property: creator

RDF Property: dct:creator
Definition Author of the cited dataset/distribution
vann:usageNote dcat:Dataset (subject) dct:creator (predicate) foaf:Agent (object)
dcat:Distribution (subject) dct:creator (predicate) foaf:Agent (object)
Label creator

Property: description

RDF Property: dct:description
Definition free-text usage account of the resource.
vann:usageNote duv:Usage (subject) dct:description (predicate) rdfs:Literal (object)
duv:UsageTool (subject) dct:description (predicate) rdfs:Literal (object)
Label description

Property: fundedBy

RDF Property: disco:fundedBy
Definition Funding agent
vann:usageNote
dcat:Dataset (subject) disco:fundedBy  disco:fundedBy (predicate) foaf:Agent (object)
dcat:Distribution (subject) fundedBy (predicate) foaf:Agent (object)
Label funded by

Property: oa:hasBody

RDF Property: oa:hasBody
Definition Body of the comment associated with either feedback or associated with citation.
rdfs:isDefinedBy oa:hasBody vann:usageNote duv:UserFeedback (subject) oa:hasBody (predicate) cnt:ContentAsText (object)
oa:Annotation (subject) oa:hasBody (predicate) cnt:ContextAsText (object)
Label has body

Property: hasCitedEntity

RDF Property: cito:hasCitedEntity
Definition The dataset, distribution, or citation of interest being cited.
vann:usageNote cito:CitationAct (subject) cito:hasCitedEntity (predicate) dcat:Dataset (object)
cito:CitationAct (subject) cito:hasCitedEntity (predicate) dcat:Distribution (object)
Label has cited entity

Property: hasCitingEntity

RDF Property: cito:hasCitingEntity
Definition Citation that references a dataset or a distribution.
vann:usageNote cito:CitationAct (subject) cito:hasCitingEntity (predicate) fabio:Expression (object)
Label has citing entity

Property: hasDatasetFeedback hasFeedback

Domain
RDF Property: duv:hasDatasetFeedback duv:hasFeedback
Definition User feedback associated with dataset Domain dcat:Dataset Range duv:UserFeedback Label has dataset feedback rdfs:isDefinedBy http://www.w3.org/ns/duv Property: hasDatasetUsage RDF Property: duv:hasDatasetUsage Definition Dataset usage guidance or instructions. Domain dcat:Dataset Range duv:Usage Label has dataset usage rdfs:isDefinedBy http://www.w3.org/ns/duv Property: hasDistributionFeedback RDF Property: duv:hasDistributionFeedback Definition User feedback associated with distribution. distribution
dcat:Distribution Range vann:usageNote dcat:Dataset (subject) duv:hasFeedback (predicate) duv:UserFeedback Label has target rdfs:isDefinedBy http://www.w3.org/ns/duv Property: hasDistributionUsage RDF Property: duv:hasDistributionUsage Definition Distribution usage guidance or instructions. Domain (object)
dcat:Distribution Range duv:Usage (subject) duv:hasFeedback (predicate) duv:UserFeedback (object)
Label has distribution usage rdfs:isDefinedBy http://www.w3.org/ns/duv dataset/distribution feedback

Property: hasDistributor

RDF Property: duv:hasDistributor
Definition The distributor is The distributor is the organization that makes the dataset available for downloading and use.  Range foaf:Agent use.
vann:usageNote dcat:Dataset (subject) duv:hasDistributor (predicate) foaf:Agent (object)
dcat:Distribution (subject) duv:hasDistributor (predicate) foaf:Agent (object)
Label has distributor

Property: hasProducer

Range foaf:Agent
RDF Property: duv:hasProducer
Definition The producer is The producer is the organization that sponsored the author’s research and/or the organization that made the creation of the dataset possible, such as codifying and digitizing the data.
vann:usageNote dcat:Dataset (subject) duv:hasProducer (predicate) foaf:Agent (object)
dcat:Distribution (subject) duv:hasProducer (predicate) foaf:Agent (object)
Label has producer

Property: hasRating

Domain rdfs:isDefinedBy http://www.w3.org/ns/duv
RDF Property: duv:hasRating
Definition RatingFeedback has rating opinion
RatingFeedback Range vann:usageNote duv:RatingFeedback (subject) duv:hasRating (predicate) skos:Concept (object)
Label has rating

Property: oa:hasTarget

RDF Property: oa:hasTarget
Definition Dataset or distribution associated with UserFeedback.
rdfs:isDefinedBy oa:hasTarget vann:usageNote duv:UserFeedback (subject) oa:hasTarget (predicate) dcat:Dataset (object)
duv:UserFeedback (subject) oa:hasTarget (predicate) dcat:Distribution (object)
oa:Annotation (subject) oa:hasTarget (predicate) cito:CitationAct (object)
Label has target

Property: hasUsageTool hasUsage

Domain
RDF Property: duv:hasUsageTool duv:hasUsage
Definition Dataset or distribution tool Dataset/distribution usage synopsys guidance or instructions.
vann:usageNote dcat:Dataset (subject) oa:hasUsage(predicate) duv:Usage (object)
dcat:Distribution (subject) oa:hasUsage (predicate) duv:Usage (object)
Label has dataset/distribution usage

Property: hasUsageTool

RDF Property: duv:hasUsageTool
Range Definition duv:UsageTool Provided guidance about a tool that can be applied to a dataset/distribution.
Label vann:usageNote has usage tool dcat:Usage (subject) oa:hasUsageTool(predicate) duv:UsageTool (object)
rdfs:isDefinedBy Label http://www.w3.org/ns/duv has usage tool

Property: identifier

RDF Property: dct:identifier
Definition The identifier of the dataset or distribution.
vann:usageNote dcat:Dataset (subject)  (subject) dct:identifier (predicate) rdfs:Literal (object)
dcat:Distribution (subject)  (subject) dct:identifier (predicate) rdfs:Literal (object)
Label identifier

Property: motivatedBy issued

RDF Property: oa:motivatedBy dct:issued
Definition reason behind citation annotation The issue or userfeedback rdfs:isDefinedBy oa:motivatedBy publication date associated with the dataset or distribution
vann:usageNote duv:UserFeedback dcat:Dataset (subject) oa:motivatedBy dct:issued (predicate) oa:Motivation rdfs:Literal (object)
oa:Annotation dcat:Distribution (subject) oa:motivatedBy dct:issued (predicate) oa:Motivation rdfs:Literal (object)
Label motivated by Date of issue or publication date.

Property: performedBy motivatedBy

Domain rdfs:isDefinedBy http://www.w3.org/ns/duv
RDF Property: duv:performedBy oa:motivatedBy
Definition Usage performed by agent. reason behind citation annotation or userfeedback
foaf:Agent Range vann:usageNote duv:Usage duv:UserFeedback (subject) oa:motivatedBy (predicate) oa:Motivation (object)
oa:Annotation (subject) oa:motivatedBy (predicate) oa:Motivation (object)
Label performed motivated by

Property: performs performedBy

Domain
RDF Property: duv:performs duv:performedBy
Definition Agent performs usage Usage performed by agent.
foaf:Agent Range vann:usageNote duv:Usage (subject) duv:performedBy (predicate) foaf:Agent (object)
Label performs rdfs:isDefinedBy http://www.w3.org/ns/duv performed by

Property: publicationDate performs

RDF Property: prism:publicationDate duv:performs
Definition The publication date associated with the dataset or distribution Agent performs usage
vann:usageNote dcat:Dataset (subject) prism:publicationDate (predicate) rdfs:Literal (object) dcat:Distribution foaf:Agent (subject) prism:publicationDate duv:performs (predicate) rdfs:Literal (object) duv:Usage(object)
Label publication date performs

Property: publisher
RDF Property: dct:publisher
Definition Creator of the cited dataset of distribution
vann:usageNote dcat:Dataset (subject)  (subject) dct:publisher (predicate) rdfs:Literal (object)
dcat:Distribution (subject)  (subject) dct:publisher (predicate) rdfs:Literal (object)
Label publisher

Property: refersToDataset refersTo

RDF Property: duv:refersToDataset duv:refersTo
Definition Dataset Dataset/distribution associated with Usage.
Domain duv:Usage rdfs:isDefinedBy http://www.w3.org/ns/duv vann:usageNotes duv:Usage (subject) duv:refersToDataset (predicate) dcat:Dataset (object)
Label refers to dataset
Property: refersToDistribution RDF Property: duv:refersToDistribution Definition Distribution associated with Usage. Domain duv:Usage rdfs:isDefinedBy http://www.w3.org/ns/duv vann:usageNotes duv:Usage (subject) duv:refersToDistribution (predicate) dcat:Distribution (object) Label refers to distribution

Property: title

RDF Property: dct:title
Definition The title of citation, dataset or distribution
vann:usageNote dcat:Dataset (subject)  (subject) dct:title (predicate) rdfs:Literal (object)
dcat:Distribution (subject)  (subject) dct:title (predicate) rdfs:Literal (object)
Label title
Property: usageClassification RDF Property: duv:usageClassification Definition  Extension vocabularies may wish to specialize this property to have a range corresponding to a specific   ConceptScheme to describe usage. Domain duv:Usage Range skos:Concept Label usage classification

Property: version

RDF Property: pav:version
Definition The version or edition number associated with the dataset.
vann:usageNote dcat:Dataset (subject)  (subject) pav:version (predicate) rdfs:Literal (object)
dcat:Distribution (subject)  (subject) pav:version (predicate) rdfs:Literal (object)
Label version

8. Examples

Note The examples need to be updated based on the new vocabulary. Are the examples detailed enough to help orient readers to the vocabulary? Are the examples correct?

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 Citation: Basic reference criteria for a dataset to produce the plot. 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 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; . 
ex:timetable-001 a dcat:Dataset ;
        dct:title  "Bus timetable of MyCity"^^xsd:string;
        prism:doi "10.3456/4567.21"^^xsd:string ;
        pav:version "series-1.2"^^xsd:string;
        dct:issued "2015-05-05"^^xsd:date;
        dct:creator <http://example.org/transport-agency/contact>;
{ "@graph" : [ { "@id" : "_:b0", "@type" : "prov:Association", "agent" : "http://example.org#xyplotter", "hadRole" : "http://example.org#chart-software" }, { "@id" : "http://example.org#chart-software", "@type" : "prov:Role", "rdfs:label" : "software that creates charts" }, { "@id" : "http://example.org#dataset-03312004", "@type" : "dcat:Dataset", "dct:title" : "Quarterly Temperature Plot", "distribution" : "http://example.org#dataset-Jan-Mar-2004-csv" }, { "@id" : "http://example.org#dataset-Jan-Mar-2004-csv", "@type" : "dcat:Distribution" }, { "@id" : "http://example.org#plot-csv-data", "@type" : "duv:Usage", "entity" : "http://example.org#dataset-03312004", "qualifiedUsage" : "http://example.org#plot-graphic" }, { "@id" : "http://example.org#plot-graphic", "@type" : "prov:Activity", "rdfs:label" : "plots a 2d graphic", "qualifiedAssociation" : "_:b0" }, { "@id" : "http://example.org#xyplotter", "@type" : [ "foaf:Agent", "prov:SoftwareAgent" ], "rdfs:label" : "2dplotter" } ], "@context" : { "agent" : { "@id" : "http://www.w3.org/nsprov#agent", "@type" : "@id" }, "hadRole" : { "@id" : "http://www.w3.org/nsprov#hadRole", "@type" : "@id" }, "qualifiedUsage" : { "@id" : "http://www.w3.org/nsprov#qualifiedUsage", "@type" : "@id" }, "entity" : { "@id" : "http://www.w3.org/nsprov#entity", "@type" : "@id" }, "label" : { "@id" : "http://www.w3.org/2000/01/rdf-schema#label", "@type" : "http://www.w3.org/2001/XMLSchema#string" }, "title" : { "@id" : "http://purl.org/dc/terms/title", "@type" : "http://www.w3.org/2001/XMLSchema#string" }, "distribution" : { "@id" : "http://www.w3.org/ns/dcat#distribution", "@type" : "@id" }, "qualifiedAssociation" : { "@id" : "http://www.w3.org/nsprov#qualifiedAssociation", "@type" : "@id" }, "dct" : "http://purl.org/dc/terms/", "duv" : "http://www.w3.org/ns/duv#", "rdf" : "http://www.w3.org/1999/02/22-rdf-syntax-ns#", "rdfs" : "http://www.w3.org/2000/01/rdf-schema#", "dcat" : "http://www.w3.org/ns/dcat#", "prov" : "http://www.w3.org/nsprov#" } }

Example 2 - Feedback: Laufer provides feedback about the temperature readings Citation: An electronic memorandum that references a 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" ; . 
     
ex:timetable-001 a dcat:Dataset ;
        dct:title  "Bus timetable of MyCity"^^xsd:string;
        prism:doi "10.3456/4567.21"^^xsd:string ;
        pav:version "series-1.2"^^xsd:string;
        dct:issued "2015-05-05"^^xsd:date;
        dct:creator <http://example.org/transport-agency/contact>;
.

ex:timetable-memorandum
      a biro:BibliographicReference;
      a fabio:Policy  ;
      dct:bibliographicCitation
     "Costello, E. Mayor (2015). City Timetable Schedule Change Memorandum Effective 
      January 1, 2015. Sept 15, 2014. DOI:0.3456/4567.21"^^xsd:string ;
      biro:references ex:timetable-001 ;
.
{ "@graph" : [ { "@id" : "http://example.org#comment1", "@type" : "duv:Feedback", "annotatedBy" : "http://example.org#laufer", "oa:hasBody" : "Written in MS-DOS text format.", "hasTarget" : "http://example.org#dataset-03312004" }, { "@id" : "http://example.org#comment2", "@type" : "duv:Feedback", "duv:hasRating" : "3 Star", "oa:hasBody" : "Linked Data Rating", "hasTarget" : "http://example.org#dataset-03312004" }, { "@id" : "http://example.org#dataset-03312004", "@type" : "dcat:Dataset", "dct:title" : "Mars Quarterly Temperature Plot" }, { "@id" : "http://example.org#laufer", "@type" : "duv:Person", "foaf:givenName" : "Laufer", "mbox" : "mailto:laufer@example.org" } ], "@context" : { "title" : { "@id" : "http://purl.org/dc/terms#title", "@type" : "http://www.w3.org/2001/XMLSchema#string" }, "hasRating" : { "@id" : "http://www.w3.org/ns/duv#hasRating", "@type" : "http://www.w3.org/2001/XMLSchema#string" }, "hasBody" : { "@id" : "http://www.w3.org/ns/oa#hasBody", "@type" : "http://www.w3.org/2001/XMLSchema#string" }, "hasTarget" : { "@id" : "http://www.w3.org/ns/oa#hasTarget", "@type" : "@id" }, "annotatedBy" : { "@id" : "http://www.w3.org/ns/oa#annotatedBy", "@type" : "@id" }, "givenName" : { "@id" : "http://xmlns.com/foaf/0.1/givenName", "@type" : "http://www.w3.org/2001/XMLSchema#string" }, "mbox" : { "@id" : "http://xmlns.com/foaf/0.1/mbox", "@type" : "@id" }, "oa" : "http://www.w3.org/ns/oa#", "dct" : "http://purl.org/dc/terms#", "duv" : "http://www.w3.org/ns/duv#", "rdf" : "http://www.w3.org/1999/02/22-rdf-syntax-ns#", "rdfs" : "http://www.w3.org/2000/01/rdf-schema#", "dcat" : "http://www.w3.org/ns/dcat#", "foaf" : "http://xmlns.com/foaf/0.1/" } }

Example 3 - Citation: A technical report :paperA identified by a DOI cites the dataset. The :dataset-03312013 Citation:  Citation characterization where memoradum is also identified by a digital object identifier (DOI). policy.

@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; . 
     
ex:timetable-memorandum
      a biro:BibliographicReference;
      a fabio:Policy  ;
      dct:bibliographicCitation
      "Costello, E. Mayor (2015). City Timetable Schedule Change Memorandum Effective 
      January 1, 2015. Sept 15, 2014. DOI:0.3456/4567.21"^^xsd:string ;
      biro:references ex:timetable-001 .


ex:memorandum-cites-dataset
      a cito:CitationAct ;
      cito:hasCitingEntity ex:timetable-memorandum ;
      cito:hasCitedEntity ex:timetable-001 .
{ "@graph" : [ { "@id" : "http://example.org#dataset-03312013", "@type" : "dcat:Dataset", "dct:alternative" : { "@language" : "en", "@value" : "Qtrly Temp Plot" }, "created" : "2013-03-31T15:18:00Z", "dct:creator" : "Laufer", "dct:description" : { "@language" : "en", "@value" : "This plot features average surface temperatures measured by the Mars Land Rover. " }, "dct:identifier" : "doi:10.1038/ex2158", "language" : "http://www.lexvo.org/page/iso639-3/eng", "license" : "http://creativecommons.org/licenses/by-sa/3.0/", "dct:title" : { "@language" : "en", "@value" : "Mars Quarterly Temperature Plot" }, "isCitedAsDataSourceBy" : "http://example.org#paperA", "dcat:keyword" : "Mars" }, { "@id" : "http://example.org#paperA", "@type" : "foaf:document", "dct:identifier" : "doi:20.1055/ex7758", "dct:title" : { "@language" : "en", "@value" : "Mars Weather Technical Report" }, "cites" : "http://example.org#dataset-03312004" }, { "@id" : "http://example.org#thisCitation", "@type" : "duv:DataCitation", "hasCitedEntity" : "http://example.org#paperA", "" : "http://example.org#dataset-03312004" } ], "@context" : { "identifier" : { "@id" : "http://purl.org/dc/terms#identifier", "@type" : "http://www.w3.org/2001/XMLSchema#string" }, "title" : { "@id" : "http://purl.org/dc/terms#title", "@type" : "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString" }, "cites" : { "@id" : "http://www.w3.org/ns/duv#cites", "@type" : "@id" }, "creator" : { "@id" : "http://purl.org/dc/terms#creator", "@type" : "http://www.w3.org/2001/XMLSchema#string" }, "keyword" : { "@id" : "http://www.w3.org/ns/dcat#keyword", "@type" : "http://www.w3.org/2001/XMLSchema#string" }, "isCitedAsDataSourceBy" : { "@id" : "http://purl.org/spar/cito#isCitedAsDataSourceBy", "@type" : "@id" }, "alternative" : { "@id" : "http://purl.org/dc/terms#alternative", "@type" : "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString" }, "created" : { "@id" : "http://purl.org/dc/terms#created", "@type" : "http://www.w3.org/2001/XMLSchema#dateTime" }, "language" : { "@id" : "http://purl.org/dc/terms#language", "@type" : "@id" }, "license" : { "@id" : "http://purl.org/dc/terms#license", "@type" : "@id" }, "description" : { "@id" : "http://purl.org/dc/terms#description", "@type" : "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString" }, "" : { "@id" : "http://purl.org/spar/cito#", "@type" : "@id" }, "hasCitedEntity" : { "@id" : "http://purl.org/spar/cito#hasCitedEntity", "@type" : "@id" }, "oa" : "http://www.w3.org/ns/oa#", "dct" : "http://purl.org/dc/terms#", "duv" : "http://www.w3.org/ns/duv#", "rdf" : "http://www.w3.org/1999/02/22-rdf-syntax-ns#", "xsd" : "http://www.w3.org/2001/XMLSchema#", "rdfs" : "http://www.w3.org/2000/01/rdf-schema#", "dcat" : "http://www.w3.org/ns/dcat#", "foaf" : "http://xmlns.com/foaf/0.1/", "cito" : "http://purl.org/spar/cito#" } } 9. DUV Requirements Issue 6 Right now this section is somewhat of

Example 4 - Feedback:  Providing a duplication of the use case requirements. It would better fit into this document if we described HOW the DUV fulfills these requirements. Issue-219 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. R-TrackDataUsage It should be possible mechanism for consumers 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 comment 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 ask the time. dataset publisher questions.

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 
      
ex:timetable-001
      a dcat:Dataset;
      dct:title "Bus timetable of MyCity"^^xsd:string;
      dct:issued "2015-05-05"^^xsd:date;
      dct:publisher ex:transport-agency-mycity ;
      dcat:distribution ex:timetable-001-csv;
      .

ex:timetable-001-csv
      a dcat:Distribution;
      dct:title "CSV distribution MyCity_busTimetable dataset."^^xsd:string ;
      dct:description "CSV distribution of the bus timetable 
                       dataset of MyCity."^^xsd:string ;
      dcat:mediaType "text/csv"^^xsd:string;
      .

ex:comment1Content a cnt:ContentAsText ;
      cnt:chars "This timetable is missing route 3"^^xsd:string .

ex:comment1
       a duv:UserFeedback ;
       oa:hasBody ex:comment1Content ;
       oa:hasTarget ex:timetable-001 ;
       dct:creator ex:localresident .

ex:comment2Content a cnt:ContentAsText ;
      cnt:chars "Are tab delimited formats also available?"^^xsd:string .

ex:comment2
       a duv:UserFeedback ;
       oa:hasTarget ex:timetable-001-csv;
       oa:hasBody ex:comment1Content ;
       dct:creator ex:localresident ;
    .

ex:localresident
       a foaf:Person  ;
       foaf:Name "Alan Law"^^xsd:string  ;
    .

Example 5:  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 - Dataset publisher provides information about use of this data will determined impact of this framework. Usage of this data MUST lead to future publications of less heterogenous data and more and more used of standardised thesauri. 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 how consumers can be recommended to future users. RDESC Data is published in Linked Data Format for discovery and use a particular distribution. 

      


ex:timetable-001-csv
    a dcat:Distribution;
    dct:title "CSV distribution MyCity_busTimetable dataset."^^xsd:string ;
    dct:description "CSV distribution of the bus timetable dataset of MyCity."^^xsd:string ;
    dcat:mediaType "text/csv"^^xsd:string;
    .

ex:release-notes a duv:Usage;
  dct:title "New timetable format";
  dct:created "20-DEC-2014" ;
  dct:description "The previous proprietary format has been replaced with a 
                  CVS format to take advantage of new off the shelf tools"^^xsd:string ;
 .

Example 6 - Data Usage:  Dataset publisher provides recommendations of related datasets. Capability to keep track of its usage will list all the tools and application suitable to about a bus route calculator that can 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. timetable distribution. 

      

ex:timetable-001-csv
      a dcat:Distribution;
      dct:title "CSV distribution MyCity_busTimetable dataset."^^xsd:string ;
      dct:description "CSV distribution of the bus timetable dataset of MyCity."^^xsd:string;
      dcat:mediaType "text/csv"^^xsd:string;
.

ex:route-calculator a duv:UsageTool;
    dct:title "Route Calculator"^^xsd:string;
    dct:created "15-FEB-2004"^^xsd:date ;
    dct:uri <http://example.org/route-calculator> .

    ex:release-notes a duv:Usage;
    dct:title "New timetable format"^^xsd:string;
    dct:created "20-DEC-2014"^^xsd:date ;
    duv:hasUsageTool ex:route-calculator ;
.

UKOpenResearchForum Data is published with intelligent openness to support research projects. Capability to track data usage will provide adequate acknowledgement to data originator. 9. Future Work

R-UsageFeedback

Data consumers should have a way of sharing feedback and rating data. This section is non-normative.

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 In the profile of near future,  the user who uses it. R-UsageFeedback should also provide a way to communicate suggested corrections and update editors want to internationalize the datasets by terms in 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. DUV as broadly as possible.  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 technical note this DUV activity officially concludes July 2016 according to crowdsource discrepancies in the vocabularies  used to describe datasets. LusTRE Data multilingualism is one of on 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 Web Best Practices (DWBP) Working Group Schedule.  It is useful to assess metadata quality. Availability of the source datasets, Correctness of persistent URI, Correctness opinion of the DUV editors that the concepts defined in RDESC such as FOAF Agents, Organizations, Physical Properties and Usability of the search interface can be captured in user feedback. R-Citable It should be possible to cite data on the Web. Use Case R-Citable Benefits Open Experimental Field Studies Various experiments usage, feedback, and fields studies citation are performed to generate data which is used in computational models still evolving 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 are considering forming 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. A. Acknowledgements The editors wish W3C Community Group to thank Silvio Peroni, University focus on: 1) the application 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. B. Change history Changes since the previous version include: The following classes used to describe usage were removed: prov:Activity and duv:Application. New classes were included to represent usage: duv:Usage, duv:UsageActor and duv:UsageTool. Two new classes were included to describe user feedback: duv:UserQualityFeedback and duv:RatingFeedback. foaf:document was replaced by dct:BibliographicResource The citation model was completely revised 2) based on future external community feedback make formal requests to reuse the Semantic Publishing and Referencing (SPAR) ontologies. duv:WebThing was removed. foaf:Agent was included together with some properties that complements the description of dcat:Dataset and dcat:Distribution. skos:Concept is being used to represent: usage type, usage actor roles, citation agent role and rating feedback. Examples were updated W3C to reflect the new model. The continue making minor vocabulary specification was updated to reflect the model updates. revisions.

C. A. References

C.1 A.1 Informative references

[CITO]
David Shotton; Silvio Peroni. CiTO, the Citation Typing Ontology . URL: http://purl.org/spar/cito
[DC-TERMS]
Dublin Core Metadata Initiative. Dublin Core Metadata Initiative Terms, version 1.1. 11 October 2010. DCMI Recommendation. URL: http://dublincore.org/documents/2010/10/11/dcmi-terms/ .
[DWBP-UCR]
Deirdre Lee; Bernadette Farias Loscio; Phil Archer. W3C. Data on the Web Best Practices Use Cases & Requirements . 24 February 2015. W3C Note. URL: http://www.w3.org/TR/dwbp-ucr/
[EmoryUCite]
Emory University. General Citation Guidelines . URL: http://einstein.library.emory.edu/citations_general.html
[FORCE11-Citation]
Emory University. Data Citation Principles . URL: https://www.force11.org/group/joint-declaration-data-citation-principles-final
[FaBIO]
David Shotton; Silvio Peroni. FaBiO, the FRBR-aligned Bibliographic Ontology . URL: http://purl.org/spar/fabio
[MSUDataCite]
Michigan State University. How to Cite Data: General Info . URL: http://libguides.lib.msu.edu/citedata
[OA]
Herbert Van de Sompel; Paolo Ciccarese; Robert Sanderson. Open Annotation Data Model . URL: https://www.w3.org/ns/oa#
[SPAR]
Semantic Publishing and Referencing (SPAR) Ontologies . URL: http://www.sparontologies.net
[VOCAB-DCAT]
Fadi Maali; John Erickson. W3C. Data Catalog Vocabulary (DCAT) . 16 January 2014. W3C Recommendation. URL: http://www.w3.org/TR/vocab-dcat/