Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected behavior for rdfmigrate with datatypes #571

Open
JeltevanBoheemen opened this issue Mar 3, 2023 · 2 comments
Open

Unexpected behavior for rdfmigrate with datatypes #571

JeltevanBoheemen opened this issue Mar 3, 2023 · 2 comments

Comments

@JeltevanBoheemen
Copy link
Contributor

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 without rdf:dataype=xsd.string attributes.
    • skos:notation without rdf: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.

@JeltevanBoheemen
Copy link
Contributor Author

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.

@fvignale
Copy link

fvignale commented Mar 6, 2023

OK. When do you think REO 2.5 will be implemented ? Sorry to bother you again with this question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants