Advanced search
Discover and download new StatDCAT-AP release 1.0.1!
We would like to announce the update of the StatDCAT Application Profile for data portals in Europe (StatDCAT-AP) and share with you the highlights of this release! What’s new? This new version 1.0.1…
NEWSCreated: 28/05/2019Updated Date: 28/05/2019
StatDCAT-AP bug fix release – Share your comments!
Dear StatDCAT-AP community, We would like to inform you about the recent update of the StatDCAT Application Profile for data portals in Europe (StatDCAT-AP). This updated version implements bug fix…
NEWSCreated: 10/05/2019Updated Date: 10/05/2019
Support for qb:measure?
STATDCAT currently provides properties to associate attributes and dimensions with datasets. It also allows the unit of measurement for the measure dimension to be specified. But it doesn't allow the measure itself to be referenced. A DataCube DataStructureDefinition allows attributes, measures and…
DISCUSSIONCreated: 12/01/2017Updated Date: 12/01/2017
Namespace URI still to be finalised?
The 1.0.0 specification still says that the STAT-DCAT namespace URI is still to be decided. I'm keen to start experimenting with publishing data using the new vocabulary. When will the namespace URI be confirmed, or where can I find the final URI? Thanks, L. Component Documentation Category bug
DISCUSSIONCreated: 12/01/2017Updated Date: 12/01/2017
Full RDF expression of an existing reference metadata standard
It might be more insightful to have a full RDF (based on a combination of statDCAT and other vocabularies/ontologies) expression of an existing reference metadata standard, i.e the SIMS. Here we have a partial metadaset that incorporates in the SDMX expression DCAT properties which is not that much…
DISCUSSIONCreated: 31/10/2016Updated Date: 31/10/2016
Typo DVAT
On page 61, "DVAT" should be "DCAT". Issue raised by Guillaume Duffes INSEE by e-mail on 28 October 2016 at http://joinup.ec.europa.eu/mailman/archives/stat_dcat_application_profile/2016-October/000090.html Component Documentation Category bug
DISCUSSIONCreated: 31/10/2016Updated Date: 31/10/2016
Modelling SDMX Metadataflow in StatDCAT-AP
[Annex II]: The statDCAT-AP model maps indeed well to the SDMX Dataflow, and then is very useful to represent the SDMX data and structural metadata. However, the SDMX Metadatalow is not modelled in statDCAT-AP. An extension could include a representation of the Metadataflow and the related metadata…
DISCUSSIONCreated: 31/10/2016Updated Date: 31/10/2016
Property stat:statMeasure is confusing
[Section 6.7.3] The stat:statMeasure property is very confusing since it designates actually an unit of measurement. A qb:MeasureProperty gives the value for each information. It is conformant with the SDMX definition of the measure. In parallel, QB defines an unit measure attribute which qualifies…
DISCUSSIONCreated: 31/10/2016Updated Date: 31/10/2016
Review definition of the numSeries property
[Section 6.2.4] The definition of the numSeries property should be reviewed in a more formal manner. If not mistaken, it is the Cartesian Product of the number of modalities of each dimension, excluding what QB calls the measure dimension (that denotes which particular measure is being conveyed by…
DISCUSSIONCreated: 31/10/2016Updated Date: 31/10/2016
SIMS as part of the StatDCAT vocabulary
[Section 6.2.2] : It would be indeed very interesting to have the SIMS as part of the statDCAT vocabulary. Several vocabularies of interest to the different SIMS sections can be already identified: VCARD, ORG and FOAF for S1 S2 : DCTERMS and PAV S3 : DCTERMS, QB (SDMX-...), SKOS et XKOS S4 : QB…
DISCUSSIONCreated: 31/10/2016Updated Date: 31/10/2016
stat:attribute and stat:dimension versus qb:attribute and qb:dimension
[Section 6.2.1] Why not directly use the properties qb:attribute, qb:dimension instead of creating the stat:attribute and stat:dimension properties which are identical. Issue raised by Guillaume Duffes INSEE by e-mail on 28 October 2016 at http://joinup.ec.europa.eu/mailman/archives/stat_dcat…
DISCUSSIONCreated: 31/10/2016Updated Date: 31/10/2016
Make the relationship between a dcat:Dataset and a qb:DataSet explicit
[Section 6.1] If possible, it would be good to make the relationship between a dcat:Dataset and a qb:DataSet explicit. The QB specification does not establish any formal relationship. On the contrary the DQV specification links the dcat:Dataset to the qb:DataSet through the dqv:QualityMeasurement…
DISCUSSIONCreated: 31/10/2016Updated Date: 31/10/2016