Skip to content

Commit

Permalink
Merge branch 'dcat-issue72' of https://github.com/w3c/dxwg into dcat-…
Browse files Browse the repository at this point in the history 
…issue72
  • Loading branch information
@agbeltran
agbeltran committed Mar 19, 2019
2 parents c10d00f + 1b485ba commit 21fac05
Show file tree
Hide file tree
Showing 13 changed files with 1,375 additions and 1,018 deletions.
10 changes: 10 additions & 0 deletions conneg-by-ap/config.js
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39,9 +39,19 @@ var respecConfig = {
wgPatentURI: "https://www.w3.org/2004/01/pp-impl/99375/status",
inlineCSS: "true",
lint: "false",
maxTocLevel: 3,
issueBase: "https://github.com/w3c/dxwg/issues/",
github: "https://github.com/w3c/dxwg/",
localBiblio: {
"ARK" : {
editors: ["J. Kunze",
"R. Rodgers"
],
href: "https://tools.ietf.org/id/draft-kunze-ark-15.txt",
title: "The ARK Identifier Scheme" ,
date: "2008-05-22",
status: "Internet-Draft"
},
"PROF-CONNEG": {
editors: [
"Lars G. Svensson",
Expand Down
540 changes: 438 additions & 102 deletions conneg-by-ap/index.html
View file

Large diffs are not rendered by default.

Binary file modified dcat/UML/DCAT-summary-all-attributes.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
42 changes: 23 additions & 19 deletions dcat/config.js
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,10 @@ var respecConfig = {
edDraftURI: "https://w3c.github.io/dxwg/dcat/",
// issueBase: "https://github.com/w3c/dxwg/issues/", -- Not needed when github used
editors: [{
name: "Alejandra Gonzalez Beltran",
company: "Oxford eResearch Centre, Engineering Science, University of Oxford",
url: "https://www.oerc.ox.ac.uk/people/alejandra",
companyURL: "http://www.oerc.ox.ac.uk/"
name: "Riccardo Albertoni",
company: "CNR - Consiglio Nazionale delle Ricerche, Italy",
url: "http://www.imati.cnr.it/joomla/index.php/people/8-curricula/178-riccardo-albertoni",
companyURL: "http://www.cnr.it/"
},{
name: "Dave Browning",
company: "Refinitiv",
Expand All @@ -24,23 +24,27 @@ var respecConfig = {
url: "http://people.csiro.au/Simon-Cox",
companyURL: "https://www.csiro.au/"
},{
name: "Peter Winstanley",
company: "Scottish Government",
companyURL: "http://www.gov.scot/"
name: "Alejandra Gonzalez Beltran",
company: "Oxford eResearch Centre, Engineering Science, University of Oxford",
url: "https://www.oerc.ox.ac.uk/people/alejandra",
companyURL: "http://www.oerc.ox.ac.uk/"
},{
name: "Andrea Perego",
company: "European Commission, Joint Research Centre (JRC)",
url: "https://joinup.ec.europa.eu/user/14209",
companyURL: "https://ec.europa.eu/jrc/"
},{
name: "Peter Winstanley",
company: "Scottish Government",
companyURL: "http://www.gov.scot/"
}],
otherLinks: [{
// key: "Contributors",
// data: [{
// value: "Makx Dekkers",
// href: "http://www.makxdekkers.com"
// },{
// value: "Antoine Isaac, Europeana Foundation",
// href: "https://pro.europeana.eu/person/antoine-isaac"
// },{
// value: "Andrea Perego, European Commission",
// href: "https://ec.europa.eu/jrc/"
// }]
// },{
key: "Contributors",
data: [{
value: "Makx Dekkers",
href: "http://www.makxdekkers.com"
}]
},{
key: "Editors of previous version",
data: [{
value: "Fadi Maali, DERI",
Expand Down
210 changes: 166 additions & 44 deletions dcat/index.html
View file

Large diffs are not rendered by default.

28 changes: 28 additions & 0 deletions dcat/rdf/dcat.ttl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -829,6 +829,30 @@ dcat:service
skos:changeNote "New property in this revision of DCAT" ;
skos:editorialNote "Status: Property accepted by DCAT revision team, but details of definition and constraints not yet resolved." ;
.
dcat:spatialResolutionInMeters
rdf:type owl:DatatypeProperty ;
rdfs:comment "minimum spatial separation resolvable in a dataset, measured in meters"@en-US ;
rdfs:comment "minimum spatial separation resolvable in a dataset, measured in metres"@en-GB ;
rdfs:label "spatial resolution (meters)"@en-US ;
rdfs:label "spatial resolution (metres)"@en-GB ;
rdfs:range xsd:decimal ;
skos:changeNote "New property in this revision of DCAT" ;
skos:editorialNote "Status: details of definition and constraints not yet resolved." ;
skos:editorialNote "Might appear in the description of a Dataset or a Distribution, so no domain is specified" ;
skos:scopeNote "If the dataset is an image or grid this should correspond to the spacing of items. For other kinds of spatial dataset, this property will usually indicate the smallest distance between items in the dataset. " ;
skos:scopeNote "Alternative spatial resolutions might be provided as different dataset distributions" ;
.
dcat:temporalResolution
rdf:type owl:DatatypeProperty ;
rdfs:comment "minimum time period resolvable in a dataset" ;
rdfs:label "temporal resolution" ;
rdfs:range xsd:duration ;
skos:changeNote "New property in this revision of DCAT" ;
skos:editorialNote "Status: Property accepted by DCAT revision team, but details of definition and constraints not yet resolved." ;
skos:editorialNote "Might appear in the description of a Dataset or a Distribution, so no domain is specified" ;
skos:scopeNote "If the dataset is a time-series this should correspond to the spacing of items in the series. For other kinds of dataset, this property will usually indicate the smallest time difference between items in the dataset. " ;
skos:scopeNote "Alternative temporal resolutions might be provided as different dataset distributions" ;
.
dcat:theme
rdf:type rdf:Property ;
rdf:type owl:ObjectProperty ;
Expand Down Expand Up @@ -887,6 +911,10 @@ dcat:themeTaxonomy
rdfs:label "テーマ"@ja ;
rdfs:range skos:ConceptScheme ;
.
dct:accrualPeriodicity
skos:definition "The frequency at which dataset is published." ;
skos:scopeNote "The value of dct:accrualPeriodicity gives the rate at which the dataset-as-a-whole is updated. This may be complemented by dcat:temporalResolution to give the time between collected data points in a time series." ;
.
prov:qualifiedAttribution
skos:definition "Link to an Agent having some form of responsibility for the resource" ;
skos:scopeNote """Used to link to an Agent where the nature of the relationship is known but does not match one of the standard Dublin Core properties (dct:creator, dct:publisher).
Expand Down
96 changes: 77 additions & 19 deletions profiles/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -128,13 +128,12 @@ <h3>Definitions</h3>
</dd>
</dl>
<div class="issue" data-number="448"></div>
<div class="issue" data-number="418"></div>
</section>


<section id="motivation">
<h3>The motivation for profiles</h3>
<p>
<p>
Communities create and use data standards to ensure interoperability for information exchange. Although members
of a community may use the same basic standard schema, it is very common for different subsets within the larger
community to need some further specification of the data they create to meet their own needs. To continue to
Expand All @@ -143,6 +142,16 @@ <h3>The motivation for profiles</h3>
cardinality, and validation rules, and can also include descriptions of the rules used by creators to make
decisions regarding their data elements.
</p>
<p>
In the <a href="https://www.w3.org/TR/dcat-ucr/">DXWG use case and requirements document</a> [[DCAT-UCR]], our group
has identified typical use cases for profiles, such as:
</p>
<ul>
<li><a href="https://w3c.github.io/dxwg/ucr/#ID7">support associating fine-grained semantics for datasets and resources within a dataset</a></li>
<li><a href="https://w3c.github.io/dxwg/ucr/#ID41">expression of vocabulary constraints</a>, and</li>
<li><a href="https://w3c.github.io/dxwg/ucr/#ID46">support for input functions</a></li>
</ul>
</p>
</section>


Expand All @@ -151,19 +160,19 @@ <h3>Examples of profiles and related work</h3>
<p>
Profiles can take a number of forms and can have a variety of relationships to existing vocabularies,
standards, and other profiles. We recognise this variety, but for the purposes of this document we are focusing
on the most general forms of profile and profiling. Although it is not possible to list all of the types
on the most general forms of profiles and profiling. Although it is not possible to list all of the types
of profiles, some illustrations of frequently-used profiles include:
</p>
<ul>
<li>
profiles that are subsets of a larger vocabulary. These reduce the vocabulary terms of a broad data
<strong>profiles that are subsets of a larger vocabulary</strong>. These reduce the vocabulary terms of a broad data
standard to a smaller number of terms that are useful for a particular community member or application.
An example of this is <a href="http://bibfra.me/">BIBFRA.me</a>, which is designed for library materials and defines
both a core set of terms as well as profiles for specialized communities such as cataloging of rare materials
or early printing trade. In this community, all profiles use only terms from a single vocabulary.
</li>
<li>
profiles that can both reduce and extend a base standard. These profiles are developed by members of a
<strong>profiles that can both reduce and extend a base standard</strong>. These profiles are developed by members of a
data-sharing community but for reasons of jurisdiction or specialization need to add terms beyond the base
standard vocabulary in order to meet their needs. They may also omit terms from the base standard that are not
relevant to their implementations. An example of this is data catalog vocabulary standard, DCAT, its primary
Expand All @@ -172,15 +181,15 @@ <h3>Examples of profiles and related work</h3>
variant. These profiles generally make use of terms from more than one namespace.
</li>
<li>
profiles that amend a base standard by inheriting or overriding values of that standard. The example here
<strong>profiles that amend a base standard by inheriting or overriding values of that standard</strong>. The example here
is of the Open Digital Rights Language (ODRL) which is a language to support rights in the use of digital
content in publishing, distribution, and consumption of digital media. The ODRL language encodes a policy
that has a core vocabulary that can be extended or overridden by individual instances called "profiles."
<div class="issue" data-number="368"></div>
</li>
<li>
profiles that use some vocabulary terms from multiple standards without having a strong relationship to any
base standard. These profiles develop new groupings of existing terms as vocabularies and may define new
<strong>profiles that use some vocabulary terms from multiple standards without having a strong relationship to any
base standard</strong>. These profiles develop new groupings of existing terms as vocabularies and may define new
terms as needed. An example of this is the Asset Description Metadata Schema (ADMS) vocabulary [[vocab-adms]]
</li>
</ul>
Expand All @@ -199,19 +208,53 @@ <h3>Examples of profiles and related work</h3>


<section id="whatisaprofile">
<h2>Profiles defined</h2>
<p>This section builds on the formal definition for <a>profile</a> and the requirements DXWG has identified, and lays down a conceptual model for profiles, their components
and their functions.</p>
<p>A Profile is based on an existing Specification, which can have the status of a Standard and which can be itself
<h2>Diving into profiles</h2>
<p>This section builds on the formal definition for <a>profile</a> as well as the requirements the W3C Data Exchange Working Group (DXWG) has identified, and lays down a conceptual model for profiles, their components
and their functions.
</p>
<p>Its goal is to establish a general view of profiles that supports the many potentially more specific examples
in practice. Usages of the term 'profile' in other contexts may not be consistent with these requirements,
and are thus out of scope.
</p>
<p>A Profile is based on an existing Specification, which can have the status of a Standard and which can itself be
a Profile of another Specification. A profile can have various Components/Manifestations in various expression languages for profiles.
These Components/Manifestations play specific Functions (roles) for the implementation of the services that motivate the creation of the Profile.
These Components are serialized and published as Distributions in various formats, which are the concrete input for performing these services.
</p>

<div class="note">
<p>
The terminology in this section is still under discussion, e.g. <a href="https://github.com/w3c/dxwg/issues/747">here</a> or
<a href="https://github.com/w3c/dxwg/issues/795">here</a>
</p>
</div>

<p>The profile may be expressed in a single specification, or it may consist of more than one component.
For example, a profile may have a vocabulary in the form of a schema (such as OWL or XML schema), as
well as a text file containing documentation for persons doing data creation, and actionable validation code,
such as a ShEx or SHACL document. Components may be added or removed without changing the fact that the profile
meets the definition of a profile as stated in this document. A profile can exist independently of the set of
resources that is used to describe it.
</p>
<div class="issue" data-number="597"></div>

<section class="requirement" id="RPFNCTERMS">
<h3>Profiles are named collections of properties</h3>
<h3>Profiles are uniquely named sets of data constraints, such as data elements (e.g. classes, properties, value domains) that describe (meta)data.
</h3>
<!--<h3>Named collections of terms [RPFNCTERMS]</h3>-->
<p>Profiles SHOULD be made up of a collection of properties or terms, and that collection SHOULD have a name. Properties are selected from existing vocabularies. Because profiles as being described here are not limited to those in RDF, collections could be of metadata terms from any type of metadata schema.</p>

<p>
When building a profile you SHOULD give it a name and you SHOULD build it from properties or terms that
you have collected from pre-existing sources. Because we are considering a wide range of profiles,
not just those in RDF, collections could be of metadata terms from any type of metadata schema, but
they might also include collections of identifiers, value lists and enumerations, other data elements,
and anything else that might be helpful in ensuring that the data matches the purpose intended by you
and your community
</p>
<div class="note">
<p>In our context, <em>constraints</em> is a general notion, which includes specification of optional data elements.
</p>
</div>
<div class="issue" data-number="275"></div>
<div class="note"><p>It could also be in roles/functions if there is nothing there about defining terms. Antoine Isaac, 2018-11-11
</p></div>
Expand All @@ -221,7 +264,7 @@ <h3>Profiles are named collections of properties</h3>
<section class="requirement" id="RPFMBSPEC">
<h3>Multiple base specifications [RPFMBSPEC]</h3>
<p>A profile can have multiple base specifications.</p>
<a target="_blank" rel="nofollow" class="external free" href="https://github.com/w3c/dxwg/issues/268">github:issue/268</a>
<div class="issue" data-number="268"></div>
</section>

<section class="requirement" id="RPFPP">
Expand Down Expand Up @@ -371,8 +414,7 @@ <h3>Cardinality rules [RPFCARDR]</h3>

<section class="requirement" id="RPFDEPR">
<h3>Dependency rules [RPFDEPR]</h3>
<p>Profiles may express dependencies between elements of the vocabulary (if A then not B, etc.).</p>
<a target="_blank" rel="nofollow" class="external free" href="https://github.com/w3c/dxwg/issues/278">github:issue/278</a>
<div class="issue" data-number="278"></div>
</section>

<section class="requirement" id="RPFUI">
Expand Down Expand Up @@ -622,7 +664,7 @@ <h2>Appendices</h2>
<!-- A list of issues will magically appear here -->
</section>

<section id="definitions">
<section id="appendix-definitions">
<h3>Definitions</h3>
<dl>
<dt><dfn>formalism</dfn></dt>
Expand All @@ -646,8 +688,24 @@ <h3>Definitions</h3>
</p>
<p><em>Source: [[DCTERMS]]</em>.</p>
</dd>
<dt><dfn>specification</dfn></dt>
<dd>
<p></p>
</dd>
<dt><dfn>Base specification</dfn></dt>
<dd>
<p>A specification MAY assume a role of being a base specification, which is the foundation of the profile.
</p>
</dd>
<dt><dfn>Constraint</dfn></dt>
<dd>
<p></p>
</dd>
<dt><dfn>Data element</dfn></dt>
<dd>
<p></p>
</dd>
</dl>
<div class="issue" data-number="371"></div>
<div class="issue" data-number="418"></div>
</section>

Expand Down
Loading

0 comments on commit 21fac05

Please sign in to comment.