-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add semapv:EntityCloning #24
Comments
Can we try and find a better label for this? I don't think migration is the right word, that makes me think that a term was taken out of one semantic space then put in another (eg a replaced by relation) The definition also reuses the label making it hard to understand quickly. From what I understand, this mapping exists because the term in the second semantic space was constructed deterministically from the term in the first one, therefore making a mapping by construction. Is that correct? |
I guess for me this is the same as "constructed deterministically from the term in the first one" - I have been using the "migration" term, but I am happy to hear better ideas to get the concept across! |
I did a bit more research, and I can't find an official term for this. Here are some more options:
|
I like cloning as the term too |
I updated the title and proposal to use the word "cloning" |
I want to add a new "mapping activity" which I can use as a "mapping justification" in SSSOM:
name:
"entity cloning"
definition:
"A process that involves cloning an entity from one semantic space to another."
comment:
"Many semantic spaces, such as Wikidata or dbpedia, frequently incorporate concepts or classes from other semantic spaces, such as ontologies. For example, the class DOID:0060392 was migrated/cloned to wikidata:Q21124537 as part of a DO - Wikidata alignment process."
A cloning process like this one can serve as a mapping justification is SSSOM: If the term was migrated / copied / cloned, an exact mapping can be safely assumed.
The text was updated successfully, but these errors were encountered: