Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Background and Problem Statement

x

HTML landing pages currently under:
https://ddialliance.org/controlled-vocabularies

Architecture

Bitbucket repo at https://bitbucket.org/ddi-alliance/ddi-cv/src/main/ will hold exported data (CVs) periodically exported from CESSDA

XKOS Links/URIs:

Metadata Profile (CVS<>RDF<>DDI-L)

Based on analysis on 07/01/2022 of content under:
https://vocabularies.cessda.eu/vocabulary/AggregationMethod?lang=en

Sort#

CVS UI Label

Example value in CVS

CVS SKOS Class

CVS RDF Property

@lang attribute

DDI-L Xpath

DDI Mapping Comments

1

[Main] CV name

Aggregation Method

ConceptScheme

dcterms:title

Yes

To extract from:
https://ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/logicalproduct.xsd

 

2

[Main]: CV short name

AggregationMethod

ConceptScheme

skos:notation

No

 

 

3

[Main]: CV description

dentifies the type of aggregation used to combine related categories, usually within a common branch of a hierarchy, to provide information at a broader level than the level at which detailed observations are taken. (From: The OECD Glossary of Statistical Terms)

ConceptScheme

dcterms:description

Yes

 

 

4

[Main]: CV notes

This vocabulary was first published by the DDI Alliance. Please see: https://ddialliance.org/controlled-vocabularies/all .

ConceptScheme

Not currently output

n/a

 

 

5

[Main]: Language

English (en)

ConceptScheme

Mapped to Multiple properties

n/a

 

 

6

[Main]: Version 

1.1

ConceptScheme

owl:VersionInfo

No

 

 

7

[Main]: Date of publication

2019-11-25

ConceptScheme

Not currently output to SKOS

n/a

 

 

8

NOT REPRESENTED IN UI

n/a
outputted in SKOS as
https://ddialliance.org/Specification/DDI-CV/AggregationMethod_1.1.html#PercentileRank
as an example

Concept

Concept URI

n/a

 

 

9

[Details]: Code value

PercentileRank

Concept

skos:notation

No

 

 

10

[Details]: Code descriptive term

Percentile rank

Concept

skos:prefLabel

Yes

 

 

11

[Details]: Code definition

The percentile rank of a item is the percentage of items in its frequency distribution which are lower [cannot reach 100%].

Concept

skos:definition

Yes

 

 

12

[Versions]: Version notes

  1. ArithmeticMean, CumulativePercent, PercentileRank: Descriptive term capitalization changed to make them conform to the other vocabularies. 2. Count, Mode: Period added at the end of the code definitions to make them conform to the other vocabularies.

ConceptScheme

Not currently output to SKOS

n/a

 

 

13

[Versions]: Version changes

Code descriptive term rephrased: Arithmetic Mean rephrased into Arithmetic mean
Code descriptive term rephrased: Cumulative Percent rephrased into Cumulative percent
Code descriptive term rephrased: Percentile Rank rephrased into Percentile rank
Code definition rephrased: Count
Code definition rephrased: Mode

ConceptScheme

Not currently output to SKOS

n/a

 

 

14

[Identity and general]: Canonical URI

urn:ddi:int.ddi.cv:AggregationMethod:1.1

ConceptScheme

Not currently output to SKOS

n/a

 

 

15

[Identity and general]: Canonical Agency

DDI Alliance

ConceptScheme

Not currently output to SKOS

n/a

 

 

16

[Usage]: DDI-L 3.3 Module name

reusable

ConceptScheme

Not currently output to SKOS

n/a

 

 

17

[Usage]: DDI-L 3.3 Element name

AggregationMethod /
https://ddialliance.org/Specification/DDI-Lifecycle/3.3/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/elements/AggregationMethod.html

ConceptScheme

Not currently output to SKOS

n/a

 

 

18

[Usage]: DDI-L 3.2 Module name

reusable

ConceptScheme

Not currently output to SKOS

n/a

 

 

19

[Usage]: DDI-L 3.2 Element name

AggregationMethod /
http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/elements/AggregationMethod.html

ConceptScheme

Not currently output to SKOS

n/a

 

 

20

[Usage]: DDI-L 2.5 Element/attribute name

var@otherAggrMeth
http://www.ddialliance.org/Specification/DDI-Codebook/2.5/XMLSchema/field_level_documentation_files/schemas/codebook_xsd/elements/var.html

