-
Notifications
You must be signed in to change notification settings - Fork 676
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
Reference Types Working Group remaining tasks #940
Comments
Please choose your preferred name for the manifest field and API name from the list below:
|
I can't edit, so my vote is for the last one:
It's not the nicest looking one (the underscore!), but I think for the image it's the most obvious term to indicate a relationship (akin to how you'd see when working with graphs "this thing relates to...") and then relationships are also what graph/ontology communities use. This makes me think that having the others as "has X" would actually make them fit that criteria too. "Attribute" is confusing with a kind of feature/descriptor, and qualifies suggests there is some criteria that one thing has that "qualifies" or validates the other. Affects makes me think of seasons, touching, it's just not the right word. So then my second and third choices would be refers and referrers, slight preference over connects/connectors which sounds like it's describing lego pieces. |
Given most people in this community are not necessarily members of the image-spec repo, maybe it makes more sense to not require edit, but pick 6 of the more "positive" looking response emojis and assign them to the rows of your table @nishakm? That way people can just click an emoji response to vote, and it's easier to see totals anyway and who voted. Then we just have to make sure that whatever ❤️ is is what @sudo-bmitch actually wants to vote for 😂 |
I think discussions might have support for polls? https://github.blog/2022-04-12-whats-new-in-github-discussions-organization-discussions-polls-and-more/ |
A key named "attribute(s)" that contains an oci descriptor doesn't make much sense to me. I'm not sure if I get a vote, but "referrer" or "relates_to" are the only ones that form coherence about what that object might contain in my mind. If I do get a vote, then I agree with @vsoch's comment and vote for relates_to/relationships |
😅 Sorry everyone. Just comment here on which ones you like and I will count the thumbs up from others. |
@afflom you can totally vote! |
@nishakm could we |
Thank you that is super helpful! So I’d only like to vote for one, my first choice “relates to and relationships” please! Otherwise I’m watering down my top vote. |
Perfecto thank you @nishakm ! And sorry for the multiple pokes, if you ever need some random help on something I will make time! |
refers / referrers is fine for me relates_to / relationships is good too I don't like any of the others! Too many assumptions in them. |
other... @lachie83 's |
@nishakm can you please add the following with my vote to the table in your comment above - #940 (comment)
|
Doh, apparently I forgot to submit my comment. My vote is for refers/referrers. I'm not a huge fan of the wording, but the longer we go, the more code gets written with those. I'm not a fan of an underscore in the field, but we could also do camel case if that were to get picked. Other ideas to consider (but I'm not voting for):
|
I'd also vote for |
Actually, I like subject / referrers and would change my vote(s) to just that one. Subject is more clear I think. |
|
@nishakm can you help update the table with the other votes - |
FYI my preference is 1 subject, referrers; 2 refers, referrers |
I've removed duplicate votes since more have come out. Seems like |
Bit late to the party but having caught up on the specs etc this week I struggled a bit with refers/referrers so was glad to see this issue. subject/referrers works best for me |
We agreed to merge #934 with the following outstanding tasks:
The text was updated successfully, but these errors were encountered: