This issue is associated with the charter epic #6.
What mapping use case aspect(s) does this issue address?
Jacob Voß via email:
We have the use case to clean up and unify RDF data in NFDI4Objects. After basic cleanup, testing and analysis of incoming RDF we have graphs that partly use different ontologies so these should be normalized.
I am not looking for a tool to create and manage mappings but a tool or script to actually modify RDF based on existing mapping rules.
For instance, replace every <http://purl.org/dc/elements/1.1/title> with <http://purl.org/dc/terms/title> or replace every URI in the namespace <http://purl.org/dc/elements/1.1/> with <http://purl.org/dc/terms/>.
I neither want to expand the RDF graph with inference rules such as based on owl:sameAs or rdfs:subClassOf but change the data.
This looks like no complicated task but I'd avoid reinventing wheels and I'm sure someone else has similar requirements.
Our current workflow to import existing RDF data dumps is https://github.com/nfdi4objects/n4o-rdf-import and I've already asked at https://metadaten.community/t/uris-in-rdf-daten-ersetzen/244 (in German).
What further steps are needed to be taken or discussed by/in our WG regarding this issue?
[ ] What is the best approach for this normalization use case?
This issue is associated with the charter epic #6.
What mapping use case aspect(s) does this issue address?
Jacob Voß via email:
What further steps are needed to be taken or discussed by/in our WG regarding this issue?