ConceptScheme

Not currently output to SKOS

n/a

 

 

21

[Licence and citation]: Copyright © DDI Alliance 2019

This work is licensed under a Creative Commons Attribution 4.0 International - CC BY.

ConceptScheme

dcterms:license

Yes

 

 

22

[Licence and citation]: Citation

DDI Alliance. (2019). Aggregation Method (Version 1.1) [Controlled vocabulary]. CESSDA. urn:ddi:int.ddi.cv:AggregationMethod:1.1.

ConceptScheme

dcterms:rights

Yes

 

 

23

[Licence and citation]: Available from


https://vocabularies.cessda.eu/urn/urn:ddi:int.ddi.cv:AggregationMethod:1.1

ConceptScheme

ConceptScheme URI

n/a

 

 

24

NOT REPRESENTED IN UI

n/a
outputted in SKOS as
https://ddialliance.org/Specification/DDI-CV/AggregationMethod
as an example

ConceptScheme

dcterms:isVersionOf

n/a

 

 

25

NOT REPRESENTED IN UI

n/a
Hierarchy is implied by concatenation of concept chain from root e.g.
Family.HouseholdFamily code value sits under Family in https://vocabularies.cessda.eu/vocabulary/AnalysisUnit?lang=en

Concept

skos:narrower

NB - skos:broader not used explicitly in CVS SKOS output

n/a

26

NOT REPRESENTED IN UI

n/a

ConceptScheme

skos:hasTopConcept

n/a

27

NOT REPRESENTED IN UI

n/a

Concept

skos:inScheme

n/a

28

NOT CURRENTLY REPRESENTED
DDI ELEMENT/XPATH
REQUIREMENT FROM TC MEETING 03-MAR-2022 TO SPECIFY WHICH DDI ELEMENT THE CV IS USED FOR. THIS WILL ULTIMATELY ENABLE FIELD LEVEL DOCUMENTATION TO AUTOMATICALLY SPECIFY THE CV USED FOR A PARTICULAR ELEMENT

n/a

ConceptScheme

TO BE DETERMINED

n/a

Governance

Follow up on Snapshot: Concerns relating to the governance of FAIR vocabularies

Appendix 1 - Notes and Discussion Trails

 11-Nov-2021 - URI issues raised at TC

1

BaseURI needs confirmation as:
https://ddialliance.org/Specification/DDI-CV/
This needs to change - [11/11]to finalise base URI with Wendy et al**
**consider practicality of DNS resolution re ICPSR

2

URIs currently use natural language semantics, rather than IDs

Problem: How can we know that these are different versions of the same concept?
Suggest that concept ID is used instead in the URI, for example: https://ddialliance.org/Specification/DDI-CV/AnalysisUnit_1.0/8
Need to clarify with Oliver Hopt : is there anything persistent in the database that could be used for the Concept ID?
Also, can we delineate the version number in the URI (rather than underscore concatenation)

[11/11]Oliver to follow up with Sigit on ConceptIDs and segmenting versionumbers.

3

Which RDF serializations are the priority?

4

Confirm whether we need a externally available SPARQL endpoint to be made available .
[11/11]Not required in first release

5

There is not a RESTful API in place by default. Confirm this is OK.
[11/11]Not required in first release

 11-Nov-2021 - Email from Taina Jääskeläinen (FSD) 11-Nov outlining CESSDA CVS versioning model

 

From: Taina Jääskeläinen (TAU) [mailto:taina.jaaskelainen@tuni.fi]
Sent: 11 November 2021 08:38
To: Bell, Darren S <dbell@essex.ac.uk>
Subject: RE: DDI CVs and versioning

 

Hi Darren,

go to this web page and click to open the section +Versioning policy

https://ddialliance.org/controlled-vocabularies

 

This applies to source vocabularies which have two-digit version number. i.e. minor and major changes.

The translated vocabularies have a three-digit version number where the first two digits are the source version number (telling the translation of which source version it is), and the third is just a running number indicating any change.

So 3.4.2 version in a translation version means a second language version of the source version 3.4.

When the source version changes, the translations of the previous source versions are frozen and cannot be changed anymore. Any changes to target languages can only be done in the next source version.

 

