[codemeta-pmc] 2024 May update

[Morane GRUENPETER]

Hello PMC,

It's been a long time since my last update, and there are many new and exciting things happening for CodeMeta.

Here is a recap of the latest news.

## The CodeMeta mappings - moving towards machine actionable mappings

On April 30th there was the FAIR-IMPACT mapping workshop which we used for CodeMeta mappings

Slides | Notes | framework

Discussion about crosswalks format https://github.com/codemeta/codemeta/discussions/336 

## CodeMeta generator

CodeMeta generator is now generating codemeta.json files that are compatible with v3:

- deployed on https://codemeta.github.io/codemeta-generator/

- code on https://github.com/codemeta/codemeta-generator/

There are a few interesting open issues:

1. Generate expanded jsonld document version from form to use for validation #29

2. Link funding and funder fields #31

3. Add validation for array values #50

4. Add possibility to upload list of fixed terms for a given property #51

## Open discussions:

- Documentation properties: https://github.com/codemeta/codemeta/discussions/335
- Content negotiation: https://github.com/codemeta/codemeta/issues/216 

• Small discussion on the issue.
  
• Move the issue to a discussion in order to vote on this.
  
• Daniel: to create a discussion with the issue.
  
• Morane: to ping PMC - doing it now
  
• Deadline for community vote will be set for June 20th

- Searching for controlled vocabularies: https://github.com/codemeta/codemeta/issues/358 

- Version of codemeta being used in the spec: https://github.com/codemeta/codemeta/issues/340 

• Daniel: action to do a PR

## V3.1 or V4.0

We haven't set yet the next formal release.

We might do v3.1 for the crosswalks before changing the vocabulary for a v4.0.

Let me know if you have strong feelings on this topic.

If you have any other updates to share with the PMC, feel free to share in this mail-thread.

I'll share this update with your additions in community mailing lists, such as the RDA and the FORCE11 mailing lists, next week.

Thank you for your engagement.

Best,

--
Morane Ottilia GRUENPETER
Head of Open Science Operations
Software Heritage http://www.softwareheritage.org
@INRIA Paris
personal website: http://moranegg.github.io/

[Daniel Garijo]

Hi Moranne,

thanks for pushing this forward and the updates.

I will work on my pending to dos next week, as I need to address a deadline by the 21st.

Best,

Daniel

--
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/CAL8iZAx7hU0XZfCD%3DdARz%3D9uXioimo88aL6Fn9fbfbOp7X%2BtmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Morane GRUENPETER]

Hello PMC,

I hope this email finds you well.

## An article on the Rosetta Stone for software metadata

As part of the work in the FAIR-IMPACT project we have discussed the need to have FAIR CodeMeta mappings and moving towards machine actionable mappings

Discussion about crosswalks format https://github.com/codemeta/codemeta/discussions/336 

The possibility to do a research article on the CodeMeta topic with the intent of improving the mappings quality has emerged and I would like to know if some of you would like to join the effort? Please let us know in this thread by Dec. 1st.

## CodeMeta maintenance 

### issues

There are a few interesting open issues:

1. Generate expanded jsonld document version from form to use for validation #29

2. Link funding and funder fields #31

3. Add validation for array values #50

4. Add possibility to upload list of fixed terms for a given property #51

### Open discussions:

- Documentation properties: https://github.com/codemeta/codemeta/discussions/335
- Content negotiation: https://github.com/codemeta/codemeta/issues/216 

• Small discussion on the issue.
  
• Move the issue to a discussion in order to vote on this.
  

• Daniel: to create a discussion with the issue.
  
• Morane: to ping PMC - doing it now
  

• Deadline for community vote was set for June 20th 2024 

- Searching for controlled vocabularies: https://github.com/codemeta/codemeta/issues/358 

- Version of codemeta being used in the spec: https://github.com/codemeta/codemeta/issues/340 

• Daniel: action to do a PR

## V3.1 or V4.0

We haven't set yet the next formal release.

We might do v3.1 for the machine actionable crosswalks before moving towards a  vocabulary change for v4.0.

Let me know if you have strong feelings on this topic.

If you have any other updates to share with the PMC, feel free to share in this mail-thread.

[Morane GRUENPETER]

Dear CodeMeta PMC and friends,

Circling back to the discussions and CodeMeta maintenance from the November update.

I have just added a comment on the two following discussions and we will move forward if there is no objection by Dec. 10th:

- Discussion about crosswalks format https://github.com/codemeta/codemeta/discussions/336 

- CodeMeta content negociation: https://github.com/codemeta/codemeta/discussions/360 

Please give your feedback directly on the issues, it would be nice to have a more FAIR vocabulary and FAIRer crosswalks too.

Let me know if you have questions.

Thank you for your engagement.

Kind regards,

--
Morane Ottilia GRUENPETER
Head of Open Science Operations
Software Heritage http://www.softwareheritage.org
@INRIA Paris
personal website: http://moranegg.github.io/

GPG fingerprint  8E3F 627C BDCC 76C3 5C5E  D222 39E0 4DCF F4F2 C486