Open JeltevanBoheemen opened 1 year ago
For REO2.5 migration I propose a --nodelete
argument for rdfmigrate
that skips the deletion step, because none of the deletions should actually be applied. However, we should look into a more durable solution.
OK. When do you think REO 2.5 will be implemented ? Sorry to bother you again with this question.
When migrating REO2.4.2 to REO2.5, some unexpected behavior occurs:
additions = desired - actual
results in only the new triples. So far so good.deletions = actual - desired
results in 200+ triples:schema:color
for classes. This is expected, because we manually add them in the migration.owl:inverseOf
for a few CIDOC properties. My guess is Protégé inferred these.rdfs:comment
withoutrdf:dataype=xsd.string
attributes.skos:notation
withoutrdf:dataype=xsd.string
attributes.The last two are problematic. I can see how they are technically not the same triples, but I am unsure why they are not in
additions
, as they are in the REO2.5 graph.