Closed cmungall closed 7 months ago
I think 1 is fine! Renaming makes a lot of sense!
Mapping is for me becoming more the noun describing the declarative artefact..
+1. "Transformer" is also now mentally associated with GPT/ML for me.
Option 1 sounds good and more naturally describes the function to me. Option 2 kind of suggests to me a particular mapping (noun). I agree that Option 3 de-emphasizes the doing.
I would vote for #1. Do you want to make this a poll?
Should we also consider the "migration" aspect? E.g. I want to capture the transformation steps I have to do between a source I've ingested to a final LinkML schema I'm using for my project, or I want to capture the changelog of my schema (e.g. I change the datatype from one release to another). I guess you could call this a declarative "mapping". I also liked "transformation" because one of our use cases was to go from a highly normalized linkml model to a flattened quick-search model.
I like linkml-mapper
or linkml-map
for brevity
@caufieldjh I hadn't considered linkml-map
. This is nice and concise, and fits better into sentences like "use linkml-map for that".
@sierra-moxon yes I'd consider migration a type of mapping (S.vN -> SvN+M). I do agree that "transformation" seems more fitting for less isomorphic mappings, e.g. denormalization, but I think we can make map inclusive!
Another completely orthogonal suggestion would be something like schemawalker
I like linkml-map
I like linkml-mapper
.
I turned the first comment in this issue into a vote.
I voted for linkml-map
..... just out of curiosity, would linkml-translate
convey the message?
Tied between map and mapper. I think I'm going with linkml-map, it's most consistent with parallel efforts like shexmap, fhirmap.
Woohoo! Team Map all the way! 🙌
Proposal: rename this repo to:
"transformer" sounds too GPT-like. Mapping emphasizes a continuum with SSSOM.
Vote
Multiple choice vote, cast as many as you are comfortable with!