[codemeta-pmc] Schedule meeting to decide on CodeMeta v3.0 context/id

[Morane GRUENPETER]

Dear PMC,

I need your help with the decision concerning the v3.0 context.
We have some new comments on: 

https://github.com/codemeta/codemeta/issues/321

The new context for the v3.0 will be used by many infrastructures that are already preparing CodeMeta compatibility (including InvenioRDM with Zenodo).
With that, there are infrastructures that are using the v2.0 (e.g ASCL and HAL).
 
This decision has more implications than expected.

This is why I propose two options:
1. schedule a call for the PMC to discuss this decision, to do so I have provided a framadate: doodle.com/meeting/participate/id/dPQBrZ6e/vote where all time suggested are in CEST and compatible with the west cost. 

2. If Tom and Daniel's agree, we can meet during the next SciCodes consortium and open this topic instead of working on the reviewing the mappings with the v3.0 (which was the initial plan). This can be an opportunity to hear also the infrastructures that might be affected. 

Let us know by email your preferred option and in any case please answer the framaform.

Note: Abby is on parental leave and I assume she won't be joining us.

Thank you for your engagement!
--
Morane Ottilia GRUENPETER
Software engineer and project manager
Software Heritage http://www.softwareheritage.org
@INRIA Paris
personal website: http://moranegg.github.io/

[Morane GRUENPETER]

Here with a correct framadate: https://framadate.org/Fd5R5IGpgGPBVNHY :)

--
Morane Ottilia GRUENPETER
Software engineer and project manager
Software Heritage http://www.softwareheritage.org
@INRIA Paris
personal website: http://moranegg.github.io/

[Carl Boettiger]

Unfortunately I can't make these dates, but I trust the team consensus.  

From my understanding, I think the w3id.org mechanism is the best choice.  

I think we could do better than redirecting to https://codemeta.github.io/terms/ (ideally each term would redirect to a deep link or page rather than all terms redirecting to an identical URI) but I think this is workable.  I'm not clear if there is any functionality (specifically regarding adoption by groups mentioned) that hinges on this aspect?  

---
http://carlboettiger.info

--
You received this message because you are subscribed to the Google Groups "codemeta-pmc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codemeta-pmc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codemeta-pmc/CAL8iZAzimO7OnJv35FGwNRNMJV1-EeC%2BofZWB4MfgAOfX4uwcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Tom Morrell]

I’ve added my availability to the schedule, and we can also use part of the SciCodes meeting on October 19th https://www.timeanddate.com/worldclock/fixedtime.html?iso=20231019T08&p1=137. I think we’d have enough time for both a context and mapping discussion. Let me know either way.

Thanks,

Tom Morrell | Research Data Specialist | Caltech Library

caltech.zoom.us/my/tmorrell | 626-395-3827 | data.caltech.edu

--
You received this message because you are subscribed to the Google Groups "codemeta-pmc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codemeta-pmc...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/codemeta-pmc/CAL8iZAzjjr%3DTk10qeFz0aZZsunQOXhguCOHFZpxGSuk99WYuZw%40mail.gmail.com.

[Daniel Garijo]

Hello, sorry to jump in a bit late.

I have added my availability as well, and I will be on the Oct 19th call too.

I think redirecting each term to an individual page is maybe too much, as usually it's better to see them all in context.

However, there should be a versioned page for each codemeta release, so we can jump back and forth between versions.

I usually include a changelog at the bottom of such page to highlight the changes between versions, but that's up for discussion.

Best,

Daniel

To view this discussion on the web visit https://groups.google.com/d/msgid/codemeta-pmc/80A564F4-43FC-4ECE-A461-B2103964CA1D%40library.caltech.edu.

[Morane GRUENPETER]

Dear all,

Thank you for your replies. 

Let's discuss both context and mappings during the SciCodes meeting on Thursday October 19th at 16h CEST instead of having an additional meeting.

After lots of discussions,  the W3id looks like the best fit and the plan is to move towards this option with the possibility to access and use the v2.0 of the CodeMeta vocabulary. 

Thanks for your engagement. 

Best,

Morane