voiD's versioning capabilities

[GoogleCodeExporter]

As pointed out by Jacco van Ossenbruggen on 2009-02-11:

'One of the key things I would like to see added is some simple versioning.
For interlinking, statistics and publishing this seems a crucial feature.
If you could only make the version of a Dataset explicit by adding a  
void:version datatype property, this would also also allow you to say 
that, for example, a Linkset interlinks two specifically versioned 
Datasets, or that a Dataset uses a specific version of a vocabulary, etc.'

Original issue reported on code.google.com by Michael.Hausenblas on 11 Feb 2009 at 10:55

[GoogleCodeExporter]

Antoine Isaac adds a pointer to some related work:
http://www.w3.org/2006/07/SWD/Vocab/principles-20080316#Versions

He says it's unconclusive but might be useful.

I feel uneasy about the versioning idea because it is quite far removed from 
our original linked data use 
cases. With linked data, what you serve is the current version, and there is 
usually no way to access older 
versions, and I don't see much point in talking about something that you cannot 
actually access.

in general, versioning in the RDF world is a complex problem, there have been 
many proposals from 
academia but nothing that seems to have been successful, so I'd rather wait and 
see than try to solve it in 
voiD.

Most of all, I would have to see some concrete deployed examples of datasets or 
vocabularies where 
versioning would be used.

Original comment by richard....@gmail.com on 11 Feb 2009 at 12:32

[GoogleCodeExporter]

I am not sure for datasets themselves, because it doesn't seem so practical to 
create and make available different versions of the same dataset - except as 
mirrors. For vocabularies used in datasets, I like the idea, because it lets 
data 
providers worried about  the instability of vocabularies, tie their data to the 
semantics of specific versions (which could be hosted by them, by the vocab 
hoster, 
or by third party services like schema-cache), while still making their data 
interoperable. Whether data providers are, or should be worried about this (in 
any, 
or all cases), is something I confess I don't know. At any rate, I think we 
should 
encourage interested parties to experiment with this, inventing any new terms 
in a 
separate namespace (eg: open.vocab.org ), and if and when it proves useful, we 
can 
document it in the guide.

I was wondering whether void:vocabulary could be used to point to both 
canonical, 
and versioned, vocab uris. I think this would be overloading it though, and if 
I was 
to do this in my dataset, I would coin a new property or something.

Original comment by K.J.W.Al...@gmail.com on 12 Feb 2009 at 9:50

[GoogleCodeExporter]

As of [1] meeting decided to postpone.

[1]
http://groups-beta.google.com/group/void-rdfs-internals/web/void-skype-meeting-m
inutes-2009-05-21.txt

Original comment by Michael.Hausenblas on 21 May 2009 at 12:02

• Added labels: Milestone-Release3.0
• Removed labels: Milestone-Release2.0

[GoogleCodeExporter]

Original comment by Michael.Hausenblas on 22 May 2009 at 7:16

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by Michael.Hausenblas on 18 Jan 2010 at 12:08

• Added labels: Prodcut-vocab

[GoogleCodeExporter]

Original comment by Michael.Hausenblas on 18 Jan 2010 at 12:11

• Added labels: Product-vocab

[GoogleCodeExporter]

Original comment by Michael.Hausenblas on 18 Jan 2010 at 12:14

• Removed labels: Prodcut-vocab