Dear Jessica,
To give full disclosure, we have decided not to release 15.0. This has been released internally and, for project reporting, we had to mark that as 15.0 (and apologies, this might have created some confusion to whoever is looking at the code).
It is indeed working but, given various major changes we are bringing (all the project data structures related to previous files will be changed and be based on the MDR) and a few sparse bug fixes here and there, we preferred to delay the release to the community, which will happen (I promise :-) ) before end of January.
I promise it will be worth the wait. The new version 3.0 [1, 2] of the MDR (Metadata Registry) (a recent publication on the almost 3-years old version 2.0 is in [3]), backing both VB and SV will feature an application profile including DCAT-3 [4], VoID [5], LIME [6,7] and a few other vocabularies. As an application profile, it will not be a cut-profile of those vocabularies; on the contrary, it will be extending them, filling gaps of DCAT-3 in specifically describing RDF datasets and – I dare to say – elegantly integrating VoID (and thus LIME, for lexical metadata).
Several features will be based on these new possibilities now and more will be in the future. Yet from the January release, it will be possible to have a clear notion of dataset in both VB and SV and of its various versions, distributions..and deployments of distributions. This can happen internally on a single project (you can have different versions on the same project and switch among them, integrating what was already available through data dumps in VB only) or across different projects (both for backward compatibility – as many users used to create different versions of a same dataset on different projects – and for covering peculiar needs, e.g. a dataset evolving from an OWL representation to a SKOS one, thus using completely different project settings).
Both in VB and SV it will be possible to:
Additionally, in VB, it will be possible to:
Kind Regards,
Armando
P.S. If anybody autonomously built and installed 15.0, the updater should work for that as well. It’s just we, as a precautionary move, preferred to avoid an official release for this intermediate developmen
[2] https://zenodo.org/records/17849142
[3] Fiorelli, M. et al.: MDR: An Ontology Vocabulary and Registry Service for Dataset Catalogs. In : Proceedings of the 38th International Conference on Industrial, Engineering & Other Applications of Applied Intelligent Systems (IEA/AIE 2025), June 1-4, Kitakyushu, Japan (2025)
https://art.uniroma2.it/publications/docs/2025_IEAAIE_MDR2.pdf
[4] World Wide Web Consortium (W3C): Data Catalog Vocabulary (DCAT). In: World Wide Web Consortium (W3C) (January 16, 2014). http://www.w3.org/TR/vocab-dcat/
[5] Alexander, K., Cyganiak, R., Hausenblas, M., Zhao, J.: Describing Linked Datasets with the VoID Vocabulary (W3C Interest Group Note). In: World Wide Web Consortium (W3C) (March 3, 2011). http://www.w3.org/TR/void/.
[6] Fiorelli, M., Stellato, A., Mccrae, J.P., Cimiano, P., Pazienza, M.T.: LIME: the Metadata Module for OntoLex. In Gandon, F., Sabou, M., Sack, H., d’Amato, C., Cudré-Mauroux, P., Zimmermann, A., eds. : The Semantic Web. Latest Advances and New Domains (Lecture Notes in Computer Science). Proceedings of the 12th Extended Semantic Web Conference (ESWC 2015), Portoroz, Slovenia, May 31 - 4 June, 2015. vol. 9088. Springer International Publishing (2015), pp.321-336. doi: 10.1007/978-3-319-18818-8_20
[7] Lexicon Model for Ontologies: Community Report, 10 May 2016. https://www.w3.org/2016/05/ontolex/#metadata-lime
--
You received this message because you are subscribed to the Google Groups "vocbench-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vocbench-use...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vocbench-user/89e26080-f76d-49c0-a4c3-ce5ad57bf56an%40googlegroups.com.