I came across your very interesting package when I was researching your topic for a part in a newly developed package described
The dataset package is in its infancy, but it wants to create a solution to working with statistical data (for example, downloaded from the Eurostat data warehouse with the eurostat package) in a way that it retains all standard metadata. My package extends a data.frame, tibble, data.frame or simliar object with attributes that can be translated to easily to RDF metadata, or added to an RDF description of a data frame, which includes the contents of the data frame, its structure, valid ranges, and as much semantic information as possible about each column and each row.
The problem overlaps with your package's solutions in sevaral ways:
- A dataset should be described with a datacite:Subject, which is ideally a SKOS or XKOS term (XKOS is the statistical modification of SKOS).
- A dataset's columns, whenever possible, should follow the domain-agnostic ontologies of the Statistical Data and Metadata eXchange.
- A future-proof dataset should be convertible to RDF.
So, while my package is not working with ontologies, it wants to be able to use ontologies, and I would like to investigate its usefulness for the purpose. The reason why I brought this up as an issue, because if there is a match and synergy, I think that connecting dataset and ontologics could boost the utility of both packages.
I came across your very interesting package when I was researching your topic for a part in a newly developed package described
The dataset package is in its infancy, but it wants to create a solution to working with statistical data (for example, downloaded from the Eurostat data warehouse with the eurostat package) in a way that it retains all standard metadata. My package extends a data.frame, tibble, data.frame or simliar object with attributes that can be translated to easily to RDF metadata, or added to an RDF description of a data frame, which includes the contents of the data frame, its structure, valid ranges, and as much semantic information as possible about each column and each row.
The problem overlaps with your package's solutions in sevaral ways:
So, while my package is not working with ontologies, it wants to be able to use ontologies, and I would like to investigate its usefulness for the purpose. The reason why I brought this up as an issue, because if there is a match and synergy, I think that connecting dataset and ontologics could boost the utility of both packages.