W3C home > Mailing lists > Public > public-gld-wg@w3.org > February 2013

Using versionable artefacts in SDMX-ML

From: Sarven Capadisli <sarven.capadisli@deri.org>
Date: Wed, 20 Feb 2013 22:30:02 +0100
Message-ID: <5125405A.4060603@deri.org>
To: Government Linked Data Working Group WG <public-gld-wg@w3.org>

If there is a backlog on the following, pointers are appreciated. While 
working on SDMX-ML transformations, versioning artefacts came up. This 
is about using RDF properties which corresponds to them.

SDMX-ML publishers use @version, and sometimes accompanied with 
@validFrom and @validTo on CodeLists and Codes. I think their 
explanations are self-evident without diving too deep into that for the 
moment. Those attributes and their values are referenced by the 
components in Data Structure Definitions. As classifications evolve over 
time, version and validity information reflects those changes.

As far as I know, there are no corresponding RDF properties for version, 
validFrom and validTo in SDMX-RDF.

The best "version" like property that I can think of (and do use) is 
owl:versionInfo. That's fine for now I guess.

validFrom and validTo is a bit more tricky. It would be nice to have 
them satisfy the following:

* have range URI (e.g., to use UK refPeriods URI)
* be datayped with xsd's time periods

I think the separation of validFrom and validTo is necessary as either 
or both may be available.

See also [1].

Would it make sense to have sdmx-concepts for these? Would other 
properties be welcome? :) e.g., isFinal

[1] http://chatlogs.planetrdf.com/swig/2013-02-08.html#T10-57-26

Received on Wednesday, 20 February 2013 21:30:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:52:05 UTC