cygri / void

An RDF schema and associated documentation for expressing metadata about RDF datasets
http://www.w3.org/TR/void/
15 stars 1 forks source link

Alignment with MetaVocab #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
MetaVocab is a proposed “vocabulary for describing vocabularies”, dating 
back to 2002. It has 
found fairly widespread use because it is a documented module for RSS 1.0 feeds:

http://web.resource.org/rss/1.0/modules/admin/

and because it is used in the popular FOAF-a-matic. The vocabulary itself 
should be defined 
here, but seems to be a victim of bitrot:

http://webns.net/mvcb/

The two key term of the vocabulary are generatorAgent (pointing to a URI that 
identifies the 
software that generated an RDF document) and errorReportsTo (usually a mailto: 
URI for 
contacting the webmaster responsible for an RDF document).

GeneratorAgent triples could be attached to void:Datasets and void:Linksets to 
point to the 
software that generated the dataset. ErrorReportsTo could also be provided with 
a linkset as a 
nice shortcut for getting in touch with the publisher. We could put examples 
into the Guide.

On the other hand, the vocabulary appears to suffer from some bitrot and isn't 
properly 
published according to best practice guidelines. Therefore, it might be better 
to first contact the 
authors and get them to fix it, or just copy the terms into our own namespace.

Original issue reported on code.google.com by richard....@gmail.com on 18 Jul 2008 at 12:06

GoogleCodeExporter commented 9 years ago
I wrote to the authors, Aaron Swartz and Ken MacLeod. Aaron confirmed that 
parts of the vocabulary have 
succumbed to bitrot, and fixed part of the breakage. I asked directly about the 
future of the vocabulary, and if 
they plan to bring the hosting in line with the W3C's Vocabulary Recipes 
recommendations. I got no answer to 
this message.

This makes me think we should not use terms from this vocabulary. If we want to 
have generatorAgent or 
errorReportsTo in voiD, we should introduce our own properties and link to the 
MetaVocab ones.

Next question is if we want those properties.

Original comment by richard....@gmail.com on 7 Sep 2008 at 10:06

GoogleCodeExporter commented 9 years ago
We resolved in today's telco to ignore MetaVocab, unless it turns out we have a 
Requirement that can be fulfilled 
by MetaVocab properties.

I'm closing this issue.

Original comment by richard....@gmail.com on 12 Sep 2008 at 10:29