The versioning of translations was one of the things we would have liked to simplify before the code base was changed to a new platform. But as we did not know the platform was being changed before the recoding had been done, it was too late.

I still don’t know what would be the best way to ensure that metadata producers learn when the term in their language has changed since ELSST-style publication once a year is not feasible.

 

Maybe keep the version number the same for all languages (i.e. the source version number) but still leave the current the language specific change history tracking  so that people could be able to see just what has changed in their version??? Don’t think it would be too hard to change the version number assignment in the system.

The risk for metadata producers is that they would not be able to track anymore whether the language version they use is kept up-to-date with the source unless they compare source and target language changes.

In the current system, if the language version is not kept up to date, the latest published version has the version number referring to the previous source version.

 

Then there would need to be another versioning concerning the whole download/API package (all languages) with version number changing whenever there is a change in any of the languages. I assume this kind of versioning would be needed for systems that have implemented a CV in their system? Even though they might not be interested in that particular language where the change was done. GESIS originally assured me that this separate ‘whole package’ technical versioning would be possible.

 

I don’t think DDI Alliance thinks that the ‘displayed’ version number of a DDI vocabulary should change if the Greek change one descriptive term. But I may have interpreted things wrong.

 

It gets complicated when there are the requirements of 1) metadata producers, 2) DDI Alliance, 3) multilingual data catalogues, 4) linked data. And my technical expertise is, as known, not very great.

 

 

BTW: We had a meeting yesterday with the Slovak team taking over the CVS technical development.

Resolving issues preventing linked open data and resolvable URIs are important issues. Do you think Carsten and John know what is required re those?

 

All the best,

Taina

 

From: Bell, Darren S <dbell@essex.ac.uk>
Sent: 10 November 2021 16:10
To: Taina Jääskeläinen (TAU) <taina.jaaskelainen@tuni.fi>
Subject: DDI CVs and versioning

 

Hi Taina – as you may be aware,  I’m working with Oliver Hopt at GESIS to make the DDI CVs available as SKOS.   I’m trying to find more detail about how versioning is currently handled in CESSDA CV Manager and what triggers a major or a minor version.  Are there any documents/specifications related to versioning in the CVS that I could get access to?

Best, Darren

 21-Oct-2021 - Notes/Requirements from Wendy 21-Oct

 

From: Wendy Thomas [mailto:wlt@umn.edu]
Sent: 21 October 2021 16:18
To: Bell, Darren S <dbell@essex.ac.uk>; Hopt, Oliver <Oliver.Hopt@gesis.org>
Subject: Questions regarding support of ddi rdf vocabulary resolution

 

OK this is really a brain dump of things that made me go hmmm and may or may not be issues that need to be addressed. So first I'd like to know which I don't need to worry about, which will be addressed by your work, and which we need to resolve either within TC or in conjunction with other product groups. 

Thanks, Wendy

 

Right now this domain is managed by ICPSR(Michael) rdf-vocabulary.ddialliance.org
Should this be the URL associated with int.ddi? or should each product have its own subagency (ddi.lifecycle, ddi.codebook, ddi.xkos, ddi.cdi, ddi.sdtl)
Does SDTL currently use a URN or just the rdf-vocabulary.ddialliance.org?

XKOS
RDF namespace: http://rdf-vocabulary.ddialliance.org/xkos#
XKOS documentation: http://rdf-vocabulary.ddialliance.org/xkos.html
RDF Turtle file: https://rdf-vocabulary.ddialliance.org/xkos.ttl

Controlled Vocabularies (note that Controlled vocabularies has its own subagency which is actually "int.ddi.cv"
Short Name:AggregationMethod
Long Name:Aggregation Method
Version:1.0
Version Notes:
Canonical URI:urn:ddi-cv:AggregationMethod
Canonical URI of this version:urn:ddi-cv:AggregationMethod:1.0
Location URI:http://www.ddialliance.org/Specification/DDI-CV/AggreagationMethod_1.0_Genericode1.0_DDI-CVProfile1.0.xml
Alternate format location URI:http://www.ddialliance.org/Specification/DDI-CV/AggregationMethod_1.0.html
Alternate format location URI:http://www.ddialliance.org/Specification/DDI-CV/AggregationMethod_1.0_InputSheet_Excel2003.xls

Note that the current URI's are in error and do not/will not resolve
What needs to be done about this? Short term, long term

  • No labels