Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to reference a specific version of a vocabulary? #112

Open
lorenae opened this issue Jul 27, 2015 · 4 comments
Open

How to reference a specific version of a vocabulary? #112

lorenae opened this issue Jul 27, 2015 · 4 comments

Comments

@lorenae
Copy link

lorenae commented Jul 27, 2015

Hi:
Suppose I have an RDFS vocabulary for which I have different versions that correspond to the evolution of the vocabulary. I would like to know if there is any recommendation on how to to add a reference to a specific version of a certain vocabulary.

In the vocabulary, I'm using owl:versionInfo to state the version number, and in the dataset I may use void:vocabulary to link the dataset with the vocabulary, but I couldn't find how to refer to a certain version.

The situation I'm dealing with is similar to the one described here: http://answers.semanticweb.com/questions/2815/how-do-i-knowmodel-the-applied-version-of-an-ontology-specification

Thanks in advance,
Lorena

@gatemezing
Copy link

@lorenae
Copy link
Author

lorenae commented Aug 7, 2015

Hi Ghislain:

thanks for your reply.

Your suggestion seems ok in order to record a set of available versions or
distributions of a vocabulary, although I think it forces a bit the
definition of dcat:Distribution. According to DCAT documentation this class
refers to "the same content in different formats" ( see
http://www.w3.org/TR/vocab-dcat/#class-distribution "Represents a specific
available form of a dataset. Each dataset might be available in different
forms, these forms might represent different formats of the dataset or
different endpoints. Examples of distributions include a downloadable CSV
file, an API or an RSS feed")

But I also want to add the version info to specific RDF datasets that use
the vocabulary.

For example, suppose I have two different RDF datasets that use cogs
vocabulary. One of these datasets uses the terms as defined in
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2013-11-25.n3, and the
other refers to
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2014-03-10.n3
I want to be able to record this and distinguish which version is used in
each RDF dataset.

any suggestions on how to represent this?

best regards,
Lorena

On Wed, Aug 5, 2015 at 10:10 AM, Ghislain [email protected] wrote:

Hi @lorenae https://github.com/lorenae, my I suggest you to use
dcat:distribution property to add the different versions of the vocabulary?
See spec of DCAT at http://www.w3.org/TR/vocab-dcat/.
Below a sample used for a vocab in LOV to store versions:

@Prefix https://github.com/prefix voaf: http://purl.org/vocommons/voaf#
.
@Prefix https://github.com/prefix vann: http://purl.org/vocab/vann/ .
http://vocab.deri.ie/cogs
a voaf:Vocabulary ;
http://purl.org/dc/terms/creator
http://vocab.deri.ie/cogs#andfre , http://tw.rpi.edu/web/person/TimLebo ,
https://plus.google.com/117319075387042980303 ;
http://purl.org/dc/terms/description
"Vocabulary for describing ETL and data transformation activities."@en
https://github.com/en ;
http://purl.org/dc/terms/issued
"2013-02-25"^^http://www.w3.org/2001/XMLSchema#date ;
http://purl.org/dc/terms/modified
"2014-03-10"^^http://www.w3.org/2001/XMLSchema#date ;
http://purl.org/dc/terms/publisher
http://deri.ie/ ;
http://purl.org/dc/terms/title
"COGS Vocabulary"@en https://github.com/en ;
vann:preferredNamespacePrefix "cogs" ;
vann:preferredNamespaceUri "http://vocab.deri.ie/cogs#" ;
http://www.w3.org/ns/dcat#distribution
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2013-11-25.n3 ,
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2013-12-08.n3 ,
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2013-02-25.n3 ,
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2014-03-10.n3 ;
http://www.w3.org/ns/dcat#keyword
"RDF" ;
http://xmlns.com/foaf/0.1/homepage
"http://vocab.deri.ie/cogs.html" .

WDYT?


Reply to this email directly or view it on GitHub
#112 (comment).

@gatemezing
Copy link

Hi Lorena,
Maybe I don't understand clearly your need. Regarding your last question, what about this solution?
Don't forget that you can always create your own vocab for a specific need and context ;)

@Prefix radion: http://www.w3.org/ns/radion# .
:myDataset1 void:vocabulary http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2013-11-25.n3 .
:myDataset2 void:vocabulary http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2014-03-10.n3 .
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2013-11-25.n3 a voaf:Vocabulary ;
radion:version "0.1" ;
.
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2014-03-10.n3 a Voaf:Vocabulary ;
radion:version "0.2" ;
.

@lorenae
Copy link
Author

lorenae commented Aug 8, 2015

Hi Ghislain
your that seems to work.
I was also thinking about using dcterms:conformsTo.
what do you think of this alternative?

thanks
Lorena

On 8/8/15 3:25 PM, Ghislain wrote:

Hi Lorena,
Maybe I don't understand clearly your need. Regarding your last
question, what about this solution?
Don't forget that you can always create your own vocab for a specific
need and context ;)

@Prefix https://github.com/prefix radion: http://www.w3.org/ns/radion# .
:myDataset1 void:vocabulary
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2013-11-25.n3 .
:myDataset2 void:vocabulary
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2014-03-10.n3 .
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2013-11-25.n3 a
voaf:Vocabulary ;
radion:version "0.1" ;
.
http://lov.okfn.org/dataset/lov/vocabs/cogs/versions/2014-03-10.n3 a
Voaf:Vocabulary ;
radion:version "0.2" ;
.


Reply to this email directly or view it on GitHub
#112 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants